It is nothing to do with novation that operator can not save midi mappings per preset, that's just how live devices are. Ableton midi mappings are saved p[er project. It is the same with any midi controller. But Ableton does do instant mappings for it's devices. You can use many control surfaces for this, but Novation SL's are probably the best way to have permanently mapped controls because it has a screen telling you what the encoders are controlling in the synth, while in the ableton template. For custom quick assignments, put operator in a rack and then when you select the rack, the instant mappings will control the rack macros.luzil wrote:thx, sounds really bad cause i use operator in nearly every project. So this appears with all midi-controllers like BCR2000 that u cant save the assignments in a preset for ableton plugins? Is this a temporal incompatiblity of Novation Software and Ableton GUI and will be fixed? Or will this generally not work. I read Ableton is written in C++ as most vsti i think. And with the vsti novations automapping seems to be working pretty fine. Are there differences in the GUI? I mean the program only have to save a sreen position for knob for vsti, because thier gui is often static, in ableton depending on tft resolution and opening of browser the position can be different. But how r the novation sliders assigned then to ableton track faders, this does work without saving in every project? I dont get why it doesnt work for plugins.glitchrock-buddha wrote:
The Novation controller can do manual midi assigning just like any other controller using the regular templates. The problem with midi assigning parameters manually on Live's devices like operator is that they can't be saved with the preset. Also the assignments are global in the project. So if you manually assign operator filter for example, then that control is always attached to that knob in that project. That can be good or bad. But if you do this, it can not be saved for alter time with the presets or made permanent for operator. However, template 40 (ableton template, but it's a different template number with the mkII I think)) uses the top 8 encoders to automatically assign to operator's most important parameters (same for all live devices). And if you use an instrument rack, then you can assign whatever parameters you wish to the 8 macro knobs. Then when you select the rack, the 8 encoders will automatically control those 8 rack macros. That's the way to go when you want to be able to control only what is selected. The bottom 8 knobs on the SL are available for global assignments, so it won't matter if the device is selected or not, they will always control what you midi learn to them.
Sry for question, but this saves me some hundreds euro if can only use the remote sl in such a limited way to control Live i have to reconsider this. Its many knobs where a main pro criteria for me. Is there any way to control operator with another midi-controller so i can easily laod its preset in every project i put a operator in? At least i need a quick controlling of all 4 osc coarse, fine, level, ADSR.
This is not the same as plug-in automap though. The above method uses ableton's own instant mappings, which the ableton template takes advantage of on the SL (not the the automap universal template)
