Johannes Pohl

Yep, smells like an compatibility issue with webkit. I don't own any iDevices to fix this, so I've labelled this with "help wanted".

@sys-b @FredVDB Can you try the develop branch? Or extract this file [snapcontrol.js.zip](https://github.com/badaix/snapweb/files/5398126/snapcontrol.js.zip) and copy it to your `doc_root` (default should be `/usr/share/snapserver/snapweb/`)

Yes, this should be possible: https://stackoverflow.com/questions/4478271/remote-console-log-on-ios-devices The modified snapcontrol.js introduced an explicit event listener for the play button click event, as suggested on [stackoverflow](https://stackoverflow.com/questions/43389248/web-audio-api-not-playing-sound-sample-on-device-but-works-in-browser). Before it was a link to...

Can you please try again the develop branch or the attached [snapstream.js.zip](https://github.com/badaix/snapweb/files/5402302/snapstream.js.zip)? Snapweb is now falling back to `webkitAudioContext` if there is no `AudioContext`

The chrome log looks as expected, the audio player tries to fill the buffer before having received the first audio chunk. The TypeError should be fixed now, please try again....

So the error message disappeared, the `undefined` Base latency is used to calculate the play-out time. The latency is now set to 0 if undefined: [snapstream.js.zip](https://github.com/badaix/snapweb/files/5404365/snapstream.js.zip) Please also make sure...

Snapweb is using a triple audio buffer. When a buffer finished playing, it should fire an `ended` event, fetch new audio data and get queued for the next play back....

Sounds good :) If he needs any support, don't hesitate to contact me.

@inickt @FredVDB @sys-b I could reproduce the issue that `onended` is not called and no audio is played in [Epiphany](https://wiki.ubuntuusers.de/Epiphany/), which is based on WebKitGTK 2.30.3. I got it working...

Snapweb uses `BaseAudioContext.currentTime` to synchronize the playback. Maybe in Safari 14 the [time precision is reduced](https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/currentTime#reduced_time_precision), a log would help here.