Re: exception thrown in AUBase::DispatchGetPropertyInfo for AudioChannelLayout
Re: exception thrown in AUBase::DispatchGetPropertyInfo for AudioChannelLayout
- Subject: Re: exception thrown in AUBase::DispatchGetPropertyInfo for AudioChannelLayout
- From: "Patrick Stinson" <email@hidden>
- Date: Thu, 5 Jun 2008 10:07:28 -0800
right, that makes sense. The exception is caught and printed in
ComponentEntry::Dispatch, so it shouldn't be breaking the build.
thanks for your help
On Wed, Jun 4, 2008 at 4:34 PM, William Stewart <email@hidden> wrote:
> Yes, this is correct behaviour...
>
> Your AU has not input elements, so asking for it will throw out an exception
> (AUScope::GetIOElement()) which is caught at the dispatcher and then
> returned as an error to the host app.
>
> So, the host doesn't need to do this (obviously), but it should cause your
> AU any problems if it does... (unless you are overiding a method in AUBase
> or AUScope somewhere here that is tripping this up).
>
> I don't see how this could be breaking your build - just in the debug build
> you will see the error being printed out, whereas in the release build it
> will not. So, I don't think this is your problem.
>
> There maybe a problem with the compiler optimising the code in some way -
> try doing a release build but setting the optimisation level of the compiler
> to be 00 (that is Capital O, and Zero) or Os to see if that makes a
> difference to the thing that is breaking.
>
> Bill
>
> On Jun 4, 2008, at 3:58 PM, Patrick Stinson wrote:
>
>> The application is Ableton Live. I queries the input scope, which I
>> initialized to have 0 elements. weird.
>>
>> On Fri, May 30, 2008 at 12:59 PM, William Stewart <email@hidden> wrote:
>>>
>>> what app?
>>>
>>> The app should be ensuring that you have a scope element on that scope
>>> before it calls you. That said however, AUBase should be resilient to
>>> this
>>> error and will rightly throw an exception for InvalidElement (or
>>> InvalidScope) in this case. This is correct, so I'm not entirely sure
>>> what
>>> your problem is.
>>>
>>> Bill
>>>
>>> On May 30, 2008, at 12:01 PM, Patrick Stinson wrote:
>>>
>>>> queried by the app. the dispatch entry point is only called by the host
>>>> app.
>>>>
>>>> On Wed, May 28, 2008 at 10:53 AM, William Stewart <email@hidden>
>>>> wrote:
>>>>>
>>>>> Queried by what code?
>>>>>
>>>>> On May 27, 2008, at 12:37 PM, Patrick Stinson wrote:
>>>>>
>>>>>> After playing with the xcconfig for my audio unit, I've broken my
>>>>>> debug build, which now doesn't show my custom view. The release build
>>>>>> works fine, but I've spent far too much time comparing the configs and
>>>>>> haven't found anything. There is an exception
>>>>>> thrown in GetAudioChannelLayout for scope 1 (input), which has no
>>>>>> elements since it's an instrument. The exception is caught by
>>>>>> ComponentEntryPoint<Class>::Dispatch(params, obj). Why is it that the
>>>>>> input elements are queried when there are none, which AUBase throws an
>>>>>> exception for? The queries work fine for the output scope, which has
>>>>>> 18 elements.
>>>>>>
>>>>>> thanks
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>>
>>>
>>>
>
>
_______________________________________________
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