4 Mar
2012
4 Mar
'12
11:17 p.m.
Am 4. März 2012 22:47 schrieb David Robillard <d(a)drobilla.net>et>:
On Sun, 2012-03-04 at 16:17 -0500, Paul Davis wrote:
On Sun, Mar 4, 2012 at 3:37 PM, J. Liles
<malnourite(a)gmail.com> wrote:
> consider the SFZ file format. it refers to other audio samples. it
> doesn't require that the references use absolute paths, but they can.
> so now create
a plugin that allows the user to alter what samples are
used for various note numbers or velocity values or whatever (i.e. a
reasonably capable sampler) and ask it to save its current state. it
gives you an SFZ file to stash away in a location of the host's own
choosing. but what do the contents refer to?
Yeah, this problem sucks. The only solution is for the plugin to map
the paths inside that SFZ file.
It is (inherently) necessary for the plugin to map
*ALL* paths in its
state for this to work. If they happen to be in some pre-existing file,
well, that's probably going to be pretty annoying, but you have to map
them all the same.
For simplification, one could assume all samples had a common parent directory ?
Then the user could simply re-locate that common parent directory,
if the samples were not found ?
example:
/home /user /store /samples /shapewavs /sine.ogg
moved to:
/home /user /newplace /samples /shapewavs /sine.ogg
common parent directory: samples/