Nevermind — the issue is that my code was throwing something custom, and 
`auval` expects to see 

  NSError(domain: NSOSStatusErrorDomain, code: 
Int(kAudioUnitErr_FailedInitialization), userInfo: nil)

thrown or else it complains with the warning.

Brad


> On Jun 15, 2021, at 13:32, Brad Howes via Coreaudio-api 
> <[email protected]> wrote:
> 
> All,
> 
> Since we are on the subject of `auval`, I am curious how one solves the only 
> warning I get for my AUv3 plugins:
> 
>       WARNING: Can Initialize Unit to un-supported num channels:InputChan:1, 
> OutputChan:2
> 
> The plugin correctly advertises its channel capabilities as [-1, -1] which 
> means that there can be any number of input and output channels, but that 
> they must be the same. What should my code do properly to remove this warning?
> 
> Thanks!
> 
> Brad
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/bradhowes%40mac.com
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to [email protected]
  • auval curiosity Brad Howes via Coreaudio-api
    • Re: auval curiosity Brad Howes via Coreaudio-api

Reply via email to