search

zynthian / zynthian-issue-tracking

Centralized Issue Tracking for Zynthian Project
https://github.com/orgs/zynthian/projects/1
11 stars 3 forks source link

Setting midi mappings per synth or layer. #288

Open Pastitas opened 3 years ago

Pastitas commented 3 years ago

Is your feature request related to a problem? Please describe. I often find myself struggling to create new sounds because the computer is not a nice interface, so I have an assortment of midi controllers that i use for this purpose. The number one problem is the need to map the controls each time, wich can be frustating and time consuming.

Describe the solution you'd like I'd like be able to load templates and to be able to recall a layer and have a mapping be there already, maybe a default one, if defined.

Describe alternatives you've considered Another option would be to have default midi mappings, so I can map my midi controller CCs in advance, or even extract, load or copy between snapshot's midi mappings.

Additional context This builds into the idea of having a more "hardware synth" setup kinda deal, where you can have a dedicated controller for a synth an so on. This along the ability to create presets would make Zynthian a lot more standalone, which is something i think a lot of people can appreciate.

Pastitas commented 2 years ago

Is this issue blocked because of the current shift to the API based system?

riban-bw commented 9 months ago

There is a fairly new mechanism called MIDI Device Drivers which allows devices to be configured to operated in predetermined ways. It may be advantageous to leverage this new mechanism to impelement this requirement.

riban-bw commented 1 month ago

Does this request refer to a template of CC mapping to an engine and/or a template of CC mapping for a hardware controller? The latter is best done in device driver. The former would need some kind of user defined (or saved) template that is applied on each engine load. To avoid complexity, this would need to always happen so that every time the engine is added to a chain it gets this user defined MIDI binding. The MIDI binding can be overriden and saved in a snapshot.

I'm not sure how popular this request would be, i.e. if the implementation effort is sufficiently beneficial.

We could add a "Load MIDI Binding" option to the snapshot menu to allow user to save snapshots with their preferred binding but that would be challenging to map the snapshot engine with the current chains' engines. We could allow the import (load) of individual chains, merging into the current configuration. In this way a user could configure chains as they like, including MIDI binding and save as a snapshot then import / merge / load just the chains they want with the binding they want.

Pastitas commented 2 weeks ago

To clarify, the idea is closer to the "Midi binding" that you describe second, but with the ability to use a specific hardware with it, so think of it as a midi default mapping for specific devices and plugins. This could be achieved with snapshots as you said, or maybe there's a way of making templates so they can be shared? just trying to clarify, not sure It's gonna help

riban-bw commented 2 weeks ago

That sounds like ctrl device driver.