> Would you keep this assignment per-project (saved with all other plugin > settings into a SONAR or other host project) or per-plugin (kept with > DirectiXer settings)? I would prefer per-plugin so that we would make the change once and forget about it. > In the latter case, I see a danger of damaging existing projects by > modifying global assignments of controllers. I would rather not > implement such an approach. That could be fixed with a "reset to default" function. And of course we could save different configs. > In the former case, the UI for controller munging must be available > within the host UI. This is certainly possible but requires more time > that I have for version 2.4. I would prefer the per-plugin solution anyway ;) > Have you used MidiOx / MidiYoke combination? MidiOx can do really > complex transforms of MIDI data, and MidiYoke can deliver them from > MidiOx to SONAR. This way, you are recording exactly what plugin sees, > and not in danger of losing mapping of controllers. > > Does this spell "solution" or "workaround"? :) No but I found an other one : Chainer. I have the demo installed for a while now and just discovered that you can map any CC to any funtion whether CC control is implemented or not. I think I will make the hole in my credit card a bit larger soon :) Dan. ===================================================================== Archive: //www.freelists.org/archives/directixer/ Unsubscribe: mailto:directixer-request@xxxxxxxxxxxxx?body=unsubscribe Admin: mailto:kkm@xxxxxxxxx =====================================================================