|
I've got one that has me scratching my head...
transport stream file, being processed by RC2.
If I say 'save project' with 'demux all audio' and NO 'log timestamps', at the end dgindex reports bad field transition. When I let it correct it, it shows a SINGLE fix.
If I say 'save project' with 'demux all audio' and ENABLE 'log timestamps', at the end dgindex reports bad field transition. When I let it correct it, well I'm guessing, but it looks like it massages a LOT of the file. (gross metric - .d2v=1300KB, fix.txt=592KB)
Other odd things I've noticed so far:
It is reported as Film ~70%. It does this for pretty much any segment, though the number varies some. As an example, I played a short section; 'Frame type' switched back and forth between Progressive and Interlaced, Playback #=706, Coded #=592, and Field Rpts=228. (706-592=114, 114*2=228), Video Type = Film 76%
mpeg2repair generates error groups every 14 frames(?)
ie "Sequence Frame NN(12-B)" where NN is 28,42,56,...
consisting mostly of 'temporalref gap' and 'unexpected tff/rff flag change'.
At the end it reports,
0 of 273148 video frames found with errors
12 of 333624 audio frames found with errors
0 corrupted video bytes in file
18300.7 seconds of video timestamp gaps
delaycut reports 1533 errors in the dgindex created ac3 file (vs 12 above?) and oftimes has to 'rewind 170 bytes' in order to find a sync word.
Comments?
Last edited by plugh; 4th April 2008 at 17:02.
|