On Thursday 28 January 2010 01:59:30 Luis Garrido wrote: > The important thing for me is that you confirm that keeping an > InstrumentEditor permanently open is a viable way of having the > gig::File structure locked (or borrowed, to use LS terminology) in RAM > so I can change it via the InstrumentEditor API and then call > gig::File::Save on it and that there are no obvious easy alternatives > that I might have missed.
Yes, that's the only way to go at the moment, without changes on the API and a bit on the internal structure of the sampler that is. > In that case, at least for my sake, I wouldn't put a high priority on > the changes you propose, there are probably more important areas of LS > to focus on, and I can proceed as I first planned. Well, ok if your're fine with that, then go ahead! :) And yes, a sound engineer probably doesnt care if there are couple sampler channels opened "too much" by the instrument editor application. It just doesn't look so good and of course for beginners it might be a bit error prone. It's like with the audio / MIDI devices of VST, Au ... host plugins of the sampler. People see the devices of those plugins at runtime and they try to destroy them, change settings on them, etc. CU Christian ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
