Jump to content

Video Stuttering on Shield


Bigmack3000
 Share

Go to solution Solved by Bigmack3000,

Recommended Posts

Bigmack3000

One file is playing fine in the web browser, but stuttering when played on my shield.  It's an episode of a TV show and the episode before and after are not having this problem.  

I'm attaching two logs.  I believe one shows it playing on the browser, and one on the shield.

embyserver (1).txt ffmpeg-remux-d549d6d5-fada-44ef-aa22-ffdfe28839e8_1.txt

Link to comment
Share on other sites

Hi.  Can you define "stuttering?  Is it pausing to buffer or does it look like a frame-rate or timing issue?

I see two things that could be a problem:

1) The frame rate of the video is 25.  Are you playing it back on a display capable of 25fps and in that mode (or a multiple of it)?

2) When the item was remuxed to play in the browser, that log is filled with timestamp errors:

01:05:20.701 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.707 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19631853, current: 19631114; changing to 19631854. This may result in incorrect timestamps in the output file.
01:05:20.713 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.719 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19650663, current: 19649922; changing to 19650664. This may result in incorrect timestamps in the output file.
01:05:20.724 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.732 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19664755, current: 19664016; changing to 19664756. This may result in incorrect timestamps in the output file.
01:05:20.745 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.751 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19690649, current: 19689910; changing to 19690650. This may result in incorrect timestamps in the output file.

If you look at a remux log from one of the episodes that doesn't have a problem (play it in chrome), do they have these same errors?

Link to comment
Share on other sites

Hi,

I would source or rip a new version of that episode as it is likely at fault and wasn't properly encoded.

  • Agree 1
Link to comment
Share on other sites

Bigmack3000
1 hour ago, ebr said:

Hi.  Can you define "stuttering?  Is it pausing to buffer or does it look like a frame-rate or timing issue?

I see two things that could be a problem:

1) The frame rate of the video is 25.  Are you playing it back on a display capable of 25fps and in that mode (or a multiple of it)?

2) When the item was remuxed to play in the browser, that log is filled with timestamp errors:


01:05:20.701 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.707 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19631853, current: 19631114; changing to 19631854. This may result in incorrect timestamps in the output file.
01:05:20.713 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.719 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19650663, current: 19649922; changing to 19650664. This may result in incorrect timestamps in the output file.
01:05:20.724 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.732 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19664755, current: 19664016; changing to 19664756. This may result in incorrect timestamps in the output file.
01:05:20.745 [libmp3lame @ 0x2438d40] Queue input is backward in time
01:05:20.751 [segment @ 0x24354c0] Non-monotonous DTS in output stream 0:1; previous: 19690649, current: 19689910; changing to 19690650. This may result in incorrect timestamps in the output file.

If you look at a remux log from one of the episodes that doesn't have a problem (play it in chrome), do they have these same errors?

By stuttering it looks like its skipping through the episode and the sound can't sync.

I'm attaching another log here.  I just tested the episode before this one on my shield, which is also 25fps.  No issues with playback.

 

33 minutes ago, cayars said:

Hi,

I would source or rip a new version of that episode as it is likely at fault and wasn't properly encoded.

Even though the file plays fine in the web browser?  

embyserver.txt

Link to comment
Share on other sites

1 hour ago, ebr said:

If you look at a remux log from one of the episodes that doesn't have a problem (play it in chrome), do they have these same errors?

Hi.  Did you do this?

I, like cayars, suspect the encoding of the item due to the errors being reported by ffmpeg.  When you play in the browser, ffmpeg is correcting those errors. 

  • Like 1
Link to comment
Share on other sites

Bigmack3000

Yea, I probably had re encoded it from mpeg2 to h264.  So this one didn't go through that properly?

Link to comment
Share on other sites

Worth trying it again - not sure what you are using to convert - but ensure you keep the fps to 25 as it's a UK PAL source most likely.

 

Link to comment
Share on other sites

Bigmack3000

Okay, yup.  Went back to the source file and that plays fine on my shield.  I had used an outside program to convert it last time, but I'll try to convert within emby this time.

  • Like 1
Link to comment
Share on other sites

  • Solution
Bigmack3000

Success.  I only played the first 5 minutes, but it appears Emby converted the file without any issues.

  • Like 1
Link to comment
Share on other sites

Awesome, thanks for updating the thread with your results!

Glad you got your problem solved.

Link to comment
Share on other sites

  • 8 months later...

This is happening again with episodes of "Travel Man".  Can someone see what the problem with the file is if I post the logs?

I was also able to play it from the web browser without any issue.  So this looks like an issue from the shield app.

embyserver (2).txt ffmpeg-remux-8fa798da-d883-4ddb-8760-996d6583b21f_1.txt

Edited by Bigmack3000
Link to comment
Share on other sites

As a general rule of thumb, If the Shield can't play something, then there are some serious issues with the source file OR the Shield is not configured properly (Auto settings should be used).  

