Re: SupportedNumChannels problem
Re: SupportedNumChannels problem
- Subject: Re: SupportedNumChannels problem
- From: William Stewart <email@hidden>
- Date: Tue, 4 Mar 2008 17:30:32 -0800
On Mar 4, 2008, at 4:39 PM, Kevin Dixon wrote:
I am inheriting from AUEffectBase. It seems that if I only have one
set of
values, e.g. {{1, 1}}, and it has a mono output, then it will fail.
If i
have one set of values, but in the form {{1, 2}}, then it will be
fine.
Is there some requirement that all effects should be stereo output
capable, or does auval just do the first initialization test with a
stereo
output?
no - I think the problem is that the default format for an element is
stereo, but because you only support mono you have a mis match.
In your constructor, after you call CreateElements() you should get
the input and output elements and set their channel counts to 1 to
match your channel capabilities - this is the "Default Format" print
at the top of the validation process - these both need to be mono
Bill
-Kevin
If you are inheriting from AUEffectBase, then its Initialise call is
validating the format of the AU at that time based on this
information.
If you are inheriting from AUBase, then there is no such work being
done for you, so you'd have to verify that yourself
Bill
On Mar 3, 2008, at 10:45 PM, Kevin Dixon wrote:
I implemented SupportedNumChannels in my au as shown here
UInt32 sscau::SupportedNumChannels(const AUChannelInfo ** outInfo) {
static const AUChannelInfo myInfo[1] = {{1, 1}};
if(outInfo)
*outInfo = myInfo;
return sizeof(myInfo) / sizeof(AUChannelInfo);
}
But when i run auval on my AU I get format not supported error
-10868
Is there something I'm missing? I had this problem before, but I
ended up
adding another item to the myInfo, and it went away.
-Kevin
_______________________________________________
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