Jump to content

Playback Locking Up


kevinw
Go to solution Solved by kevinw,

Recommended Posts

This is similar to the issue I reported here.

 

I turned hardware decoding back on some time ago and it's been working with no issue until recently. Playback is hanging on both FTV and Shield. I tried turning hardware decoding back off again but it hasn't made any difference this time.

The fact it stopped in exactly the same place on both devices perhaps points to the file itself but this has happened on half a dozen different files or so in the last week. I recognise that all of the files could be faulty but it seems a bit coincidental.

 

I did try to playback the same file in a browser on my PC afterwards but just sat there staring at spinning arcs before giving up.

 

I've attached the server log together with the ffmpeg log for both devices (same file being played).

 

As an aside, I was surprised the file was being transcoded for the Shield, I thought the Shield would play just about anything directly but perhaps that's wrong.

 

Kevin

Server Log.txt

ffmpeg for Shield.txt

ffmpeg for FTV.txt

Edited by kevinw
Link to comment
Share on other sites

Hi there, have you tried lowering the in-app quality setting? Often times this is an indication that the bitrate is a little too high.

Link to comment
Share on other sites

Hi Luke, Max Streaming BitRate is set to Auto. Should I change that?

 

Not sure if this helps but the dedicated server is running W10Pro on an i5-6600T with 16GB RAM. Media is coming from a Synology 1819+ which is doing nothing but serving files (and only to one instance of emby at the moment).

 

Kevin

Link to comment
Share on other sites

What happens if you turn off transcode throttling?  Glancing at the log ffmpeg encounters this error:

18:02:23.109 [matroska,webm @ 0000025426edf100] 0x00 at pos 208942068 (0xc7433f4) invalid as first byte of an EBML number

And, at that point, our throttle logic appears to get kind of "stuck"

Link to comment
Share on other sites

Just tried that but no change...well, maybe a little as the playback hung for a while, then continued for about a second, then went to a black screen with a blue swirling circle.

 

This is a different file on Shield, logs attached. I wasn't sure which ffmpeg file is the correct one. Not that I have any idea what I'm talking about but the latest one seems too short to tell you anything so I attached the previous one as well.

 

Again, the Hardware Acceleration setting makes no difference.

 

Kevin

 

Edit: Corrected Encoding to Acceleration.

Server Log.txt

latest ffmpeg.txt

Previous ffmpeg.txt

Edited by kevinw
Link to comment
Share on other sites

Is there something wrong with this file, or have you done a hard disk check to look for a possible drive failure?

 

Because first the player tries to direct play it, which produces an error. Then the app switches to transcoding to try and get it to play, but ffmpeg on the server also has trouble with it. You see lots of things like this in the log:

corrupt decoded frame in stream 0
Link to comment
Share on other sites

Hi Luke, yes, as per my opening post, it's possible there may be something wrong with the file but if that's the problem there are 5 files that have the same issue.

 

The files are located on a NAS and there are no disk issues with it.

 

I'll replace the files with new versions and we'll see how we go from there.

 

Thanks for the team's speedy responses.

 

Kevin

Link to comment
Share on other sites

 

 

The files are located on a NAS and there are no disk issues with it.

 

I understand that you're saying that, but have you done a hard disk check to look for a possible drive failure?

Link to comment
Share on other sites

Well the SMART quick test runs monthly and hasn't reported any errors. I've just run it again with the same result.

 

The extended test will take between 11.5 and 29 hours per disk, depending on which disk it is, across eight disks so I'm not about to run that.

 

Kevin

Link to comment
Share on other sites

It's just odd that both the video player in the app as well as ffmpeg on the server are having trouble reading the file.

Link to comment
Share on other sites

I agree and having just said I'm not about to run the extended test I kicked it off about 15 minutes ago.

 

I think they may be duff files no matter how coincidental that is.

 

Kevin

Link to comment
Share on other sites

Mixed results so far. Of the four files I replaced three played with no issue. Two replacement files for the other one locked up at different places. Unfortunately my wife deleted the first one before I grabbed a copy but when I've got two or three samples I'll have a look at the files and see if there are any common attributes.

 

What's the best tool for displaying information about a video file? I've got MKVToolNix and MediaInfo but neither seem to display all of the data in such a way that I can easily screen grab it.

 

Kevin

Link to comment
Share on other sites

  • 3 months later...
  • Solution
kevinw

...and just to close this off, I figured out the issue was being caused by a setting within Sonarr. Once I'd changed that the problem was resolved.

@Luke: It's not that data is missing, more than it's not presented in a way I could easily screen shot to put in here. Thanks for your help.

 

Kevin

Edited by kevinw
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...