• 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: Tue, 15 Dec 2009 12:37:57 -0800


On Dec 14, 2009, at 11:01 PM, tahome izwah wrote:

Like I said, if you support *both* [1,2] and [2,2] you won't have a
problem. It is when you support only [1,2] that you run into this.

ok - I misread your comments


While it doesn't crash in the current version of the SDK it can't be loaded either (AULab cannot add the effect "SingleInput" because an error has occurred. Result code: -10868). This is better, but still the [1, 2]-only plug in is unusable in all hosts that I tried this with, even though it passes auval and is displayed and selectable.

All you have to do is add

UInt32 SupportedNumChannels(const AUChannelInfo** outInfo)

this needs to be virtual...

	{

			static const AUChannelInfo asChannelInfo[] = { { 1, 2 } };
			if ( outInfo )
				*outInfo = asChannelInfo;
			return 1;

	}

To a new Cocoa AU created from the template.

You also need to add this to the constructor:

	CAStreamBasicDescription desc = GetInput(0)->GetStreamFormat();
	desc.mChannelsPerFrame = 1;
	GetInput(0)->SetStreamFormat(desc);

(if you don't the AU fails to initialise because the default formats are 2 channels). The AU passes validation, but fails in the way you mention in AULab, so we'll follow up on this and figure out why.

Bill


--th

2009/12/15 William Stewart <email@hidden>:

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.


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

  • Prev by Date: Re: Audio Unit ioConfigs (Resolved)
  • Next by Date: carbon, 64bit and AU views
  • Previous by thread: Re: Audio Unit ioConfigs
  • Next by thread: Re: Audio Unit ioConfigs (Resolved)
  • Index(es):
    • Date
    • Thread