Re: Channels and frames
Re: Channels and frames
- Subject: Re: Channels and frames
- From: William Stewart <email@hidden>
- Date: Mon, 31 Oct 2005 11:43:45 -0800
Yes, this is what I would have thought as well. Why make the user go
through all of this - and this will in any case be broken with any
other host that uses the version number to cache information, unless
you have a way for a user to invalidate this cache. Then, of course,
you have to - ad infinitum - explain to every user how to do this
with every host they use - How do you tell a GB user for instance, to
do this? A Digital Performer user, a SoundTrack Pro user, a Metro
user, an AU Lab user, etc,.. A "solution" that is targeted at a
specific host app is not going to be sufficient for broad usage of
your AU.
As a general comment if you are sharing code between VST and AUs I
think you need to do this with a respect for the nuances of the
various specifications, rather than trying to bend one solution to
fit badly... This is of course, one of the big challenges of
supporting multiple formats or hosts, and we certainly recognise that
this is something all AU developers have to deal with in one way or
another.
So, currently for an AU you should either publish your channel
capabilities as they are, or, every time you change your channel
capabilities, you should return a different version number for your
AU **AND** you need to edit the version number contained in the
component resource. If we need to describe a more formal solution to
resolve this issue, then I'm happy to consider one.
Bill
ps - thanks for raising this issue Michael.
On 31/10/2005, at 6:26 AM, Marc Poirier wrote:
On Oct 31, 2005, at 7:40 AM, john smith wrote:
One of our plug-ins has a user setting for the number of output
channels. This is a preference setting, i.e. is not stored with
the project, but rather "globally". Also, the user is required to
reload all instances before the new setting works.
Ewww, why not just publish all possible channel configurations as
legal, and let the user/host choose configurations according to the
AU spec?
Marc
On 31/10/2005, at 6:08 AM, Stefan Gretscher wrote:
B: Logic will not even realize this after a restart, because the
version number hasn't changed.
true as well, but this can be worked around by manually launching
the AU manager from Logics preferences menu and rescanning the plug-
in there.
This is what other developers who did run into the same problem
advise their users to do.
As most users will adjust this setting only once, you may improve
user experience by asking the user about this in the installer.
--
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