brainstorm: how to update panel modulators on program change

[msepsis]

it’d be great of the panel modulators would update to the current values upon program changes either initiated from the panel or the actual piece of gear.

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[minimalist]

Oh yes! This is a really great & mighty feature request! Almost every day I’m dreaming about it… ” title=”Wink” />
This could be the last step that Ctrlr and the synth are finally REALLY one thing…
And you’re right – the modulator update should happen by program changes done in Ctrlr and also by program changes at the synth itself.
This is my hottest dream ever! ” title=”Very Happy” />

[msepsis]

I’m thinking it should be possible with mutli messages attached to a program change knob who’s last message is a syesx patch/sound/program request from the hardware synth (the message would be different for every synth)… but I’m wondering then if all knobs and sliders, combo boxes and buttons would have to be set to be sending sysex (and receiving… not sure if ctrlr modulators actually can receive messages currently?), not ccs…

why I titled this a brainstorm ” title=”Razz” />

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[atom]

this does not work this way, like i wrote some time ago about the virus, 99% of synths send program data as a bulk of bytes that you need to decode to usable numbers/text and set modulators from that decoded data. You must write at least a line or two of code (lua) to interpret this data, each synth does that in a different way, sometimes it differs between firmware versions. I’m doing work on that but it’s very complicated to get something usable. I thought about doing this without LUA but almost every idea i had was a bad idea.

[minimalist]

Yeah, we already spoke about this some weeks ago. If I understood it right the most complicated thing to realise this, is the support of ALL synths – because everyone has it’s own Sysex format.
It’s just a completely shot in the dark: I thought about that maybe it could be more easy to implement if each panel supports this "modulator update" just for 1 single synth. Maybe there could be an component option/field where the user can type in a particulary "line of code" which is translating just the dedicated Sysex dump message which comes from the current controlled synth. As I told, it’s just a shot in the dark from a non-programer…

[nozoku]

and maybe for the "line of code" we could use the deviceDB? to share the translation of the bulk sysex for different devices for the users that cannot do it themselves?

[atom]

yes that’s how it will be done, each panel (actualy the Program Manager of each panel) will have all the needed options to make this communication work, and it will be panel specific.

DeviceDB, well sure since it will be a part of a panel you can always look at others people work and how they solved those problems. Nothing will be compiled/binary.

[Prana]

Yes!It´s an essential feature!I would love it!

[OnkelHage]

That would be great! Would give my setup a fastforeward.! ” title=”Razz” />

[Author]

Posts