No audio playback in Chrome

[thomasdeppisch]

Hi,

Thanks for the great work on Earshot!

When I use OBS Music Edition and Earshot everything works as expected in Firefox. Unfortunately audio playback does not seem to work in Chrome. The video is displayed but there is no audio. The DASH Stream Info also looks fine. I tested this using the 16chambixloop.wav from the repository and the webtools page.

Are you aware of this behavior? Does this have to do with the HTTPS requirement of Chrome you describe in the readme?

Edit: I'm on Chrome 88.0.4324.192 and macOS 11.2.2

[roddylindsay]

Hey Tommi,

Is this with local deployment or on AWS?

If on AWS, can you try wrapping with a CDN and see if that works on Chrome?

[thomasdeppisch]

Hi Roddy,
I experienced this with local deployment. (I basically only started the docker container and opened the webtools in Chrome.)

[roddylindsay]

Do you get any JS errors?

…

On Tue, Mar 2, 2021 at 10:17 AM Thomas Deppisch ***@***.***> wrote: Hi Roddy, I experienced this with local deployment. (I basically only started the docker container and opened the webtools in Chrome.) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJWC3XKUOBILIZ7TTIJAUDTBUTUXANCNFSM4YOPVL7A> .

-- "Buy the ticket, take the ride."

[thomasdeppisch]

No errors, I only get the warning that the audio context can't start without user interaction, but that's the same on Chrome and Firefox and I don't think that's the reason. (Actually I don't think it is the reason because I experience the same problem when using Earshot with HOAST: On Firefox it works nicely and on Chrome there is no sound. An for HOAST I took care of the context user interaction procedure.)

[roddylindsay]

Yeah, I think this might be an issue with webtools on Chrome specifically since Chrome is stricter about autoplay (seemingly recently as this worked on Chrome as recently as the fall) Have you tried just using the MPD in a different web app that requires user interaction i.e. within HOAST?

…

On Tue, Mar 2, 2021 at 10:37 AM Thomas Deppisch ***@***.***> wrote: No errors, I only get the warning that the audio context can't start without user interaction, but that's the same on Chrome and Firefox and I don't think that's the reason. (Actually I don't think it is the reason because I experience the same problem when using Earshot with HOAST: On Firefox it works nicely and on Chrome there is no sound. An for HOAST I took care of the context user interaction procedure.) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJWC3WJKSGXM3MNY6FZL3TTBUV4XANCNFSM4YOPVL7A> .

-- "Buy the ticket, take the ride."

[thomasdeppisch]

Yes, like I said when I used Earshot with HOAST I did not get any sound in Chrome, that's why I think it's not a problem with the autoplay...

[roddylindsay]

What URL are you using for the MPD? HTTPS or HTTP?

…

On Tue, Mar 2, 2021 at 10:44 AM Thomas Deppisch ***@***.***> wrote: Yes, like I said when I used Earshot with HOAST I did not get any sound in Chrome, that's why I think it's not a problem with the autoplay... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJWC3Q3XI4G7OHT6AEOVALTBUWX3ANCNFSM4YOPVL7A> .

-- "Buy the ticket, take the ride."

[thomasdeppisch]

Only used HTTP so far. Does Earshot also provide an HTTPS link? (I think you would need certificates for that, correct?)

[roddylindsay]

Chrome doesn't like MPEG-DASH over HTTP. There's a bug in the HTTPS cert code which we will look at and fix. But in the meantime you can use a CDN like Amazon Cloudfront which will put an HTTPS wrapper around an HTTP origin.

…

On Tue, Mar 2, 2021 at 10:49 AM Thomas Deppisch ***@***.***> wrote: Only used HTTP so far. Does Earshot also provide an HTTPS link? (I think you would need certificates for that, correct?) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJWC3V6EAYV4JI3UDS6FH3TBUXKTANCNFSM4YOPVL7A> .

-- "Buy the ticket, take the ride."

[thomasdeppisch]

Yes, I wondered if that's the problem. Thanks for the quick response!