mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #898] No sound with Chrome >=71 #589
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#589
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ynizon on GitHub (Jan 20, 2019).
Original GitHub issue: https://github.com/koel/koel/issues/898
Hi,
All works good in Firefox, but when i click on a music with Chrome, i cant show the progress bar, and i cant listen it.
Chrome console show more than 20 warnings like this:
Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952 on
/public/js/1.d474316446e507c851d5.js
I dont know where i can add the passive instruction or where is the no minify file.
Maybe you know. Good luck
@phanan commented on GitHub (Jan 22, 2019):
What's your OS? I'm using Chrome 71 on Mac Mojave without any issue.
Edit: The warnings shouldn't have anything to do with the issue.
@vesper8 commented on GitHub (Jan 23, 2019):
was just having the same issue on Chrome, then as I tried to open it in Firefox I realized I was running into the 'out of memory' exception due to the media caching and a big library (only 8500 songs)
After disabling the media caching in env and restarting the serving process after clearing the config cache. Songs now play in Chrome so maybe try that out @ynizon
@ynizon commented on GitHub (Jan 27, 2019):
It's very strange. I logout, then i log again and it works on Chrome also.
I make F5, then i have the same error. I need to logout then login to correct it.
I dont know if the bug need to be fixed or not. Maybe others persons have this ?
@vesper8 commented on GitHub (Jan 27, 2019):
I'm experiencing the same thing. I thought I had resolved it as mentioned above, but then I noticed it stopped working. And then it worked again
@kellertobias commented on GitHub (Jan 28, 2019):
Same thing. also works after re-login, but not on f5 or session resume.
Getting the console error:
@phanan commented on GitHub (Jan 28, 2019):
Hmm, this indeed looks like the new audio policy coming with Chrome. I'll take a look later.
@phanan commented on GitHub (Jan 28, 2019):
But then again, I'm not sure how to reproduce this. The problem doesn't occur with my setup.
@ghost commented on GitHub (Feb 8, 2019):
Have totally the same problem in Chrome on my mobile. I have to re-login to fix it.
@donghaoren commented on GitHub (Feb 10, 2019):
@phanan With the new policy, there is a media engagement score (you can see it from here: chrome://media-engagement/). This score increases when you interact with the website. If the score is high enough, chrome will allow passive playback. That's probably why you are not getting the issue.
You can find the details here: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes under the "Media Engagement Index (MEI)" section.
I had this issue today after updating chrome, then I tried refreshing the website many times, each time I clicked the play button on some random songs. After repeating this around 10 trials, it starts to play!
To reproduce this, maybe you can try resetting the media engagement score? (see https://stackoverflow.com/questions/50683830/reset-chrome-media-engagement-score for example)
@phanan commented on GitHub (Feb 18, 2019):
@donghaoren Interesting, thanks for the links. Now I'm wondering what the fix/workaround should be (it's not very clear in the articles, or maybe it's because I was just skimming through them).
@phanan commented on GitHub (Feb 18, 2019):
Btw I tried resetting the MEI by opening a guest window – still couldn't reproduce the issue.
@VirtusB commented on GitHub (Feb 24, 2019):
You can go to chrome://flags/#autoplay-policy and disable it completely, I just did and now it plays. But the progressbar still doesn't work, it just shows "aN:aN"
@donghaoren commented on GitHub (Feb 24, 2019):
I solved this by enabling the "Sound" option in the "Site Settings" (you can bring it up by clicking the icon before the url), without having to worry about the MEI score. This seemed to be more specific than disabling the autoplay policy entirely.
@VirtusB commented on GitHub (Feb 24, 2019):
@donghaoren Yes, that also fixes the sound problem. Is the progressbar working for you?
@donghaoren commented on GitHub (Feb 28, 2019):
@VirtusB the progressbar works fine for me
@phanan commented on GitHub (Mar 17, 2019):
Fixes in the latest commit. Can you guys confirm?