Am 2. April 2012 21:22 schrieb J. Liles :
> Why would one
If you work with samples, OTHO, why would you
want the (same!) samples to be stored in the sessions folder
and even in duplications ?
To waste some space ?
That was our conclusion for using symlinks.
The clients would be advised, to create them
> (and hopefully the application involved uses the symlink
> Remember, you can always write a simple shell script
We can always create shell scripts for anything,
but aren't we talking about some kind of "management" !?
NSM has some nice rules already, to make things behave smooth.
Now add a few sensible rules, to make sure that
audio-file management works equally well.
These are really very simple points, I say.
- clients MUST create symlinks for all external files used - in the
- clients are ADVISED to store large-files in "/nsm/large-files/" (and
create symlinks for them as in previous point)
> I think this is very much a corner case anyway.
I think no, but very much depends on personal work-flow.
I use to do different Versions of _the same_ project,
with some minor or major differences.
So my workflow would be:
- create a session
- if happy with a state, duplicate
- continue work with the duplicate.
since many/most files stay the same, there is no reason
to copy the files over different session directories.
Linux-audio-dev mailing list