On Tue, Dec 22, 2009 at 12:13 PM, Gabriel M. Beddingfield
But this doesn't happen. Jacksession saves the project state. So the
project entitled "my twiddles with my big piano" is saved, not a
repetitive copy of each patch. Patched are loaded in the sampler,
once. the sampler state is saved for that project, and when you reopen
that session, Gigasampler loads the "same" patch for the session as
you requested as saved previously. Sampled patches usually reside on a
static drive, and are "called" for when required. The same is not only
true for Gigasampler, but linuxsampler, kontakt, and most samplers.
They "request" the sample set, i.e. GIG. NKI. SFZ. Other, and it is
made available to the app. One sample library, accessible by request.
Same patch, same app, loaded as required, not saved everytime as a new
patch, i,e, big piano 1, big piano 2 ,etc...
the sampler data, i.e. "when this session is opened, load this patch"
is saved, only.
The same would be true for most apps in a jacksession, with the
exception of recorded audio sessions, and tell me a smart studio, or
serious audio engineer, that doesn't make multiple copies of recorded
sessions, with the view that a messed up session can be discarded, and
the engineer can go back to the previously saved set.
Even for domestic audio users, who don't want to back everything up,
and simply overwrite the previously saved session, most of their
session data is going to be saving "data states", and the overwrite
will imprint the new saved session over the old. Not the way i would
work, but it does work for others, who are quite happy to keep one
Linux-audio-dev mailing list