Guys, I have an old session from 2008 (time flies …) which I created with Ardour 3 I believe. I am cleaning my old recordings and found this nice song idea which I had completely forgotten! So I opened it in Ardour 9.7, and to my surprise, it opened fine, just some old plugins were missing and stubbed. No problem, I replaced them with modern versions and it still played as I remembered it.
However, I used to have effect busses (which are still there) and back in the day, you did not have “aux sends” in the track menu. The old “sends” are still in place but most of them don’t send anything any longer for some reason and I can’t use their respective IO matrix, clicking on it does nothing:
So I wanted to recreate them with “aux sends” but to my surprise, the “New Aux send”, “New Foldback send”, “Remove Foldback Send” menu items are grayed out in every track. Did anyone experience something like that ? Is there some internal IO architecture incompatibilities between these antic Ardour versions and the 9.x series ?
Since 9.7.120 (tomorrow’s https://nightly.ardour.org/ build) sends from the old Ardour 2 session are now properly converted.
You have to start with impro25-2000.ardour. Ardour 3.x already had the bug of not correctly converting old external sends. It’s a side-effect of MIDI ports and MIDI sends that were added in Ardour 3.
I can add aux-sends to busses, and was even able to do that after loading impro25-2000.ardour in Ardour 9.7.0. Please let me know if that still is an issue with 9.7.120 on your end.
The only downer is : I now remember, when I created this session with Ardour 2, MIDI was not yet a thing and I used Rosegarden to track the MIDI drum line, which contains time sig changes and tempo ramping at various time points. I had then recorded the drums into an audio track in the Ardour session. MIDI came with Ardour 3 IIRC (or was it A5 ?), I imported the MIDI track into it and built the specific time signatures and tempo changes / ramping. When I initially opened the A3 session in A9, the timepoints where the changes are supposed to happen were messed up. So I need to recreate them. Maybe you could still check with my A3 session whether time sig and tempo changes convert correctly in A9. I vaguely remember that Ardour started to offer two timing modes (audio vs musical) at some point and maybe the old A3 sessions don’t convert properly because of this (just a wild guess).
<!-- Sample rate converted from 96000hz to 48000hz -->
No version of Ardour ever resampled, so this is likely something you did yourself manually as some point? Perhaps this can explain the marker differences?
–
PS. Yes, Ardour 3 introduced MIDI and related tempo infrastructure.
Originally, I recorded everything at 96k. After looking at the disk space, I resampled all my sessions’ audio files at 48k manually (via scripting) and edited the session files manually to avoid the warning popup (and to be honest, it did not make a difference sound-wise). Strange that 96k is still in the old session files but anyway, when I started building the time sigs and tempo changes, I think it was already at 48k but it was so long ago, I can’t be sure and you could be right on that. In any case, it’s no big deal to redo it. Thanks again for your timely help!
Just curious, what went into the nightly build apart from the fix for my case ?
Until the release notes are written for the upcoming 9.8 release, the only way to find this out is by reading git commit messages: Commits · Ardour/ardour · GitHub
