[Ardour-Dev] Development Summary (5.8..ba24f287ca)
robin at gareus.org
Thu May 4 13:38:47 PDT 2017
On 05/04/2017 09:03 PM, Fons Adriaensen wrote:
> On Wed, May 03, 2017 at 11:51:35PM +0200, Robin Gareus wrote:
>>> BTW, 5.8 still reconnects auditioner and click to system ports
>>> even if the session was saved without those connections. That's
>>> a very old one.
>> Indeed, "empty" port-name for those means "use defaults". Unless you
>> audition or enable the metronome it won't play anything on these ports.
>> It's intentional and not a bug. It's a lot more inconvenient if they're
>> not connected to anything.
> If this is a 'feature' I'd call it a fake feature, to use the
> language of our times. What's wrong with restoring a session
> *as is was saved* ??
It's not a feature, it's a fact. The config file never lies. :)
nitpicking here: It's restored as it was saved. It's just not saved in
the way you expect:
The auditioner connection is saved with the session. When a port is
given, it is saved in the *preferences* (studio setup). An empty config
currently means "autoconnect".
Anyway, unconnected ports means that the audition-signal goes nowhere.
Audition does not work. So I conclude you never audition anyway. Why do
you care if the ports are connected?
I'm asking because fixing this and handling relevant edge-cases  in a
backwards compatible way is a significant amount of work. I've started
to prepare this a while ago (using explicit "default") but postponed it.
 e.g. When using a monitor-section the auditioner ports are
disconnected and connect the monitor-section instead.
More information about the Ardour-Dev