• 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: auval 1channel test
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: auval 1channel test


  • Subject: Re: auval 1channel test
  • From: William Stewart <email@hidden>
  • Date: Mon, 2 Jul 2007 19:25:09 -0700

This is a little arcane to understand, but here is how it works.

The pairs of numbers you provide for channel capabilities are NOT per bus, but are a possible channel combination for ANY input to ANY output bus.

So, if have your 3 input elements,

if you publish {1,1}, {1,2} then you would only see mono on each input if you had either mono or stereo output

if you publish {1,1}, {2,2} then you would see either all mono (inputs and outputs) or all stereo, but no mix between the two

If you publish {1,1} {1,2} {2,2}, then if your AU has 2 channels output, any input can be either mono or stereo.

HTH

Bill

On 25/06/2007, at 6:21 AM, bastian.schnuerle wrote:

hi list,

my au has one element with one inputelement, one outputelement and 3 elements with only one outputelement each. channel infos are {1,1} {1,2}{2,2}. auval succeds. when auval does its render test for two channel input and two channel output, au::validformat and au::changestreamformat is done for all elements. good. but when auval is doing its one channel test, it does au::validformat and au::changestreamformat only for the first element. seems logical to me. but here is the paradoxon i face. the one channel render test also includes the other three elements. why ? and what makes this even more paradox is, that the number of channels for these output elements are always two. i would assume, that when they are included in the one channel render test, they should also have only one channel, not two, right ? they then should also be included in the au::validformat and au::changestreamformat calls don by the auval 1 channel render test, not ? am i doing something wrong ? I have tried to SetStreamFormat for these outputelements in the render or processbufferlist calls, but this blows the auval ...

any ideas for a workaround or how to solve this issue are appreciated.

regards,

bastian
_______________________________________________
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


  • Prev by Date: Re: problems using afconvert to do alac to aac
  • Next by Date: Re: (no subject)
  • Previous by thread: Re: Bug Resolved as of when?
  • Next by thread: Re: (no subject)
  • Index(es):
    • Date
    • Thread