Quote:
Originally Posted by sstillwell
Do any of these I/O string variations cause issues with AUs? Those strings get reported to the host (unless we reformat/sanitize them)...hosts won't understand our variations, will they?
|
They don't get reported directly, even though they are similar to what you see in auval... the string is parsed in IPlugBase::IPlugBase() and in IPlugAU::IPlugAU() a BusChannels struct is set for each input and output bus. The host queries the kAudioUnitProperty_StreamFormat property which reports the audio stream format for the specified bus. It's not quite that simple though, Schwa seems to have worked out how audiounits work under the hood, and bypassed a lot of the Apple base classes...which makes it quite hard to understand because even if you use the apple base classes the documentation is pretty weak on this stuff.
I think a channel IO string where dots delimitate buses might be OK, like
"1-1 1.1-1 2-2 2.2-2" = mono - mono (+ optional mono sc) or stereo - stereo (+ optional stereo sidechain)
"0-2 0-2.2 0-2.2.2 0-2.2.2.2" = up to 4 stereo output buses