View Single Post
Old 1st February 2009, 23:39   #8106  |  Link
Snowknight26
Registered User
 
Join Date: Aug 2007
Posts: 1,430
Quote:
Originally Posted by madshi View Post
A bigger problem is that eac3to doesn't like the h264/AVC tracks in your MKVs. This is caused by the video stream itself not containing any sequence headers. Because of that eac3to just lists the MKV properties of the video track instead of parsing the video bitstream itself. You can see that by the tracks being listed as "V_MPEG4/ISO/AVC". All video and audio tracks beginning with "V_" or "A_" are Matroska names. If tracks are listed like that, eac3to was not able to fully understand/parse the video/audio bitstream.
Strange. The only thing that they share in common is that they were all muxed with mkvmerge.

Quote:
Originally Posted by madshi View Post
The video in that MKV is encoded with 23.976/1.000fps. I consider that "non-standard". The correct framerate would be 24.000/1.001fps. That's why eac3to (correctly) posts a warning. You can fix the problem by using "eac3to 24.s01e01.mkv fixed.mkv -slowdown". That will patch the video bitstream from 23.976/1.000 to 24.000/1.001.
Is that all it does? It won't keep the audio muxed into the mkv?
Snowknight26 is offline