• 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: Audio Unit ioConfigs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audio Unit ioConfigs


  • Subject: Re: Audio Unit ioConfigs
  • From: William Stewart <email@hidden>
  • Date: Mon, 14 Dec 2009 19:31:08 -0800


On Dec 14, 2009, at 8:08 AM, tahome izwah wrote:

I don't think that you can prevent this from happening - at least I
never found a way to do it. Also, in order for a [1, 2] config to work
you need to support [2, 2] as well, otherwise your AU will crash on
init.

huh? This is the first I've heard of this and there are a number of audio units that do [1,2] and [2,2] configs. Where is the crash? Have you filed a bug report on this? If you haven't please do with a reproducible case if possible. Thanks.



--th

2009/12/14 Chris Santoro <email@hidden>:

I'm trying to implement an audio unit (type aufx) with the ability for
mono->stereo and stereo->stereo, but NOT mono->mono.

ok, so what you have below is correct.


My AU subclasses from AUMIDIEffectBase and properly overrides the SupportedNumChannels function.

ok


If I run the AU Validation tool on it, it shows the proper channel handling
capabilities.

right


//------------------------------------------------------- Reported Channel Capabilities (explicit): [1, 2] [2, 2]

Input/Output Channel Handling:
1-1   1-2   1-4   1-5   1-6   1-7   1-8   2-2   2-4   2-5   2-6   2-7
2-8   4-4   4-5   5-5   6-6   7-7   8-8
      X                                   X
//-------------------------------------------------------

However, both AULab and Logic 8 show a mono->mono option, even though it
isn't there.

Are you sure? If we just take AULab as the starting point, can you print out the formats in the Init call for both the input and output. I would be surprised if your AU is being asked to do mono in/out if it explicitly says it can't support it. I would share your concern about this too! :)


Bill


Is this a bug in Logic or am I doing something wrong? Has anyone else
experienced problems with this? I've also tried every combination of
removing/restarting/rebuilding I could think of, in case the component
manager might be caching out-of-date information.


Best,
Chris

_______________________________________________
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
  • Follow-Ups:
    • Re: Audio Unit ioConfigs
      • From: tahome izwah <email@hidden>
References: 
 >Audio Unit ioConfigs (From: Chris Santoro <email@hidden>)
 >Re: Audio Unit ioConfigs (From: tahome izwah <email@hidden>)

  • Prev by Date: Re: Audio Unit ioConfigs (Resolved)
  • Next by Date: Re: Enable matrix mixer inputs without ramping
  • Previous by thread: Re: Audio Unit ioConfigs
  • Next by thread: Re: Audio Unit ioConfigs
  • Index(es):
    • Date
    • Thread