On Monday 08 February 2010 02:38:44 Luis Garrido wrote:
> Can an InstrumentEditor object API be used to modify safely
> instruments other that the one used to spawn it?
In theory yes. I just checked the code again and I think it should work, but
we never tested this scenario before. So maybe ther
Can an InstrumentEditor object API be used to modify safely
instruments other that the one used to spawn it?
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers
> 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, cha
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 Instrumen
> 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
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
> 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
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
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 about here:
https://sourceforge.net/apps/trac/qgiged/wiki/devel/doc/R
