Ryogo 0 Posted July 28, 2017 Posted July 28, 2017 Playback is not working in FF/Chrome. The issue persists from 22 version (first version I installed) through 26 version (latest). Note: playback works in incognito mode both in FF and Chrome.
Luke 42085 Posted August 4, 2017 Posted August 4, 2017 hi @@Ryogo, can you reproduce this using the online web app at http://app.emby.media ? Thanks !
Ryogo 0 Posted August 4, 2017 Author Posted August 4, 2017 Hi, @@Luke It works as it should using http://app.emby.media
Ryogo 0 Posted August 4, 2017 Author Posted August 4, 2017 @@Luke Do you have any ideas at where I can look at to diagnose/fix the issue?
Luke 42085 Posted August 4, 2017 Posted August 4, 2017 Was there anything more in the browser debugger?
Ryogo 0 Posted August 4, 2017 Author Posted August 4, 2017 @@Luke no, nothing at all. You could check it yourself if you have time. log with error: https://pastebin.com/AVVR0NKd log without error: https://pastebin.com/J2AxW035
Luke 42085 Posted August 4, 2017 Posted August 4, 2017 Ok. Please try again with the next release of Emby Server. Thanks.
Ryogo 0 Posted August 4, 2017 Author Posted August 4, 2017 @@Luke Sure, thank you. I'll report back when next release will be out.
bfir3 117 Posted August 15, 2017 Posted August 15, 2017 This is the reason I'll never turn on automatic updates. I couldn't imagine updating to a version that loses complete playback functionality for users with specific browsers. That's gotta be frustrating, I hope the issue gets resolved quickly.
Ryogo 0 Posted September 21, 2017 Author Posted September 21, 2017 @Luke Updating to 31 version does not helped, but anyway - I've tracked down the issue. It is in htmlvideoplayer/plugin.js in createMediaElement method. videoElement.volume = htmlMediaHelper.getSavedVolume() this is the line that causing a problem. videoElement.volume expects value from 0 to 1, but htmlMediaHelper.getSavedVolume() returns 50 and setting 50 to videoElement.volume is causing exception to be thrown.
Solution Luke 42085 Posted September 21, 2017 Solution Posted September 21, 2017 Thanks for the info. Try clearing browsing data. I think what is probably happening is you have an old value saved in your browsing data on a 0-100 scale. The newer code saves it as 0-1. Thanks. 1
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