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 API I guess I shouldn't rely on it.
I think it's better to adjust the instrument editor API on sampler side appropriately. One problem currently is that you can only access an instrument manager by an engine instance, which implies creating a sampler channel etc. So maybe we have to consolidate this first, so one can access instrument managers globally, independent of sampler channels and engine instances. Maybe we could simply introduce a new factory class for instrument managers, which holds exactly one instrument manager for each sampler format and one can access the respective instrument manager of the respective format no matter if an engine channel and engine instance of that format is instantiated or not. This is probably not so much code change. After that one should extend the instrument manager, so instrument editors could insert new instruments by their own into the resource pool of the respective instrument manager. 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
