21 karma · joined August 16, 2017
Thanks for expressing your interest in using Resonance Audio SDK for the Web (formally Songbird). We don't currently offer a 5.1 rendering of the audio as an available option. However, we do offer .ambisonicOutput which outputs ambisonic content directly and this can be rendered to a 5.1 target using 3rd party tools (http://www.radio.uqam.ca/ambisonic/b_g.html). If we see a large need for 5.1 rendering, it may be worth considering posting an issue to Omnitone (https://github.com/GoogleChrome/omnitone/issues) which is our ambisonic renderer on the web. :)
Cheers, Drew
I'm aware of the issue and I hope to have it resolved within the day. :)
Cheers, Drew
Thanks for your interest! Let me try to clarify and answer your questions:
1. Songbird is indeed an enhanced alternative to PannerNode.
2. It internally works with ambisonics, but outputs stereo (we use Omnitone internally to render the multichannel audio down into a stereo track).
The general reason people use ambisonics instead of direct HRTF rendering is because ambisonics allows for head rotation prior to rendering, so the user can easily turn their head, etc. without you having to adjust all the incoming sources' hrtfs.
The reason we feel Songbird is an upgrade to PannerNode is three-fold:
One, you can control the quality of the localization/spatialization effect by adjusting ambisonicOrder (1st to 3rd, atm).
Two, PannerNode is costly... 2 convolutions per source, while songbird is a fixed number of convolutions irregardless of the number of sources, so it ends up allowing you to get more for less.
Three, PannerNode doesn't support any sort of room modelling and Songbird produces spatialized (ambisonic) room reflections and reverberation.
Hope this helps clarify things! :)
Cheers, Drew
Songbird renders stereo-out using Omnitone internally, so Android/mobile is certainly supported. Feel free to file any issues you have at https://github.com/Google/songbird/issues.
Cheers, Drew