Loke 4 Posted February 24, 2019 Posted February 24, 2019 (edited) OS: Debian 9.8 Emby: 4.0.2.0 Setup: Remote streaming (LE + HTTPS) This is a brand new install on a new ARM dedi. I uploaded a bunch of media from my home server and in all of the files, playback shows the file has a 3 sec duration. When it nears 2-3 sec it stops (buffers?), adds another ~3 sec in duration and on and on it goes. Going to the menu and restarting the playback on the files shows again 3sec. I tried scanning libraries, metadata: refresh all metadata & search for new and updated files, restart of emby, no dice Files are stored in a LV that is grouped under emby group with 775 permissions. No plugins added (initally I had added the Anime plugin but I removed it to make sure it wasn't that the cause). Apparently I did not do that, check post below. How should I proceed to debug this? Thanks Edited February 24, 2019 by Loke
Loke 4 Posted February 24, 2019 Author Posted February 24, 2019 (edited) Bump, after 1.5 days of the above, including today when I did the above tests again suddenly it has improved itself a bit. Now when it reaches the 3-4sec mark it increases duration to X min and after that in 2-3 steps to the full duration which at least doesn't stop the playback. Still re-accessing the file has the same result. Video example: https://streamable.com/ozwfx Edit: So I just experimented some more and apparently enabling Anime plugin causes only on Firefox the stream to be transcoded (cause is the container) which explains the 3 sec jumps. On mobile app it plays fine. Removing the plugin and restarting, the files direct play on both platforms. On the app it shows the full duration straight away, Firefox shows ~ 1-5min and increases it in steps quickly to the full length. Edited February 24, 2019 by Loke
Luke 42078 Posted February 24, 2019 Posted February 24, 2019 Hi, please try refreshing the metadata on one of these titles. If that does not pull in a runtime, then please attach the emby server log. thanks.
Loke 4 Posted February 24, 2019 Author Posted February 24, 2019 Hi, please try refreshing the metadata on one of these titles. If that does not pull in a runtime, then please attach the emby server log. thanks. It seemed to work at start but nope. I have pmed you the log.
Luke 42078 Posted February 26, 2019 Posted February 26, 2019 Ok i believe this is resolved for the next release. The fix will be on the beta channel within the next few days. You'll need to refresh metadata again on these titles. Thanks.
Loke 4 Posted February 26, 2019 Author Posted February 26, 2019 Ok i believe this is resolved for the next release. The fix will be on the beta channel within the next few days. You'll need to refresh metadata again on these titles. Thanks. It's a bug related to Firefox / web browsers? Any link for the relevant issue? So the version after 4.1.0.10 ? Thanks
Luke 42078 Posted February 26, 2019 Posted February 26, 2019 No it's related to the media probing process on the server. I'm not positive the very next beta will have the fix or not, but it will be soon. Thanks.
Loke 4 Posted March 3, 2019 Author Posted March 3, 2019 No it's related to the media probing process on the server. I'm not positive the very next beta will have the fix or not, but it will be soon. Thanks. What exactly am I looking for in the change-log so I know that the current beta includes the fix?
Luke 42078 Posted March 5, 2019 Posted March 5, 2019 The latest betas should have it at this point. Please try refreshing metadata on one of these titles. If there is still an issue, please attach the emby server log. thanks !
Loke 4 Posted March 5, 2019 Author Posted March 5, 2019 (edited) The latest betas should have it at this point. Please try refreshing metadata on one of these titles. If there is still an issue, please attach the emby server log. thanks ! Works 98% fine. On the files I had and refreshed worked fine but on some new files I added (after the beta upgrade and library scan to replace all metadata) on at least one of them I had to refresh metadata. At least I think so, hence the 98% !! Thanks for the fix and hope we get a new stable soon. Btw to hijack my own thread, is there an option so emby denies transcoding at all? and posts a cannot playback since transcoding is required? (I use an arm cpu so direct stream is A OK but transcoding ...) Since I doubt there is any point on requesting it or it won't be added due to niche? Edited March 5, 2019 by Loke
Luke 42078 Posted March 6, 2019 Posted March 6, 2019 Yes there is. Have you explored user permissions?
Loke 4 Posted March 6, 2019 Author Posted March 6, 2019 Yes there is. Have you explored user permissions? Apparently not! And there is a lot of stuff in there that is quite interesting. Thanks for the pointer. Correct me if I am wrong "Allow video playback that requires conversion without re-encoding" This is pretty much changing container? So it falls under Direct Play right? So un-checking only: Allow audio playback that requires transcoding & Allow video playback that requires transcoding should suffice.
Luke 42078 Posted March 7, 2019 Posted March 7, 2019 Correct, but if you start having playback problems then you will need to allow those things again. Emby apps should already be direct playing whenever possible.
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