27 Mar
2012
27 Mar
'12
10:45 p.m.
Am 27. März 2012 21:41 schrieb Fons Adriaensen <fons(a)linuxaudio.org>rg>:
...
Nor would I want the the shared data to be duplicated
In my scenario, this would match EXTERNAL_REF
It would only be copied to Lfiles directory, if modified.
Obviously there are cases, where this is not desirable
and destructive editing is preferable.
The app could offer this as an option, as you are pointing out below.
- not only
because it's a wast of disk space, but also because it may be
reviewed and modified as well (e.g. correcting bad edits) and
such changes should be picked up by all sessions using the data.
My POV about 'external' data (that is data not
saved as part of
a session) is that if the user (or an app on behalf of the user)
declares that some data is external to the session then the SM
should just accept this as a fact an go on doing its thing. It
is then of course the user's responsability to take care of such
data if a session is transferred or archived.
I would expect a SM to have a tool to 'ls' a
session (providing
a list of required apps etc.), and ideally such a tool should be
able to mention any dependencies on external data.
Another useful tool: ' list-session-deps Lfile/audio.wav '
that would list all sessions and applications with current-references
to that file.
--
E.R.