@ paul:
Well, I just can’t figure it out, in this release it just defaults the Generic MIDI to “disabled” mode. A very few times I was able to reopen a session with the bindings saved, closed and reopened the session and no longer was Generic MIDI enabled, when re-enabling, the bindings were lost making me re-assign them again. Always checked that midi connections were connected in qjackctl, even tried before opening Ardour, I would launch Ardour, then at the starting prompt window I would switch to qjackctl and connect the M-Audio Oxygen to Ardour control, then load the session and would still fail to have MIDI enabled.
When I trace the input in terminal there is no problems there, shows me all MIDI activity.
Also I have my Oxygen connected via MIDI to Fast Track Pro, so I also tried instead of connecting Oxygen to Ardour I bridged it with Fast Track Pro, so Fast Track would send the MIDI messages to ardour and had same issues, sometimes (very few) it did remember the bindings but mostly would reset, thinking if maybe could be something to do with M-Audio MIDI, both devices are M-Audio.
I check ~.ardour2/ardour.rc and it defaults the MIDI settings right there
The Mute bug still persists also, have to open ~.ardour2/ardour.rc to change the values, these values don’t change like the MIDI settings, they do remain as edited.
One last thing, I mostly get the log window when reopening sessions, the main message is this:
[ERROR]: control protocol XML node has no name property. Ignored.
[INFO]: Loading session /home/joe/Desktop/test using snapshot test (1)
Loading history from ‘/home/joe/Desktop/test/test.history’.
I’m not sure if this has to do with the MIDI bug I’m having, since it happens quite often also.
I’ll wait for further instructions from you, I just couldn’t figure it at all, deleted my ~.ardour2 folder many times and nothing…
So if you have any ideas just let me know, I do want to see if anyone else is having this particular issue.