On Mon, Jun 14, 2010 at 3:25 PM, Christian Schoenebeck <schoeneb...@software-engineering.org> wrote: > On Monday 14 June 2010 16:53:00 Christopher Cherrett wrote: >> ON_DEMAND_HOLD >> >> but would also like to get rid of extra samples when I am done with them. > > What kind of extra samples? > > Anway, you can also replace the map entry, or delete the map by LSCP to get > rid of old instruments with HOLD or PERSISTENT mode. Some people also send a > "RESET" command and transfer a new instrument map to the sampler. > > CU > Christian > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Linuxsampler-devel mailing list > Linuxsampler-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel >
I get the impression this is about "live" loading and unloading, where a sequencer reads ahead, and at a given point, swaps one gig for another. (Sort of like, "in 5 bars time i need 1st violins staccato, so i'm going to load it in the background 4 bars before it's needed, and dump the existing 1st violins legato just after the staccato starts.) If this is the case being described, then i would think it's the sequencer's responsibility to provide read ahead functions, but some mechanism that tells LS to load another gig in the background, and on receiving a message from the sequencer, dumps the existing loaded gig. I guess you could say this might be" ON_DEMAND_UNTIL_MESSAGE_RECEIVED_TO_DUMP_CURRENTLY_LOADED_GIG". Not sure if that's possible at the moment, as it would need not only a change in LS, but code written in sequencers as well, to read ahead, and send a "get ready" message to LS, without immediately swapping gigs. Bank and patch changes in sequencers tend to send for immediate change, and that ignores the time it takes LS to load the next gig, which is why ON_DEMAND_HOLD is so important for fluent and smooth playback. I guess you could call that sequencer function something like "4 bars before a designated bank/patch change, send a secret message to LS to load the next gig, and once that's happened, dump the previous one, unless it's going to be used again in the next 4 bars." So LS knows it needs to load a gig in advance, but the sequencer needs to hold off immediately switching to that gig, until it's actually needed. Good idea though. Alex -- www.openoctave.org midi-subscr...@openoctave.org development-subscr...@openoctave.org ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
