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: William Stewart <email@hidden>
- Date: Thu, 4 May 2006 13:05:39 -0700
On 04/05/2006, at 1:22 AM, Muon Software Ltd - Dave wrote:
We've got a few AUs in development that are being broken down into
various
versions. In one product there is a "free" and a "pro" (paid-for)
version,
and in another we have a demo and a full version.
In the VST world a "unique" 4-character ID is declared for each
plugin.
However this isn't very well controlled and there are a lot of
duplicate IDs
out there. As a result most hosts use more information than just the
4-character ID to identify which plugin to instantiate when
reloading a song
file, for example filename, date, version etc.
When doing demo versions of VST plugins in the past, we've always
used the
same 4-character ID for both the demo and the full plugin, and the
same
filename/version for the executable. In this way someone who
started a song
with the demo version could install the full version over the top
of the
demo version when they get it and still have their song load.
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?
The manuID is your name space delimiter. This must be registered
with Apple to ensure uniqueness.
How you manage the sub type is up to you. The information a host
saves for a given AU (and what is saved in the AU preset) is this
subtype. We don't expect hosts to save any additional information
beyond the AudioClassDescription (type, subtype, manu)
Bill
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?
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?
Kind regards
Dave
Muon Software Ltd
www.muon-software.com
_______________________________________________
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
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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