Ambisonic Audio working on PC but not Android

I am trying to get an ambisonic wav file to play through an audio source in my Gear VR application.

I have tried the default method: Setting the spatializer plugin to OculusSpatializer and the ambisonic decoder plugin to OculusSpatializer then enabling the ambisonic property on the 4 channel wav file before putting it onto an audio source.

I have also tried the Oculus method: downloading the Oculus spatializer plugin, set the spatializer plugin and ambisonic decoder to OculusSpatialzier, enabled the ambisonic property on my file, attached the ONSP Ambisonics Native script to my audio source then set the output of that audio source to SpatializerMixer > Master.

I have also tried the Google method: downloading the Resonance plugin, set the spatializer plugin and ambisonic decoder to Resonance Audio, enabled the ambisonic property on my file and set the output of my audio source to ResonanceAudioMixer > Master.

All three methods produce the same result, on PC the ambisonic effect works fine but once I build the app and run it on Gear VR the audio seems to be ambisonic but the directions are all messed up.

I’m thinking this is an Android issue.

Does anyone have any clues on what might be going on and can point me in a direction to solve this issue?

I have the same issue, did you find a fix for this?

I contacted Unity some time ago about this problem and they confirmed that the Issue is a bug with their latest versions of Unity 2017. I found that using an older version of Unity (I believe 2017.1 and earlier) or 2018.0 (beta at the time) solved the problem. Forgive me if any of my information is incorrect or outdated as it has been a few months since I ran into this problem. Hope its helps!

Hi there

So the note about ambisonic’s not working in
“Note: Ambisonics do not work in any other version of Unity other than the Unity 2017.1 beta.”

https://developer.oculus.com/documentation/audiosdk/latest/concepts/ospnative-unity-ambisonic/

Is that still valid as I would imagine that it should be working in 2018?

Cheers
Brian