Re: [Linuxsampler-devel] Complex editing sessions and the InstrumentEditor interface

2010-01-27 Thread Luis Garrido
> I think it's better to adjust the instrument editor API on sampler side > appropriately. Hmm, ok, then. To be honest, the only ugly thing about having a 'sentinel' InstrumentEditor is the possibility of never using the SamplerChannel created to get it, but I can work around that by eventually pa

Re: [Linuxsampler-devel] Complex editing sessions and the InstrumentEditor interface

2010-01-27 Thread Christian Schoenebeck
On Wednesday 27 January 2010 23:38:50 Luis Garrido wrote: > Yup, I don't want the sampler to free the structures while I am > working with them. > > I thought perhaps of including a copy of the ResourceManager header > with my project and hooking up my app there, but since you don't > publish that

Re: [Linuxsampler-devel] Complex editing sessions and the InstrumentEditor interface

2010-01-27 Thread Luis Garrido
> So just to get it right, you want to launch fake instrument editors by the > sampler which you then use in the actual instrument editor application to > control the file / instrument data structures? > Yup, I don't want the sampler to free the structures while I am working with them. I thought

Re: [Linuxsampler-devel] Complex editing sessions and the InstrumentEditor interface

2010-01-27 Thread Christian Schoenebeck
On Monday 25 January 2010 21:55:03 Luis Garrido wrote: > Hi, guys! > > I keep pondering about how to use the InstrumentEditor stuff in > qgiged. I'd like to know if you can suggest a better way to lock a > gig::File structure in an InstrumentResourceManager memory than the > fugly one I ramble abo