Re: kAudioUnitProperty_SupportedNumChannels on MusicDevice
Re: kAudioUnitProperty_SupportedNumChannels on MusicDevice
- Subject: Re: kAudioUnitProperty_SupportedNumChannels on MusicDevice
- From: Jeremy Sagan <email@hidden>
- Date: Tue, 13 Nov 2007 20:47:05 -0500
On Nov 13, 2007, at 8:31 PM, William Stewart wrote:
The one AU type where this is optional is the music device. For an
effect, it has to have an input. For a generator we expect no
inputs. For other AU types, an input would be required.
Yes it is a music device.
For the music device though, there is no real difference between
having an input and having the option of having one. The AU can
always tell if there is anything connected to an input or not, and
I would think that if the instrument can accept input, then it
might as well have an input element available in any case.
Well there is unnecessary processing occurring if the music device
accepts 0 inputs but can't be configured that way. IMO I think that
the an AU should fail AUValidation if it says on the one hand that it
can accept 0 inputs but then when it is configured as such it does
not accept them (but that is because I had a bug in my app that in
this condition did not fill in the audio buffers since my host app
incorrectly presumed that the AU was accepting the promised no input
configuration!).
Jeremy
Bill
On Nov 13, 2007, at 5:12 PM, Mark Pauley wrote:
What is the type of your audio unit? If it's aufx then I'd expect
at least one input too...
_Mark
On Nov 13, 2007, at 4:27 PM, Jeremy Sagan wrote:
Hello Bill,
Shouldn't a user be able to use 0 inputs if the audio inputs are
optional?
Jeremy
On Nov 13, 2007, at 6:10 PM, William Stewart wrote:
auval is probably ignoring the 0 because the AU clearly has an
input element.
On Nov 13, 2007, at 12:10 PM, Jeremy Sagan wrote:
I have run into a curious problem with a particular plug-in.
I call kAudioUnitProperty_SupportedNumChannels to get the
supported channel info on this plug-in and I clearly get this
array: 0000 0002 0001 0002 0002 0002
Meaning to me that it accepts 0 in 2 out, 1 in 2 out and 2 in 2
out.
However in Auval all I see is:
FORMAT TESTS:
Input/Output Channel Handling:
1-1 1-2 1-4 1-5 2-2 2-4 2-5 4-4
4-5 5-5 5-2 6-6 8-8
X X
In other words AUVal does not see the 0 in 2 out. Also the
problem I am having is that if I set the plug-in to 0 in 2 out
it will not accept it and sets its input number back to 2.
Any help appreciated here.
Note that AULab does not show 0 inputs as a possible
configuration either.
Note also that I am using a very old version of AUVal 1.1b9 I
think since others I have seem to have expired.
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@verizon.net
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
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