Page 2 of 2

Re: VST3 HOA Support > 3rd order

Posted: Fri Apr 03, 2020 3:47 pm
by Stefan
Arne Scheffler wrote:
Fri Apr 03, 2020 2:47 pm
Hi Stefan,
please describe what you mean with "flexible audio channel layout description like in Audio Units", thank you.
Hi Arne,
I would appreciate to get a layout description consisting of channel labels instead of just an index to predefined ones (same for set, of course).
So basically a vector of audio channel descriptions.

Re: VST3 HOA Support > 3rd order

Posted: Wed Apr 08, 2020 12:54 pm
by olilarkin
Would it be possible to add an option for just N discreet channels? I.e not specify an ambisonic bus? I think this is what most developers of multichannel plugins would appreciate

Re: VST3 HOA Support > 3rd order

Posted: Wed Apr 08, 2020 1:33 pm
by Stefan
Sometimes it is good to know what the channels are, e.g. you may want to know what the lfe is if only in order to ignore it.

Re: VST3 HOA Support > 3rd order

Posted: Thu Apr 09, 2020 9:20 am
by charlifiiiii
Would IExtendedSpeakerArrangement be equivalent to the VST2 behavior ?

Using VST2 and Juce, we used to declare a number of supported in/out configs, specifying only the number of channels, e.g., {2, 2}, {1, 2}, {6, 2}, {6, 6}...
Then the user could choose his loudspeaker layout directly in the plugin. That worked fine basically.

Would be nice to have a simple interface like this in VST3.

Thanks,

Charles

Re: VST3 HOA Support > 3rd order

Posted: Fri Apr 10, 2020 9:59 am
by angelo.farina
olilarkin wrote:
Wed Apr 08, 2020 12:54 pm
Would it be possible to add an option for just N discreet channels? I.e not specify an ambisonic bus? I think this is what most developers of multichannel plugins would appreciate
I second this entirely. Multichannel audio is not limited just to Ambisonics, we have now other competing formats such as Spatial PCM Sampling (SPS, aka Mach1), T-design geometries (T-format), MPEG-H, Dolby Atmos, etc.
Also the maximum number of channels should be unlimited: in Wave Field Synthesis it is common to use systems with 128 or even 192 channels. We have a WFS room here in Parma, Italy, inaugurated in 2008 (12 years ago) equipped with a single computer driving 192 channels. The WFS rendering cannot actually be done with a VST3 plugin, simply because the VST3 format does not allow for such channel number, whilst the host program (Plogue Bidule) has no problem managing the RME MADI interface providing them.
In some of these formats, such as MPEG-H and Dolby Atmos, we get a mixture of "loudspeaker" channels in fixed positions and a potentially large number of "sound objects", which are mono tracks encoding sound sources moving around.
In some other cases, each of these moving sources is Ambisonics-encoded (perhaps just at first or second order) or SPS-encoded, representing the directivity of the sound source with a number of channels, which can then be moved in space and oriented in space (6DOF rendering).
In conclusion, what would be important is to allow for maximum flexibility, both on channel number and channel labelling.
Sticking to a reduced set of predefined "speaker layouts" is something which brings all us back by 20 years.
So Please Steinberg, remove all these limitations form the VST3 SDK...

Re: VST3 HOA Support > 3rd order

Posted: Fri Jun 12, 2020 6:24 pm
by PeterStitt
I'd like to voice my support for the approach Oli and Angelo mentioned. It would make things a lot more flexible and allow a lot more formats to be supported.

Re: VST3 HOA Support > 3rd order

Posted: Mon Jul 13, 2020 6:11 pm
by mwilga
I would also like to request N discreet channels