• 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: Multi-input bus (sidechain) configuration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multi-input bus (sidechain) configuration


  • Subject: Re: Multi-input bus (sidechain) configuration
  • From: Brian Willoughby <email@hidden>
  • Date: Tue, 21 Oct 2008 13:38:21 -0700

Steve,

The standing advice from this list, if I recall, is that you must derive from AUBase to do what you want.

That said, AUEffectBase implements some very useful things which nearly everyone needs, and it's quite a pain to implement them every time you use AUBase. It would be great if Apple split AUEffectBase into two, perhaps with AUEffectNxNBase and AUEffectMxNBase as appropriate. Most of AUEffectBase is very specific to effects which have the same number of busses on input and output, with correspondingly-matching channel counts.

I suggest you look closely at AUBase, and start by deriving from that. If you're successful, you might try learning how to achieve the same results with AUEffectBase, but you might have to hack things too much.

Brian Willoughby
Sound Consulting


On Oct 21, 2008, at 12:33, steve wrote:
I'm trying to create a AU plug-in with a fixed configuration of 2x stereo bus inputs, and 1x stereo bus output by modifying the FilterDemo example plugin from the SDK (derived from AUEffectBase), with the following modifications:

1. I've added creation of an additional input bus in the constructor thus:

  AUBase::CreateElements();
  SetBusCount(kAudioUnitScope_Input, 2);


2. I've overridden SupportedNumChannels to return a single { 4, 2 } pair.


3. I've overridden Initialize() so it doesn't simply try to match the above pair to the Input(0) and Output(0) channel counts.

I'm clearly missing something fundamental though - though the buses seem to be correctly reported with sensible audio stream formats, auval fails with the following output:

VERIFYING DEFAULT SCOPE FORMATS:
Input Scope Bus Configuration:
Default Bus Count:2
Format Bus 0: AudioStreamBasicDescription: 2 ch, 44100 Hz, 'lpcm' (0x00000029) 32-bit little-endian float, deinterleaved
Format Bus 1: AudioStreamBasicDescription: 2 ch, 44100 Hz, 'lpcm' (0x00000029) 32-bit little-endian float, deinterleaved


Output Scope Bus Configuration:
Default Bus Count:1
Default Format: AudioStreamBasicDescription: 2 ch, 44100 Hz, 'lpcm' (0x00000029) 32-bit little-endian float, deinterleaved


ERROR: Default Format of unit does not match reported Channel handling capabilities
* * FAIL



Can anyone give me any pointers in the direction of my (I suspect) obvious error?


Thanks,

Steve.
_______________________________________________
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: 
 >Multi-input bus (sidechain) configuration (From: steve <email@hidden>)

  • Prev by Date: Re: coremidi virtual endpoint problem
  • Next by Date: Re: reminder for AU View compatability
  • Previous by thread: Multi-input bus (sidechain) configuration
  • Next by thread: Re: Multi-input bus (sidechain) configuration
  • Index(es):
    • Date
    • Thread