linuxaudio.org

--20cf30363911cd315e04c4edf653

Content-Type: text/plain; charset=UTF-8
On Sun, Jul 15, 2012 at 7:55 PM, David Robillard  wrote:
> On Fri, 2012-07-13 at 15:57 +0100, James Morris wrote:

quoted text
> > Hi,

> >

> > My sampler app has Non Session Mangement implemented but is currently

> > still referring to external files by their original path.

> >

> > I want to use the symlink method as discussed fairly extensively here

> > but I'd like to know if there is any recommended strategy for naming

> > the symlink of a sample.

> >

> > It could so happen that as far as the filesystem is concerned the only

> > discerning uniqueness between two samples is in the path (ie

> > kit1/snare1.wav and kit2/snare1.wav).

> >

> >

> > I've come up with three possible solutions to this (in my current order

> > of preference):

> >

> >

> > 1) symlink-to-sample created in a subdir named using a hash* of the

> > full path to external file

> >

> > 2) painstakingly re-create the full path within the session dir and add

> > the symlink into that.

> >

> > 3) some horrible text manipulation of the full path (ie replace / with

> > _) that is bound to fail.

> >

> >

> > * J. Liles mentioned SHA1 here:

> >   http://linuxaudio.org/mailarchive/lad/2012/3/30/189343

> >

> > Are there other/better options or disagreements about (1) being a good

> > choice over the other options I've presented?

>

> I just used the original name of the file, with a number added for

> uniqueness if necessary (which is very seldom the case).  It works and

> is much more human-friendly and straightforward than the above options.

> A "make this path unique by sticking a number on the end of it" function

> turns out to be pretty useful anyway.

>

> Of course, you need to actually check for existence of files to create

> it, which might be a problem in some cases (though not any I've

> encountered), but anything that assumes a mapping based on the current

> path is a unique identifier for a particular file's contents is bound to

> fail anyway.

This is exactly what I do in Non-DAW as well. Use the original name and add

an ordinal number until it's unique.
--20cf30363911cd315e04c4edf653

Content-Type: text/html; charset=UTF-8

Content-Transfer-Encoding: quoted-printable
On Sun, Jul 15, 2012 at 7:55 PM, David R=

obillard <d@drobilla.net> wrote:

On Fri, 2012-07-13 at 15:57 +0100, James Morris wrote:

quoted text
> Hi,

>

> My sampler app has Non Session Mangement implemented but is currently<=

br>

quoted text
> still referring to external files by their original path.

>

> I want to use the symlink method as discussed fairly extensively here<=

br>

quoted text
> but I'd like to know if there is any recommended strategy for nami=

ng

quoted text
> the symlink of a sample.

>

> It could so happen that as far as the filesystem is concerned the only=

> discerning uniqueness between two samples is in the path (ie

quoted text
> kit1/snare1.wav and kit2/snare1.wav).

>

>

> I've come up with three possible solutions to this (in my current =

order

quoted text
> of preference):

>

>

> 1) symlink-to-sample created in a subdir named using a hash* of the

> full path to external file

>

> 2) painstakingly re-create the full path within the session dir and ad=

d

quoted text
> the symlink into that.

>

> 3) some horrible text manipulation of the full path (ie replace / with=

> _) that is bound to fail.

quoted text
>

>

> * J. Liles mentioned SHA1 here:

> =C2=A0 http://linuxaudio.org/mailarchive/lad/2012/3/30/18934=

3

quoted text
>

> Are there other/better options or disagreements about (1) being a good=

> choice over the other options I've presented?
I just used the original name of the file, with a number added for

uniqueness if necessary (which is very seldom the case). =C2=A0It works and=
is much more human-friendly and straightforward than the above options.

A "make this path unique by sticking a number on the end of it" f=

unction

turns out to be pretty useful anyway.
Of course, you need to actually check for existence of files to create

it, which might be a problem in some cases (though not any I've

encountered), but anything that assumes a mapping based on the current

path is a unique identifier for a particular file's contents is bound t=

o

fail anyway.This is exactly what I do in Non-DAW as w=

ell. Use the original name and add an ordinal number until it's unique.=
--20cf30363911cd315e04c4edf653--