Try setting the 'Match Refresh Rate/Scaling' on the Emby Playback settings.

Can you provide a screenshot of the 'Stats for nerds' so we can see the playback details and a mediainfo of the source file ?

The ffmpeg log is simply remuxing the Audio so the browser can play it - so it's not giving many clues - however ..

The 'Travel Man' is a UK TV broadcast - which will be at 25/50 fps - ffmpeg is reporting the Video as 23.976 (film) - meaning something is not right ...

 

Edited by rbjtech
Link to comment
Share on other sites

18 minutes ago, rbjtech said:

As a general rule of thumb, If the Shield can't play something, then there are some serious issues with the source file OR the Shield is not configured properly (Auto settings should be used).  

Try setting the 'Match Refresh Rate/Scaling' on the Emby Playback settings.

Can you provide a screenshot of the 'Stats for nerds' so we can see the playback details and a mediainfo of the source file ?

The ffmpeg log is simply remuxing the Audio so the browser can play it - so it's not giving many clues - however ..

The 'Travel Man' is a UK TV broadcast - which will be at 25/50 fps - ffmpeg is reporting the Video as 23.976 (film) - meaning something is not right ...

 

I see two options. "Enable Refresh Rate Switching" and "Match Video Resolution".  Are these the same thing?

Also, what is stats for nerds? and where do I find it?

This is a mediainfo screenshot for Travel Man:

600451255_ScreenShot2021-12-15at12_34_25AM.png.066ac6f476d7f3574ee00451d42935ad.png

 

In comparison here is a screenshot for an episode from the Up Series that is also 25fps and plays without any issues:

 

1394010070_ScreenShot2021-12-15at12_35_02AM.png.ed5b96651f90e771016fa7b5ac4774e9.png

Link to comment
Share on other sites

Stats for nerds (SFN) is shown by pressing and holding the centre button during playback.  You can also get to it from the menu but this is the quickest way.

As expected, this is a 25 fps show - the only difference is this one has AC3 Audio - which is perfectly normal and should not introduce any issues.

Nothing shouts out as being wrong here - the only thing I can see is the writing library - which I've never heard of (WonderShare MKv Muxer)

If you have mkvtoolnix GUI (you can download the mkv tools for free) - it is worth dragging this file in and remuxing it to a new file to try ?

Link to comment
Share on other sites

Ok throwing it into mkvtoolnix might have worked.  Have to check more episodes to confirm.

Here is the sfn for the file that did not work:

20211215_231711.thumb.jpg.59a4bf301b3fa48cf86c197f254e8913.jpg

 

here is the sfn for the remux that did work:

20211215_231803.thumb.jpg.501e0ac51aff77c76fd2822a4afbe7f1.jpg

 

Does this confirm what you thought the problem was?

Link to comment
Share on other sites

6 hours ago, Bigmack3000 said:

Does this confirm what you thought the problem was?

Hi.  Most likely, yes.  It was probably a problem with the headers or other meta of the file.

Link to comment
Share on other sites

7 hours ago, Bigmack3000 said:

Ok throwing it into mkvtoolnix might have worked.  Have to check more episodes to confirm.

Here is the sfn for the file that did not work:

20211215_231711.thumb.jpg.59a4bf301b3fa48cf86c197f254e8913.jpg

 

here is the sfn for the remux that did work:

20211215_231803.thumb.jpg.501e0ac51aff77c76fd2822a4afbe7f1.jpg

 

Does this confirm what you thought the problem was?

If a remux has fixed it - then yes, the application used to create the MKV has done it in an incompatible way for Exo (Android) to correctly playback.

To further improve the experience - I do note that you are attempting to playback 25fps material on a 60fps display - this will 'work' but it is not optimal.  

Assuming your TV supports framerate switching (most do these days) then in the Emby App, in Playback settings - set both the options for framerate matching/scale to on.

In SFN - you should then see the Display Mode say 2160/25 - ie the TV is displaying the video the same as the source file - it should look 'less jerky' especially in 'panning' type shots.

This will also significantly improve 'Film' where a fps of 23.976 is normally used.

 

Edited by rbjtech
Link to comment
Share on other sites

8 minutes ago, Bigmack3000 said:

I've enabled those settings in emby, but it's still saying 60fps for playback.  Anywhere else to adjust that?

It's possible your TV does not support it - what TV is it ?

Link to comment
Share on other sites

  • 3 months later...
Bigmack3000

So I keep coming across more files with the Wondershare Matroska Muxer".  I think it's files that I used iSkysoft to convert. But the thing is they play fine in essentially every app Except the android tv one on my shield.  Is it possible to add support for this container on the shield app?

Link to comment
Share on other sites

22 minutes ago, Bigmack3000 said:

Is it possible to add support for this container on the shield app?

Hi.  The MKV container is supported.  That particular muxer must be doing something unexpected though if Exo does not like it.

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
 Share

×
×
  • Create New...