Emby stops at 55 min mark

[Coolegb 0]

Hey,

 

My Emby player, playing on the server stops always near the 55 min mark and shows a black black screen , I've to go back and start play the video you again it.

 

How can i fix that ?

 

[Wondertje 10]

Is it the 55 minute mark of all videos or just of videos that are nearing the end around there?

 

There have been several similar reports before, here among others.

 

https://emby.media/community/index.php?/topic/73883-episodes-cut-off/

 

https://emby.media/community/index.php?/topic/69866-jump-of-images-blackscreen-during-the-playback-of-the-video-at-the-end-only/

 

https://emby.media/community/index.php?/topic/73373-not-playing-till-the-end-of-file/

 

It appears to be a rather wide spread non-distinct issue,which I believe they're working on hunting down. If you want to add to it, I suggest you add logs from when this is happening so that they can check those for anomalies.

[theghost31 4]

@@Coolegb, please attach the logs as @Wonderdertje suggested you

Follow this link : https://emby.media/community/index.php?/topic/790-how-to-report-a-problem/?view=getnewpost

 

And yes it's seems to be the same issue. Are you using a browser to read movies with emby ? Under Windows? Linux? What browser?

 

Thanks

Edited June 9, 2019 by theghost31

[Coolegb 0]

Hi @@theghost31 and @@Wondertje

 

I've attached my server and ffmeglog file, and I do play through my browser

Google chrome Version 74.0.3729.169 (Official Build) (64-bit)

Window 10

 

anymore info i need to provide

ffmegLog.txt

serverLog.txt

[theghost31 4]

OK thank you.For your personal info, You're running on the latest stable version and not beta, so sometimes you can missing latest fixes .

 

That will be @@Luke who can read these logs. I'm not a dev on this project .

I can see some 'port mapper' error. I'm not sure what this error represents but Luke will know.

BTW,to help them, May I suggest to give the date and time where you find the issue (blackscreen) next time ? I can see 3 days of logs here.

Edited June 10, 2019 by theghost31

[Wondertje 10]

I too cannot read logs that well, so I won't even try. I can tell you this though: you're not running the latest Chrome update, so you should fix that. It might not (probably won't) fix the problem, but it's one less thing to worry about.

[pwhodges 2014]

I just had another occurrence of this (first for a while).  I was playing an episode, but had been jumping about a bit near the end to find a particular scene, which clearly confused the buffering a couple of times.  But after a slightly longer uninterrupted play, it stopped dead with a black screen, and the control buttons on the display became unresponsive.  I know that the back button will get out of this, but I captured the logs before doing that.  The crash is at 21:44 of a 24:00 episode (well, 21:44 is shown on the client display, but the console says it's at 21:50).  The data was being directstreamed to the webapp in Opera on Windows.  The version of the Emby server is 4.2.0.11.  I had earlier watched the whole episode without a crash, but that was on an Android client.

embyserver.txt

ffmpeg-directstream-8ecc26a1-d3d7-4831-a23a-02a71f743621_1.txt

[theghost31 4]

@@pwhodges, we have exactly the same issue and usecase. Since a recent beta version, on android, I didn't have any issue as you mentioned.

 

On Windows and Linux browsers, it's not the same thing and yep you get a blackscreen but the console continues to read but you can't see anything on your browser. Sometimes if you wait a long time, you get something like --:-- as duration in the Admin console and the episode will fake a restart from the begin always visible in console.

But in opera / chrome browser, nothing will move, Always blackscreen exactly at the first duration where its happening.

 

Thanks for the logs

Edited June 11, 2019 by theghost31

[pwhodges 2014]

I have in the past had similar hangs near the end using both Android and iOS clients, though not for a couple of months now - and also not in the web client over the same period.  Another report mentioned a hang at the moment the buffering read-ahead reached the end; as a (past) programmer I'd certainly be chasing up that clue.

[Wondertje 10]

Another report mentioned a hang at the moment the buffering read-ahead reached the end; as a (past) programmer I'd certainly be chasing up that clue.

 

I haven't looked out for that actually, I'll see if I can look out for it next time and concur with previous report or not!

[Coolegb 0]

My issue is similar to @pwbodges , if it's a 1 movie, it goes blank at 55 min and if it's a 22 min movie it goes black at 19 and it seems to be consistent. It must be triggered by an end of movie function.

[Luke 42085]

We are looking into this. Thanks guys.