| Users sponsoring this issue (Total Sponsorship = US$ 25) |
|
|
I've found a description which says to use a template for MIDI mappings. That's for 2.x.x and doesn't work either in 3.0 svn. Looking further, I've found the software goes to look in ~/.config/ardour3/midi_maps/*.map for MIDI mappings. It expects an XML file there, but nowhere can be found what that XML file looks like. I've managed to reverse engineer a few bits and pieces to get a .map file loaded and parsed, but the actual bindings I've no clue how to configure using that file. I might be able to work on this feature myself, see how far I get, but I have a couple of questions: - What is the status of the bits and pieces of code which remap the MIDI bindings based on these .map files? Does the code involved actually work? - What are the specifications of those files, more specifically the <Binding> entries |
|
|
There is code in GenericMidiControlProtocol::load_bindings() to load these bindings, I believe; this gives an indication of the format. I'm not sure if there is code to save them; I guess they should be saved back to ~/.config/ardour3. |
|
|
Sorry about the duplication of the issue. Could not find it ;-) I confirm this bug. Midi control surface is the only way to work if you are used to it, and I would love for this one to be fixed. |
|
|
http://ardour.org/ardour_midi_binding_maps |
|
|
I am working on a map. DDX3216 is quite complex. Pan is not enabled yet? When can we expect that? |
|
|
pan isn't feasible in ardour's current architecture because its "too complex". ardour doesn't implement a *single* control to pan a track, but has a control per signal in the track. this makes things quite a bit more complicated, sufficiently so that its a post-3.0 item. |
|
|
A suggestion for the "complex" pan situation. Ardour 3 already has all the control elements needed for me to successfully mix using my DDX3216, with fader and pan control by using the assignment method. I typically bind the first of the two signal paths and link the other to it using the panner links. Mono channels I split to stereo first in order to have the two channels to manipulate. I link some channels to follow the encoder and others to swop depending on the channel( effectively controlling how wide a source appears to be. So, you could make the binding something like /route/pan/gain1 and route/pan/gain2 allowing the user to assign controllers to it as they please. Should be more simple to implement it this way, and perhaps even simple enough to make it for 3.0? |
|
|
PS: It could be a clone of the way Ardour3 handles send gain control at this moment. my 2c ZAR |
|
2010-11-23 16:36
|
ardour3 panner.jpeg (66,013 bytes) |
|
|
Added screenshot. Took me a while to realize that I had to add an extra output to the track manually to enable the panner. I see. it is complex. |
|
|
pan control is now entirely feasible. the mono panner exposes a single control; the stereo and VBAP panners expose two controls (position & width). i have not yet added OSC access, but MIDI access is possible. i should write up the MIDI map documents to include this. |
