Re: MatrixMixer info

• Subject: Re: MatrixMixer info
• From: Robert Grant <email@hidden>
• Date: Tue, 18 Nov 2003 07:41:56 -0500

2. If the channel layout of the input audio unit does not match the mixer input bus then the MatrixMixer will not accept input. Use kAudioUnitProperty_StreamFormat to fix them up.

I wouldn't use the words "channel layout" here. To us, channel layout means the number and order of the channels (viz AudioChannelLayout). That matrix mixer only cares about the number.

You're right - my mistake - I'll correct the page.

Hmm... Well, this is a very confusing statement Robert.

There is nothing special about the matrix mixer here and how it handles connections (well, aside from the bugs of course:-).

A connection between 2 audio units by definition must share the format between the output of the source and the input to the destination unit.

In fact, manipulating a format on either side of any connection where that manipulation is done in any manner in which this connection is in an inconsistent state when a render call is made (ie, the connection is used) will lead to "undefined results"

Not my terminology preference.. 0xFFFFFFFF is the master. These are output channel gains.

I wasn't thinking big enough - (too focused on my little app) - of course if you've got multi-outs you'd want one fader to control them all... I'll correct this too.

All volumes in the matrix mixer can be set in Global Scope, where the elementID is set as:

Input Volume is:
(in << 16) | FFFF
Cross Point:
((in << 16) | out
Output Volume:
(FFFF << 16) | out
Master Volume:
FFFFFFFF

Its kind of nice to just think about this in one scope with just one argument (the elementID) to configure.

Bill

• Prev by Date: Re: MusicDevice with a different approach
• Next by Date: using MusicPlayer to convert sysex bulk <-> std MIDI
• Previous by thread: Re: MatrixMixer info
• Next by thread: Re: MatrixMixer info
• Index(es):
  • Date
  • Thread