How much do you adjust parameters in UI?

[Pastitas]

@riban

That previous point highlights a reason why we need access to all of an engine’s parameters. We each want to modulate different parameters and hence need a mechanism for mapping CC to controls. The current method involves finding the parameter in the engine’s control screens, turning on MIDI learn and twiddling the knob. There are different implementations as described in this thread but the point is that a curated list of controls or better, a user defined selection of controls may be preferable for sound design and performance but full access is required to perform the mapping and ideally that is done without the need for external devices like VNC.

I think having to use the webconf for the arragement of the controls wouldn’t be a huge pain but definitely there is a need to be able to map cc in the device itself.

In my opinion the way the current method is flawed is in the workflow with mapping midi in the synths, with no way of exporting, importing or modifying midi mappings for synths, which kinda locks you to using snapshots for the purpose of controller maps, even if you purpose-built midi interfaces for the synths you most often use.

Also for me the part where you get feedback into which value you’re modifying with an external controller is pretty important.

@ricard

I don’t really want to bog this thread down with my own views, but I have thought a lot about parameter editing over the years, and which compromises are better and which are less good.

I’d recommend you to check out this thread (shameless plug) then, since I’d also love some feedback on the idea I’m working on and talk about user interface desing.