Re: Resource IDs for AU demo versions etc.
Re: Resource IDs for AU demo versions etc.
- Subject: Re: Resource IDs for AU demo versions etc.
- From: Marc Poirier <email@hidden>
- Date: Sun, 7 May 2006 09:14:12 -0400
On May 4, 2006, at 4:22 AM, Muon Software Ltd - Dave wrote:
I'm interested to know what the situation with AUs is. In the case
of a demo
and full version we don't typically expect the user to want to
install both
at the same time - in such a case then is it acceptable to use the
same
manufacturer ID/subtype for both versions?
In the case of the free and pro versions of the other product, I
did an
experiment with installing both (using same manufacturer ID/subtype/
version)
and hosts only detected the free version and not the pro version.
Given that
these components have different filenames (SatellitePro and
SatelliteFree)
I'm assuming then that AU hosts I tried use the resources to
identify AUs
rather than look at filenames - is that correct?
Yes. The combo of type + subtype + manufacturer codes is an AU's
unique ID. Filename is irrelevant (remember, you can have more than
one AU in a given component bundle, load an AU strictly from memory,
etc.).
If I assume that I need a different component subtype to uniquely
identify
the free and pro versions, I wonder where users who upgrade will
stand from
the point of view of their existing songs. Does anyone have any
thoughts on
this?
Utilize the kAudioUnitMigrateProperty_FromPlugin property with
kOtherPluginFormat_AU to show that your free version is settings-
compatible with your full version.
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