11
Support - (fb2k) / Re: [BUG?] Foobar fails to function with Windows Sonic, why?
Last post by Case -Sorry for being a bit slow tonight, but is your response above saying that foo_out_spatial incorporates normal multichannel support (like foo_out_xaudio2 once included Spatial Output capability), and foo_out_xaudio2 is therefore not needed?XAudio2 output is a entirely different, it for example will happily take up-to 64 channel input. It may not play such audio correctly as there are no defined channel mappings for these, but at least it will audibly play something. And I already replied earlier that it could be useful for Wine people who want to try to avoid resampling.
So it's also a whole different API as well?Yeah, there are plenty of different ways to play audio on Windows.
What happens when I use this output, but I have the Windows spatial audio feature disabled?
With Spatial disabled the playback should match WASAPI shared mode pretty closely. With the exception that spatial engine seems to have its own sampling rate. So if your Windows mixer is not running at the spatial mixer's sampling rate, there will be extra resampling step before the windows mixer gets the signal.
At least on my machine the spatial engine only reports one supported input type: 48 kHz 32-bit floating point input.
I made foo_out_spatial report the engine's supported audio formats on first device open. If there are multiple supported formats it should print a list of them all.
The documentation for this API seems very lacking and at least Microsoft's github has some incorrect information.