Perhaps you can experiment reducing the preload cache size, if you have a fast processor and hard disk:
/* Define amount of sample points to be cached in RAM. */ #define CONFIG_PRELOAD_SAMPLES 32768 That's 128 K per stereo, 16-bit sample, so 1 GB RAM would allow 8K samples. An instrument of average complexity could have, let's say, 4 velocity layers and 20 splits for a 5-octave range, that'd be 80 samples, meaning about 100 instruments worth of cache in that GB. Anyway, regarding your question, I don't get very well what you are trying to achieve, but if it is something you can do manually from the front-end, acting on the back-end doesn't look the best idea to me. It should be easier to add automation to the front-end side (from what I gather from your message that would be the VST plugin code.) BTW, why don't you stick to the mode compatible with your host? You are referring to the instrument lifetime modes, right? ON_DEMAND Instrument will be loaded when needed, freed once not needed anymore. ON_DEMAND_HOLD Instrument will be loaded when needed and kept even if not needed anymore. PERSISTENT Instrument will immediately be loaded and kept all the time. Cheers, Luis ------------------------------------------------------------------------------ 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
