ezzah 3 Posted March 31, 2020 Share Posted March 31, 2020 I would preface this by saying that this was experienced by one of my users. I have looked through embyserver logs and transcode/remux logs but could not find anything of note. However, the user did find that in console this error would appear when the playback would pause and could not be resumed: Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22 Any thoughts what this javascript error may mean? Is it a client-side issue? 1 Link to comment Share on other sites More sharing options...
Luke 37060 Posted March 31, 2020 Share Posted March 31, 2020 Hi there, can you attach the complete console contents? Thanks. Link to comment Share on other sites More sharing options...
aplusm 1 Posted April 1, 2020 Share Posted April 1, 2020 Hi Luke, I experienced this particular promise exception in Chrome, but didn't get a chance to capture a screenshot when playback stopped. I did experience the 'random pause in playback' again, but this time on Safari, in the console, the logs were a bit different. I thought may still be relevant to trying to fix this problem, could be different factors but producing the same outcome of stopped playback I'll keep an eye out for more of these client-side console logs whenever this happens. Link to comment Share on other sites More sharing options...
Luke 37060 Posted April 2, 2020 Share Posted April 2, 2020 Can we go over an example of what you're playing? thanks. Link to comment Share on other sites More sharing options...
aplusm 1 Posted April 4, 2020 Share Posted April 4, 2020 (edited) I just encountered this error just now, and managed to grab a screenshot, as well as the full browser console logs. See attached below. System Info:- Browser: Brave v1.15.15 (Chromium-based browser)-- Only active extension for Emby app is 1Password. I disabled any uBlock Origin & Brave Shield (adblockers) when I started encountering these issues.- OS: macOS 10.15.4- Hardware: Macbook Pro 13-inch (Retina, Early 2015) Here's exactly how it unfolded:I was watching Supernatural S13E09, and at minute 39:31.. the playback suddenly stopped. When I hovered to check, the play button was toggled (as if it got paused). I immediately grabbed a screenshot, and copied the full log which should show the log since I opened the web app.At the timestamps where the playback stopped (towards end of the log), I can see those "bufferStalledError" and "bufferFullError" errors I captured before.. and when I tried to press 'play' again, to try to see if it will resume.. I got the 'uncaught promise DOM exception' error that @@ezzah posted. The playback never resumed obviously, regardless of how long I wait. emby_console_masked.txt Edited April 4, 2020 by aplusm 1 Link to comment Share on other sites More sharing options...
Luke 37060 Posted April 5, 2020 Share Posted April 5, 2020 OK i guess we'll have to do some brave testing. Thanks for reporting. Link to comment Share on other sites More sharing options...
aplusm 1 Posted April 6, 2020 Share Posted April 6, 2020 (edited) I just wanted to clarify on the browser part. I encountered this problem on BOTH Safari and Brave, not exclusively Brave. You'll see in my post #3 that the screenshot of a similar error in the console, is in the Safari Console viewer. So the problem (and the exact error) I encountered was on both Safari and Brave.. I just happened to be using Brave when it happened again, and managed to get you the full logs I'm using the latest Safari 13.1 on macOS 10.15.4 Catalina FYI I have started using Firefox today, and will see if I encounter it on Firefox as well. Edited April 6, 2020 by aplusm Link to comment Share on other sites More sharing options...
Luke 37060 Posted April 6, 2020 Share Posted April 6, 2020 Ok great, thanks for the info. Link to comment Share on other sites More sharing options...
legionsra 0 Posted August 11, 2020 Share Posted August 11, 2020 (edited) Regarding this issue I have it always if my bitrate is 40Mbps or higher, no matter the resolution. It happens for now in my case only in Chrome with Mac (Mojave) in just a few seconds, while in Safari and Firefox (again, Mac Mojave) seems to be capable of long runs 4k 120Mbps with no issue. It seems that there are some buffer issues with the HLS.js used to process the data depending on the combination of browser/OS. My recommendation is that we should try to use other browsers meanwhile as a workaround in Mac (and also in other OS if this happens there) and also update Emby periodically with the latest versions of HLS. You can see these bugs notified already in the HLS sidehttps://github.com/video-dev/hls.js/issues/1084 TL;DR: Workarounds 1. Reduce Mbps bitrate in your browser. 2. Use another browser and/or OS if you can, try max Mbps and then reduce until it works flawlesly 3. Wait HLS and Emby team for updates. Edited August 11, 2020 by legionsra Link to comment Share on other sites More sharing options...
Luke 37060 Posted August 11, 2020 Share Posted August 11, 2020 The next release of the server will contain a newer version of hls.js. Thanks. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now