Re: Logic7.1 picks the wrong plugin
Re: Logic7.1 picks the wrong plugin
- Subject: Re: Logic7.1 picks the wrong plugin
- From: William Stewart <email@hidden>
- Date: Wed, 13 Jul 2005 11:05:20 -0700
There's one other point I wanted to make about this as well. This is
a suggestion, rather than a requirement.
AU Presets are stored in the following locations: /, ~/, /Network/ then:
Library/Audio/Presets/<AU MANU NAME>/<AU NAME>/
In order to facilitate the sharing of presets between different
incarnations of an AU, we'd also suggest that those AUs be given the
same name.
In our case, we have:
auol tmpt appl - Apple: AUTimePitch
And:
aufc tmpt appl - Apple: AUTimePitch
(Just a note, in Tiger, the auol version was named
AUOfflineTimePitch, but this has been changed in 10.4.2 to what you
see above.
By using the same name for these different AUs allows applications to
both save and restore presets to the disk into/from the same
directory locations. So:
Library/Audio/Presets/Apple/AUTimePitch/
is where presets for both of these AUs would go - which is entirely
appropriate of course as the presets between these AU types are
interchangeable.
We don't believe that it is necessary to have a different name. It
should be clear from the usage context, which particular
manifestation of an AU you are using. For instance, in the AU
Instrument vs AU Effect it is clear in current host apps by the place
within the channel strip that you are adding an instrument or effect
version of the AU. The same would apply to the difference in usage
situations of converters and offline units.
We believe that this enhances the user's experience as it simplifies
the preset handling and sharing; providing a substantial and useful
benefit.
Thanks
Bill
ps AU Lab (/Developer/Applications/Audio/) provides full support for
preset handling, so you can experiment with this yourself if you
would like to see how this works
On 13/07/2005, at 4:21 AM, Stefan Gretscher wrote:
Indeed, as Bill pointed out you shouldn't change the IDs to work
around this bug - it's a serious issue with Logic and we just gotta
fix it.
Here's more info on the current behaviour:
Logic unfortunately ignores the component type and always picks the
AU that it finds first and that matches the given I/O config.
In 5.x versions, that would depend upon the order the AUs are
returned from the system. The 6.x versions started caching AU
information, so there it would depend upon the order of the AUs
within the cache. This is why the bug went unnoticed for so long:
it often just worked by coincidence.
In Logic 7.1, the cache is now always sorted by ID for faster
access, which results in this defined behaviour:
effect slot: "aufx" stays "aufx" but "aumf" is replaced by "aufx"
instrument slot: "aumf" stays "aumf" but "aumu" is replaced by "aumf"
Am 12.07.2005 um 23:57 schrieb Os:
Ah yes, I forgot about preset sharing. So I do have a good reason
for wanting to keep the subtype and manu the same.
Looks like I'll be telling users to update their hosts after all.
At least if they run into the problem, they are able to correct
this by inserting the proper AU and the settings should be kept
unchanged.
Best,
Stefan
On 12/07/2005, at 2:38 PM, William Stewart wrote:
No. He is already using a unique ID - the unique ID are the three
identifiers of the component, its type, subtype, and manu. If other
hosts have problems here then they should fix their implementation
here as well.
An offline AU and a converter AU can vector down to the same code,
where some minor differences are used for the different AU types,
but otherwise the code is identical. These two AU types represent
distinct usage scenarios (one is where the AU is being used in some
real-time context, the other to process a file). The presets
between these two AUs can be interchangeable for example. Apple
ships two AUs on your system that behave in exactly this manner:
AUTimePitch and AUVarispeed - the only distinction between the two
is the au's type (auol vs aufc)
Of course the situation Os describes is similar, and quite legitimate.
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.
Bill
--
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