Spatial audio doesn't work in iOS12.01 safari

[KeiNitta]

Hi.
I tried resonance Audio SDK for web in (iOS12.0.1/safari & OSX10.13.6/safari) . But it did't work at all.
Official Web sample didn't play any sound in this environments.

In iOS11.2.5, it seems to work well. Would anyone tell me this reason?

[hoch]

Just to clarify:
Safari on iOS 11.2.5 = Working
Safari on iOS 12.0.1 = Not working
Safari on OSX 10.13.6 = Not working

Do you see any error messages in the developer console?

[KeiNitta]

@hoch Thank you for reply.
In iOS 12.0.1 and OSX10.13.6, Hello world Demo show these message when push play button. There was nothing error message.

[Log] [Omnitone] Version 1.0.6 (running Safari 12.0.1 on Mac OS X) (@144.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] Safari detected. Appliying polyfill... (@144.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] FOARenderer: Initializing... (mode: ambisonic) (@280023.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] BufferList: 2 AudioBuffers from Base64-encoded HRIRs loaded successfully. (@280231.00ms) (resonance-audio.min.js, line 166)
[Log] [Omnitone] FOARenderer: HRIRs loaded successfully. Ready. (@280232.00ms) (resonance-audio.min.js, line 166)

[hoch]

I think this is related to CORS issue. I am seeing the same problem when I run Omnitone example:
https://rawgit.com/GoogleChrome/omnitone/master/examples/foa-renderer.html

MediaElementAudioSource outputs zeroes due to CORS access restrictions for https://rawgit.com/GoogleChrome/omnitone/master/examples/resources/4ch_B_FuMaNorm_FuMaOrd_speech.wav

At least Chrome Canary (72.0.3599.0) produces this error, so I can track it from there.

[ubershmekel]

I can confirm:

• https://cdn.rawgit.com/resonance-audio/resonance-audio-web-sdk/master/examples/room-models.html does not play any sound with Chrome 85.0.4183.109 on iOS 14.0.1.
• When I download this repo, and host it all locally, the audio does play and the demo works. Though there is some audible noise. It seems somewhat rhythmic, so perhaps it's a buffer issue.

To summarize - this issue is definitely caused by CORS. But there might be more problems too.