Re: Audio Units and Multi-mono in Logic 8
Re: Audio Units and Multi-mono in Logic 8
- Subject: Re: Audio Units and Multi-mono in Logic 8
- From: Stefan Gretscher <email@hidden>
- Date: Fri, 25 Jul 2008 11:08:32 +0200
Am 25.07.2008 um 08:40 schrieb P. Grütter:
you could include two different units in your component. I do so in
one of my plugins, there's a (multi-)mono (that supports all n-n
configurations) and a stereo version (that only supports 2-2
configuration). On stereo tracks Logic lists both units, on other
tracks it only lists the (multi-)mono version.
Cheers, Paul
That's an obvious workaround indeed, but I would strongly suggest NOT
to to do this because it breaks the general AudioUnit approach of
organizing all I/O configurations in a single plug-in. Breaking this
concept has several disadvantages:
- settings will no longer be automatically shared between the various
I/O configurations of the same plug-in
- the host will have to deal with more plug-ins, which is slowing down
the plug-in management (e.g. validation)
- once we add the feature Sophia suggested to Logic, your users will
see two plug-ins doing the same thing, causing confusion
Also, implementing the workaround "properly" has more to it than
simply providing different number of channels. You must support the
settings compatibility properties
(kAudioUnitMigrateProperty_FromPlugin etc.) to make sure settings can
be properly sent back and forth between the different flavours of the
plug-in by the host.
You should also be aware of that Logic's multi-mono feature (despite
its name) can actually use mono/stereo combinations to ensure proper
processing of stereo pairs in the stream (e.g. rear left+ rear right
surround channel processed in the same stereo instance to keep the
impact on stereo imaging minimal). This implies that if you really did
the workaround, you should rather code a plug-in variant that does
"normal" mono+stereo plus another one that does only the multi-channel
formats instead of doing the two flavours you're suggesting above.
I think that's a lot of compelling reasons not to hack around
potentially temporary host limitations but rather do like Sophia said
and file bug reports. Btw: duplicate reports from different sources
will raise the priority of a request, so don't skip this just because
someone else already did it. I know filing bugs may be a lengthy
process, but our bug database is a very important instrument of our
daily work and it depends on your input, so please make good use of it.
Thanks,
Stefan
Am 24. Jul 2008 um 21:02 Uhr schrieb email@hidden
:
On Jun 25, 2008, at 4:07 PM, Matthew Morton wrote:
I have an AU with a class, myClass that is derived from
AUEffectBase.
ProcessBufferList() is overridden so that one of two processes may
occur; Firstly, if(inBuffer.mNumberBuffers == 1) then a mono
version
of the processing algorithm is run. The other option runs for all
other inBuffer.mNumberBuffers , and this is a stereo version of the
algorithm. Now, I could implement a third algorithm for when there
are 6 channels, assuming 5.1 surround audio, and in fact I have
and it
works fine. However, I thought it would be interesting to have my
AU
work in the multi-mono mode within Logic to give the user further
control. My question really is relating to how Logic knows how to
implement a plugin as a 5.1 or Multi-mono version; what are the key
parts involved here? Any help from others who have done this
themselves would be great. Thanks very muchly!
From what I can deduce, Logic will present a 5.1 version if the
plugin claims it will support that (via its implementation of
SupportedNumChannels), and if not (and if the plugin does support
mono
operation) then it will present the plugin as multi-mono.
I agree with you that Logic should still make the multi-mono option
available for surround- and mono-capable plugins. There are reasons
why multi-mono can sometimes have its own advantages. Pro Tools
allows for both options. I submitted an enhancement request for this
to Apple back in November 2007, though others should too if they
agree
it's important since more reports gets bugs noticed more. :)
http://bugreport.apple.com/
- Sophia
------------------------------------
Stefan Gretscher
plug-in development & 3rd party developer support
phone: (+49)-4101-495-586 (Central European Time)
AU developer support: email@hidden
TDM developer support: email@hidden
Apple GmbH
Geschäftsführung: Georges Guyon de Chemilly
Sitz der Gesellschaft: München
Amtsgericht München, HRB 66158
_______________________________________________
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