• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AU incorrectly reports Dynamic Configuration capability ???
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU incorrectly reports Dynamic Configuration capability ???


  • Subject: Re: AU incorrectly reports Dynamic Configuration capability ???
  • From: William Stewart <email@hidden>
  • Date: Mon, 14 Aug 2006 12:32:50 -0700

There's a couple of points of confusion here.

On 14/08/2006, at 6:47 AM, Chris wrote:

Hello,

auval returns this when I try to validate my plugin (effect)...
Does anyone has an idea of what is the problem?

(Plugin is working in AULab anyway)


I have redefined public: UInt32 SupportedNumChannels (const AUChannelInfo** outInfo) { if (outInfo==NULL) return 2; else { _AUChannelInfo.inChannels = -1; _AUChannelInfo.outChannels = 2;
This just says you can have any number of channels on input (-1), but stereo on output. It isn't a dynamic config setting

return 2;

This is wrong I think - you are returning **1** AUChannelInfo struct, not 2. I think the second one is garbage - which is why auval is probably thinking you are reporting dynamic config when you aren't.


	}
}


Best regards Chris

(XCODE 2.4, OSX10.4.7 and MACBOOK, auval  1.1.2c11 )




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 X
ERROR: AU incorrectly reports Dynamic Configuration capability (bus count is not writable)

*IF* you were reporting dynamic config capabilities, then there is a also a requirement that the bus count is writable on the scope that is dynamically configurable. The idea is this:
(1) You report the maximum number of channels you can support on a given scope (input or output)
(2) The host will set up some number of elements (buses) on that scope, where the total number of channels is less than or equal to the total number of channels you reported in (1). Because the host decides how your channels are going to bundled/bused, it needs to tell your AU how many buses to establish on that scope.


The document in the SDK about this goes into more details (/Developer/ Examples/CoreAudio/Documentation/...)

Bill

_______________________________________________
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

--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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


  • Follow-Ups:
    • Re: AU incorrectly reports Dynamic Configuration capability ???
      • From: Chris <email@hidden>
References: 
 >AU incorrectly reports Dynamic Configuration capability ??? (From: Chris <email@hidden>)

  • Prev by Date: Re: AU Cleanup / destructor, what to do in which method?
  • Next by Date: Re: AU incorrectly reports Dynamic Configuration capability ???
  • Previous by thread: AU incorrectly reports Dynamic Configuration capability ???
  • Next by thread: Re: AU incorrectly reports Dynamic Configuration capability ???
  • Index(es):
    • Date
    • Thread