Re: Indexed Audio Unit Parameter
Re: Indexed Audio Unit Parameter
- Subject: Re: Indexed Audio Unit Parameter
- From: "Sophia Poirier [dfx]" <email@hidden>
- Date: Sun, 13 Apr 2008 15:09:30 -0400
On Apr 13, 2008, at 2:42 PM, Chad Wagner wrote:
I'm having a problem with audio unit parameters whose "unit" is set
to kAudioUnitParameterUnit_Indexed. Everything works when the
indexed values start at 0 and I provide an array of value strings.
But one of my indexed parameters has no value strings, which causes a
bus error in auval, and another indexed parameter starts at 1 rather
than 0, but auval seems to be looking for an extra value string as if
they started at 0 (i.e. my range is 1 to 3, I provide an array with 3
strings, but auval is looking for a 4th). In all cases, changing the
unit to generic makes the problem go away, as does leaving it as
indexed but starting at 0 and providing an array of value strings...
e.g. one of the parameters is a MIDI channel, which should be an
integer from 1 to 16. I don't want it to start at 0, and it seems
absurd to have to specify an array of strings "1" to "16". Is there
a better way?
Am I misunderstanding the usage of kAudioUnitParameterUnit_Indexed?
Is it required that the minimum value always be zero? Is it required
that I always provide an array of value strings? Or is there
something else I may be doing wrong?
From your follow up message, it sounds like you've resolved the
problem by located other mistakes that you made, but I just wanted to
say for reference that my understanding is that the things you
describe above are all correct implementation options, and also I have
done all of them in various AUs of mine with no issues (in various
hosts or in passing auval).
Sophia
_______________________________________________
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