Am 28. März 2012 05:46 schrieb David Robillard :
> Files are files. Size does not have any impact on how any of this has
> Why? What exactly is "large"?
The reason is simple and important:
Duplicating a session should be lightweight.
Lfiles _belong_ to _one or many different_ sessions, but they would
not be stored within the session folder.
Instead, a cloned session would contain references to _the same_ Lfiles,
as its original !
This means, no Lfiles are copied, just referenced, thus its a quick procedure.
This is no problem, if applications are non-destructive: If the clone
had to change
a file, it would create a copy in the Lfiles directory and use this
For destructive apps, this woulde not work obviously and the SM would
have to duplicate their files in the Lfiles directory too.
What is a large-file ? (for a non-destructive app)
Every file, that is not required to immediately become copied if a
session has to be cloned.
Every file, where a reference is enough in the first place.
What is NO-large-file ?
Data that is required to access large-files (references), or that is
lightweight (~below 1MB)
(some config-values), or has to be read by the SM to initialize the client.
Linux-audio-dev mailing list