Re: 2in1: MusicDevice & MidiEffect
Re: 2in1: MusicDevice & MidiEffect
- Subject: Re: 2in1: MusicDevice & MidiEffect
- From: Urs Heckmann <email@hidden>
- Date: Sat, 11 Dec 2004 04:17:36 +0100
Hiya Marc,
thanks for the insight!
I found that auval was testing my 'aumf' for InstrumentCount without
complaint... yes, I'm lazy, my aumf supports this Property... hence my
thoughts...
Do you say that there's anything in MusicDeviceBase that makes it
useless when instantiating as an aumf, because it awaits certain calls
before it would actually let stuff happen?
I went ahead the traditional way and so I currently have 2 identical
.h/.cpp pairs, one deriving from MIDIEffectBase, the other from
MusicDeviceBase, which works great, but of course itches me due to
redundancy.
Thanks btw. for bringing up the idea (2 years ago, I think it was) of
using the same derivate of AUBase for a Shell-like plugin, by creating
the actual implementation depending on SubType. This is dead simple.
Btw. my Save/RestoreState question was bogus as this happens in AUBase,
and it checks against current ComponentDescription which of course has
nothing to do with the actual OtherBases::BaseClass. I have got to
override it anyway, because each plugin in the .component can read each
other's presets :-p
Cheers,
;) Urs
Am 11.12.2004 um 00:20 schrieb Marc Poirier:
I've done this (with Pluggo) and it is not as simple as you are
hoping. You need to handle Component selectors specific to
MusicDevices and a few other things. Anyway, when you start
tinkering, and testing with auval, you will see what needs to be
done...
Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden