Playback stopping after a few seconds

[vast1983 0]

I know this thread has been done to death. But all of a sudden I cant play files from my server. Ive tried both my nvidia shield TV and my android mobile. I get about 1 minute at best before it stops. 

 

Attached is the server log, there is nothing in the transcoding temp folder, as I shouldnt be transcoding anything, all files are h 264 mp4s with external srts downloaded through emby server. 

server-63603572570.txt

[Luke 42077]

Hi, can you discuss an example? Please provide a copy of the media info as seen in the web interface. thanks.

[vast1983 0]

This work for you?

 

Really an example is now, any time I try to play back any movie file, it will play for anywhere from 10 seconds to 2 mins. Then it will kick me out to the title selection screen, as though a pressed back on the remote. Same with my android phone. 

 

Ive been handbraking my titles with the same preset for a couple years, so nothing has changed there. I did change server hardware, from an i3 NUC to an i5 NUC about 2 months ago, but that has been operating fine up until recently.  

[Luke 42077]

Have you customized the in-app bitrate setting?

[Luke 42077]

The only thing that jumps out is 6 reference frames for h264 1080p is a little on the high side. That might be a little too much for the decoder to handle. Since you're using handbrake, can you do a test and encode a similar or the same video with 3 or 4 reference frames? 4 is generally considered the upper limit for 1080p. Thanks.

[vast1983 0]

Set to "auto" in the app settings

[vast1983 0]

The only thing that jumps out is 6 reference frames for h264 1080p is a little on the high side. That might be a little too much for the decoder to handle. Since you're using handbrake, can you do a test and encode a similar or the same video with 3 or 4 reference frames? 4 is generally considered the upper limit for 1080p. Thanks.

Interesting, Ill look into that.

[Luke 42077]

Yea we probably need to be excluding this video from direct play and transcoding it, it's just a little complicated because the rules need to vary based on input resolution, and we have to add that ability to our decision making process. So for instance, at 1080p h264, the upper limit is generally 4. At 720p, it's a bit higher, etc. It's on our to do list so that it ultimately will just work.

[vast1983 0]

Anything above 4 reference frames seems to be the culprit.

 

I think I've never noticed it before because I use a mix of emby (my preferred) and an Apple TV using homesharing (my wife's preferred, boo) I think we just got lucky with my wife choosing said movies with over 4 ref frames.

 

Great catch! And thank you for making such an amazing media consumption ecosystem! 

[Luke 42077]

Awesome, thanks for reporting back.

[vast1983 0]

Follow up question:

 

I am building my own NAS out of my main rig parts soon, as Ill be upgrading. Would utilizing more robust hardware as the server (this will be an i7-4770k) have any effect on handling more reference frames?(looks like the max Ive found is 6) Or is the decoder something inherent of the emby server/playback hardware itself?

 

Taking an audit of all my movies with over 4 reference frames.... the though of re-encoding allt hose files...... I can hear my CPU screaming now!

[Luke 42077]

No this is an issue of client side, and no specific to android. Most video players are going to have trouble with high ref frame counts.