[Ardour-Dev] Trouble with imported files

Fons Adriaensen fons at kokkinizita.net
Sat Mar 21 15:43:10 PDT 2009

Taking up Ardour's way of hard-linking imported
files when possible, and even when 'no copy' has
been requested, this has another unexpected
consequence which hit me today.

When the imported file is replaced with one having
the same name, the Ardour session doesn't see the
change, and continues to use the old file.

For a file that is explicitly requested not to
be part of the session this is not what would be
expected - changing the external file should 
affect the session.

Once again, this behaviour is leading to results
that depend on something the user very probably
is not aware of.

IMHO, Ardour should do one of two things, depending
on what the user specifies, that is, either:

A. copy the file to the session directory, or
B. refer to it as an external file, 

and not something that behaves sometimes as A and
sometimes as B, depending on the phase of the moon.



Io lo dico sempre: l'Italia è troppo stretta e lunga.

More information about the Ardour-Dev mailing list