External Midi W Instr Midi Control

[dby]

Thanks! You get where I’m coming from.

@Cie

I think, the Midi-Control Device was not originally designed to map all parameters of a synth and control it via this device; but to add only the midid-cc you want to automate/change in the song. So these cc are changing during play anyway.

Yes, trackers in general have never been live performance oriented, but nowadays with GridPie and whatnot, it’s an excellent live tool… only need some tweaks here and there. Also it’s great to have all parameters mapped when you edit a patch, with a MIDI controller like BCR2000 compact synths become pretty close to having a full blown synth. Instr. MIDI Control works just fine the way I use it, except for this little detail of sending CC to all params on startup.

@Cie

Your approach is nowadays, in times of hardware synths with limited control-surface, reasonable of course. An update of the Midi-Control Device would make sense definately.
I would suggest to send out a value of a Midi CC only, if there is an automation value set for that Midi-CC somewhere in the song. If there is no automation of a MIDI-CC it won’t send anything (also not 0 on startup).

There has been rack mount synths with limited control surface since the eighties, but newer ones are accepting more CC parameter control.

I’m suggesting a little more complex sollution that eliminates the need for saving every variation of a patch you make on the synth (Instr Midi Control On Startup), you could load a patch, edit some params and save the Renoise song. I think it’d be nice to use factory presets as starting points sort of.

Even if your suggestion is a lot better than it is now, it would be kinda like going back to the workaround before the Instr. MIDI Control - CC on startup bug was fixed ([Fixed 2.8 Rc2] Renoise Not "remembering" Midi Cc Values). Well the only difference is I’d like automated AND sliders that has been moved since a program was changed on the linked ext. MIDI instrument to send CC on startup.