Research (Chromium) autoplay policy #Help
-
Hi all,
Hope you're well
Thanks for software
Today I have a problem with autoplay in the latest version (i.e. 2.0.1309.29 (Stable channel) (64-bit))
https://player.fm/series/watershed-podcast-1603913/october-2018-cinema-podcast - this podcast episode should play automatically but it doesn't. Even when I click to play I see console errors, notably:
Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22
... which I suspect is related to Chromium's autoplay policy[y] change(s)
Aside, can anyone confirm when this feature/policy changes reached Vivaldi?
However, my suspicions seems wrong because experimentation with the following flags has no effect:
vivaldi://flags/#autoplay-policy
vivaldi://flags/#enable-autoplay-ignore-web-audioCan anyone else reproduce my issue?
If you have any issues (e.g. questions/queries) happy to help
Hope to hear back
Keep up great work!
Cheers
[y] https://developers.google.com/web/updates/2017/09/autoplay-policy-changes
-
BUMP BUMP
ModEdit: Please, don't do that.
-
@ldexterldesign said in Research (Chromium) autoplay policy #Help:
BUMP BUMP
ModEdit: Please, don't do that.
Better quote, just in case.
-
@ldexterldesign Sorry for the late reply to your post. The problem autoplaying this podcast is not the the status of the
#autoplay-policy
flag itself; if you set the flag to "No user gesture is required." it should work. Rather, the problem is playing the watershed-cinema-podcast_2018_10.m4a file itself. It contains chapter marks and embedded artwork, it plays fine in Safari, but it looks like it's causing a renderer crash when I try to play it in Vivaldi on macOS.I'll file a bug for this.
-
Hi @xyzzy,
Thanks for reply
Glad to know the reason
Regarding the bug - unsure of the severity - what's a realistic fix timeframe (e.g. days/week/months/years), so I know when to follow up?
Hope to hear back
Cheers
-
@ldexterldesign My guess is that it probably won't take too long to fix but I can't say for sure. I only just just just filed VB-45871... and it's still early morning (Oslo time) so the Vivaldi team has not even had an opportunity to even confirm the bug yet.
-
Hi all,
What's the status?
Hope to hear back
Yours hopefully
-
@ldexterldesign Thanks for asking... I don't know why this hasn't been fixed already. I've reconfirmed the broken media playback (and renderer crash) with the latest 2.5 build and am doing what I can to get this assigned to a developer.
-
-
@ldexterldesign I'm not 100% sure but I think it's a different issue. Unfortunately, I don't have time to debug this at the moment. The broken podcast in your initial post was an "enhanced podcast" and Vivaldi choked when it tried to play it. This looks like it's just a normal/simple podcast but Vivaldi only let me download the .m4a file and when I tried to play it, Vivaldi opened the file with iTunes.
The same podcast at https://anchor.fm/bit-v-byte/episodes/Traefik-2-0--Powershell-7--VS-Code-1-33--Grafana-6-1-and-More-Resources-e3m38s plays fine for me in Vivaldi.
-
@xyzzy unsure what expected behaviour is but neither of the feed audio files stream natively in the browser for me:
https://apps.watershed.co.uk/shared/uploads/wvs/audio/19/04/watershed_2019_04.m4a
https://anchor.fm/s/398b338/podcast/play/2869980/sponsor/acs8i0,acs9h0/https%3A%2F%2Fd3ctxlq1ktw2nl.cloudfront.net%2Fstaging%2F2019-3-8%2FTraefik-2-0--Powershell-7--VS--d5348dfdad988.m4a... which suggests an .m4a container issue
Perhaps https://anchor.fm/bit-v-byte is doing some routing because it's unclear what file type https://anchor.fm/bit-v-byte/episodes/Traefik-2-0--Powershell-7--VS-Code-1-33--Grafana-6-1-and-More-Resources-e3m38s is using
Regards
-
@ldexterldesign Could you please open a simple bug report saying that the podcast does not play in Vivaldi but the site works fine in Safari and Chrome? I'll confirm it and the Vivaldi team can then investigate further. Thanks!
-
-
FYI plays in macOS Safari and Brave (Chromium-based), but not Chromium, so unlikely a macOS-specific issue. More likely a container/codec support issue.
Hope this helps
Regards
-
FYI All good now - computers!
Hope this is useful
Regards
-
-