iOS not playing

[sys-b]

Under iOS the controls are working fine. Just like the desktop.
But the client is not playing. It is displayed linke on the desktop, but no audio is played.
Tried in Chrome, Safari, Firefox and even Opera.
The iPad-chrome-console output after while pressing play:

[badaix]

What iOS version is your iPad running on? Have you tried playing audio on an iPhone? Here they say that on iOS 10.1.1 the web audio API is not working: https://developer.apple.com/forums/thread/48815

This was fixed in the second build of iOS 10.1.1. iPad now plays Web Audio API again, but didn't from 9.3.2 to the first build of 10.1.1. Thanks.

[sys-b]

It is an iPad Pro. Running iOS 14.0.1. Same as an iPhone 11 Pro Max. Also Not Working. On the current iMac it only works in chrome also, Not in safari.
Maybe an webkit Issue.?

[badaix]

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".

[badaix]

@sys-b @FredVDB Can you try the develop branch?
Or extract this file snapcontrol.js.zip and copy it to your doc_root (default should be /usr/share/snapserver/snapweb/)

[FredVDB]

Still no audio with the modified snapcontrol.js. Is there some way to get logging info ?

[badaix]

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. Before it was a link to a java script function.
I think without having an iOS device, I'm out for now :(

Did you restart the snapserver after copying the file? The server doesn't cache (refreshing the browser should be enough), but who knows.

[sys-b]

Hi.
I just pulled the development branch, make, replaced the folder, restart service.

It seems to behave like before. In Chrome on iPadOS 14:

Also interesting is, that it isn't working in Safari on the recent iMac and recent OS:

Hopefully this will help.

[badaix]

Can you please try again the develop branch or the attached snapstream.js.zip?
Snapweb is now falling back to webkitAudioContext if there is no AudioContext

[sys-b]

No sound but different errors. On both devices:

In Chrome on the iMac the sound still works. But the Failed to get Chunk error appears 3 times. I didn't saw that before, I think...

[badaix]

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. Mühsam nährt sich das Eichhörnchen...
snapstream.js.zip

[sys-b]

I am happy that we are going to figure it out.
But still sound. This time same log results on Safari MacOS and Chrome iPad:

Wer im Glashaus sitzt, fällt selbst hinein.

[badaix]

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
Please also make sure that you're not muted: https://stackoverflow.com/questions/21413396/simple-oscillator-but-no-sound-with-web-audio-api-on-ios

$10 says your mute switch is on. For whatever reason, Safari won't play sound when the mute switch is engaged, but Chrome will. Other than that, Chrome uses the same engine as Safari to render your page (minus the Nitro JS optimizations), so there's no other reason that your code should work in one but not the other. I just tried it via JSBin, and both worked for me when the mute switch was off. –

[sys-b]

The iPad doesn't have a mute switch. Other websites like YouTube work. On the iPhone with mute off also no sound.
I am not sure if it is clear, that the last message on the console is the last one. On a working Browser there are coming a lot with age: and others messages.

I had once problems with video html5 elements. They had to be muted if not, the element wasn't playing automatically.
I'm starting to think this is more a communication thing than an output thing. Is it possible to use a dummy output maybe ?
Anyway I am not into any JS or TS at all.

Gute Nacht.

[badaix]

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. Here the ended event seems not to get fired and thus the whole logging stops.
One more attempt with a different ended callback handling: snapstream.js.zip