|
|
It is possible to create new NSM sessions which include Ardour 3.5, but not quite without issue as stated above. A dialogue is displayed with a drop-down menu to select buffer size. A warning message reads: "The JACK audio backend was configured and started externally. This limits your control over it" Ardour should really just use the buffer size already configured by JACK. After clicking OK an error message is displayed stating that the session could not be created, but after clicking OK the message goes away and Ardour appears. When re-opening the NSM session the buffer size dialogue and the error pop-up are always displayed. |
|
2013-10-20 11:52
|
Audio-MIDI Setup_001.png (18,690 bytes) |
|
2013-10-20 11:52
|
Untitled window_003.png (9,186 bytes) |
|
|
I think the problem is that Ardour is suddenly unable to open projects when there is a whitespace in the path (which would be the case if your session is saved under "NSM Sessions"). At least that's the case on my system. Escaping the whitespace or wrapping the path in quotes don't work either. |
|
|
I tried removing white space from path names but the issue persists. Old (pre-Ardour3.5) sessions still can't be opened and 3.5 sessions still display the setup dialogue/warning. This is using Ardour 3.5.14 |
|
|
It seems that, when started by NSM, Ardour 3.5 expects the folder containing the Ardour session to hold files named Ardour.ardour and Ardour.history, whereas Ardour 3.4 would add the NSM session ID to the names, e.g. Ardour.nAEQS.ardour and Ardour.nAEQS.history. Renaming these files and editing Ardour.ardour so the name in the 2nd line reads: name="Ardour" instead of: name="Ardour.nAEQS" solves the problem! Tested on latest release Ardour 3.5.143. The JACK config dialogue issue is no longer present. |
- Anonymous
