FabFilter User Forum
Bug: multiple instances + midi learn
Hi,
I've tested this not with Saturn and Timeless in both Ableton and Reaper, on OSX 10.6.8. Basically what happens is if I have more than 1 instance of the plugin in the project, and I assign a midi CC to a parameter, via the midi learn, ALL THE OTHER INSTANCES take on this midi assignment. So If I assign Saturn 1 mix to cc 10, then saturn 2's mix, will get changed to cc 10 as well.
The thing is, is that the other instances will change their cc assignment, even though midi learn is not activated on them.
Thanks
Greg
greg — Aug 19, 2012
here as a video showing it happen - notice the Saturn without midi learn enabled changing it's CC number once the other Saturn's CC has been changed
imageshack.us/clip/my-videos/16/u5zwczyygzzjsqlzpknzhs.mp4
g
This is intended behavior: we store MIDI learn assignments globally.
Think about how confusing it would be if we would store MIDI learn assignments in plug-in parameters: you would have to re-learn them for every new plug-in, or try to store them in a preset... etc.
Cheers,
well if that's your intention so be it, though I don't really think your avoidig much confusion, or else plugin developers would have been implementing that system for the last 20 years, which isn't the case
I can see if your gearing towards mixdown situations, where people are loading 30 Pro C's and Q's, they want their console to work the same on each track.
The thing though, this isn't the way everyone uses plugins, ESPECIALLY the creative suite. Global CC's across all plugins is quite strange in that regard. That means you can't have 2 Volcano's on 2 tracks and control them at the same time - independantly.
I for one would say that there should be a preference to enable global CC's across plugins. This would account for big mixdown situations where consistancy is imperative, and when not enabled, more creative and typical production\live scenarios, where cc's only control what they are assigned to
cheers,
Greg
Our idea is that you set a fixed assignment for the knobs on your controller to the controls in a plugin like Volcano.
Of course you can have 2 Volcano's on 2 tracks and control them independently. In Cubase for example, you just make two MIDI tracks and route each of them to a different Volcano instance.
However, you can't control the two at the same time via the same controller. For that to happen, we would in fact have to store the CC assignments with the plugin parameters, but that could easily get confusing. Perhaps you can assign MIDI CCs to parameters manually in your host in this case?
Cheers,