PowerGamer
11th January 2010, 21:12
I have done some testing with demuxing video tracks from .m2ts files from a few Blu-ray disks: main movie track from Tinkerbell, largest bonus film from the same disk and Mike's New Car from Pixar Short Films Collection. All video was in h264/AVC, 1080p24 /1.001 format. Each video track was demuxed by each of the following programs: eac3to, tsmuxer, xport, Blu-Ray Demuxer Pro (http://dvd-logic.com/bddemuxerpro.php). Files produced by last 3 programs were byte-identical. In case of Mike's New Car eac3to also produced the same byte-identical .h264 video file. But in case of two other movies eac3to produced different video files:
Tinkerbell main movie:
eac3to file size: 16 845 863 552 bytes
other programs: 16 876 200 309 bytes
bytes start to mismatch at 000EC3FC offset.
Tinkerbell bonus movie:
eac3to file size: 1 361 242 778 bytes
other programs: 1 362 859 162 bytes
bytes start to mismatch at 00000D98 offset.
Why eac3to video output is not byte-identical to the output of other programs in 2 out of 3 cases? Is there some bug in eac3to that produces incorrect video output?
Tinkerbell main movie:
eac3to file size: 16 845 863 552 bytes
other programs: 16 876 200 309 bytes
bytes start to mismatch at 000EC3FC offset.
Tinkerbell bonus movie:
eac3to file size: 1 361 242 778 bytes
other programs: 1 362 859 162 bytes
bytes start to mismatch at 00000D98 offset.
Why eac3to video output is not byte-identical to the output of other programs in 2 out of 3 cases? Is there some bug in eac3to that produces incorrect video output?