Mpeg 2 converted to h264 stuttering

[Bigmack3000 107]

Not the exact same issue, but I think close enough to not warrant starting a new topic:

 

I tried converting a few mpeg2 files to h264, but they are causing stuttering in the Shield app while the mpeg2 versions play fine.  Both versions play fine in the web app.  I don't know if this picture will give the info needed, but here is an example of one:

 

[ebr 16184]

Please provide logs from an example.

 

Thanks.

[Bigmack3000 107]

I saved the log as a txt file, but how do I attach it here?

[Bigmack3000 107]

Found it.  I attached logs for playing the mpeg and playing the h264

12 Angry Men_Mpeg.txt

12 Angry Men_H264.txt

[ebr 16184]

Looks to me like not a great conversion...

[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 19645, current: 18906; changing to 19646. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 45539, current: 44800; changing to 45540. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 66716, current: 65886; changing to 66717. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 92518, current: 91780; changing to 92519. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 113696, current: 112955; changing to 113697. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 139590, current: 138849; changing to 139591. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 160676, current: 159937; changing to 160677. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 186569, current: 185831; changing to 186570. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 207745, current: 207006; changing to 207746. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 233639, current: 232810; changing to 233640. This may result in incorrect timestamps in the output file.
[libmp3lame @ 0x158f600] Queue input is backward in time
[segment @ 0x16cec40] Non-monotonous DTS in output stream 0:1; previous: 254727, current: 253986; changing to 254728. This may result in incorrect timestamps in the output file.
[

[Bigmack3000 107]

Interesting.  So iSkysoft maybe a program to avoid?  Also, is that the audio or video that seems to be causing the problem?  Or both?

[ebr 16184]

@@softworkz do you have any insight?

[Bigmack3000 107]

I may have answered my own question.  I used mkvtoolnix to switch out the audio with the original file's audio and no playback issues on my shield.  So I might have to look over the audio options in iskysoft.