Re: Channels and frames
Re: Channels and frames
- Subject: Re: Channels and frames
- From: "john smith" <email@hidden>
- Date: Tue, 01 Nov 2005 13:00:42 +0100
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.
Because it's a cross-platform product.
Then, of course, you have to - ad infinitum - explain to every user how to
do this with every host they use
Yes, that's a problem with the solution I was offered. We would need to
explain for each host. Hmm, that's not good.
So, it looks to me like a version number of 0 is the only option...
- How do you tell a GB user for instance, to do this?
Sorry, GB?
A Digital Performer user
Digital Performer has VST support, right? We generally recommend using VST
for hosts that use both AU and VST (and probably will not support AU at all
in those cases).
, a SoundTrack Pro user
Sorry, I'm not familiar with that app.
, a Metro user
Im Metro we recommend VST (see above).
, an AU Lab user
Another one I don't know, sorry. I'm afraid I'm not too familiar with
applications on the mac platform, sorry.
, etc,.. A "solution" that is
targeted at a specific host app is not going to be sufficient for broad
usage of your AU.
I agree. So, what's the option? As I said in a previous mail, if we remove
it from the interface, then we have to explain in the manual that "there's a
setting for output channels, which can, bla. bla, expect for AU hosts". Or
something like that.
It just strikes me as unnecasary complicated, and the user will be asking
himself "why not, what's wrong with 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.
I do it with respect for the nuances, when (and only when) it makes sense.
That sentence was not about this situation, just like I assume your sentence
wasn't.
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.
Hmm, it was recommended by some other guy (gretscher) that I shouldn't do
that. Strikes me as a bad solution as well (seems too much of a hack).
If we need to describe a more formal solution to resolve this issue, then
I'm happy to consider one.
Sorry, I'm not sure what you mean here.
Thanks,
Michael
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
________________________________________________________________________ __
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
_______________________________________________
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