Settings compatibility
Settings compatibility
- Subject: Settings compatibility
- From: Stefan Gretscher <email@hidden>
- Date: Wed, 13 Jul 2005 13:26:26 +0200
As the topic came up when discussing the Logic bug about picking the
wrong AU:
Am 12.07.2005 um 23:57 schrieb Os:
On 12 Jul 2005, at 22:38, William Stewart wrote:
In both of these situations I would see this dual-identity as a
feature of the AU specification (especially the sharing of presets) -
there was a post I made about 2 months ago to change the preset
validation mechanism in AUBase to ignore the component type for this
very reason.
Ah yes, I forgot about preset sharing. So I do have a good reason for
wanting to keep the subtype and manu the same.
While this is the easy way to keep the settings compatible, I'd
additionally like to remind AU programmers about the compatibility
features of the AU protocol - look at
kAudioUnitMigrateProperty_FromPlugin. This has been around for a while
now, and recently it's been upped to also do AU-to-AU mapping.
It's a really handy feature e.g. if you release a new AU that can
import settings from an older, no longer supported one, or if you have
some low-end trial and some fully-blown version of your AU and want to
enable users to upgrade from the trial without having to manually
change all the existing songs.
Is there any AU out there that already supports AU-to-AU-mapping?
We plan to add it to Logic (VST-to-AU is already in there) and would
like to verify it in a real life situation.
Thanks,
Stefan
------------------------------------
Stefan Gretscher
plug-in development & 3rd party plug-in support
Emagic GmbH, Hamburg, Germany
a subsidiary of Apple Computer, Inc.
email: email@hidden
phone: (+49)-4101-495-586
(Central European Timezone)
_______________________________________________
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