Avi_tc: "# of data chunks does not match frame count&qu

kiarrens · Post by **kiarrens** » Sat Sep 08, 2007 12:36 pm

I'm attempting to run the raw episodes of Romeo x Juliet 19 and 20 through avi_tc, and I'm getting the error I quoted in the subject.

(Entire Processing Window:
"Frame parsing progress: 100%
Timecode file created successfully
Frame modification progress: 0.00%
Number of data chunks does not match frame count")

I double checked the frame count in Vdub and it is indeed 120 FPS...
All of the other episodes I've run through the program have worked, but they were all encoded WMV9, and these two are divx521 (Xvid MPEG-4 codec according to Vdub), so maybe that's the issue?
If anyone's run into this issue and knows how to fix it, I'd really appreciate the help.

post-it · Post by **post-it** » Sun Sep 09, 2007 1:15 am

.. all the un-subbed episodes are in 120 fps this fall so get used to it. It's not a Virtual Dub program that they are being Captured to, nor is it a Codec error. How you correct it is quite simple,

.. if the program is not in True HD and only Cropped then you will see that by dropping frames 1,2,3 and leaving 4 has no barring on viewing it. The default codec's are MKv related .. not Divx/xviD

kiarrens · Post by **kiarrens** » Sun Sep 09, 2007 9:41 am

Ok, I'll try. Thanks. I wasn't aware that the problem could be fixed in Vdub, I thought it had to be fixed with Avi_tc.

BasharOfTheAges · Post by **BasharOfTheAges** » Sun Sep 09, 2007 10:03 am

Well, sources that are 120fps are usually like that because they're a mix of 2 frame rates. If you simply change the frame rate like post-it is suggesting all the parts that are the frame rate you're changing into will be fine and all the others will be completely fucked up.

kiarrens · Post by **kiarrens** » Sun Sep 09, 2007 5:21 pm

that's what I thought, but I figured it was worth a try. It DID seem to work, but I'm getting this strange little watermark in the top right hand corner of the video after using his method.
(Imported Raw into Vdub, fixed framerate, exported clips as huffyYUV with no audio, no other alterations)

kiarrens · Post by **kiarrens** » Sun Sep 09, 2007 5:34 pm

That's the watermark....
(hope that code worked since there's no edit posting on here)

kiarrens · Post by **kiarrens** » Mon Sep 10, 2007 6:31 pm

Disregard the watermark. I'm just unobservant, I guess... DOKool pointed out that it is the Tokyo Broadcasting symbol. It was on the original raw.
Go go DOKool.

post-it · Post by **post-it** » Mon Sep 10, 2007 7:56 pm

.. I did not deceive in my answer; this solution works -- did it not??

.. as far as splitting the Video's, that question was not asked ^__^

Qyot27 · Post by **Qyot27** » Mon Sep 10, 2007 9:38 pm

post-it wrote:.. I did not deceive in my answer; this solution works -- did it not??

It just doesn't do it properly - which is the key thing here. It 'works', but it incurs loss - loss that can be avoided by using Avi_tc, because it losslessly removes the dummy frames which make the file 120fps, leaving only real frames behind. Doing it in VirtualDub (or AviSynth, for that matter) by no means guarantees that only dummy frames are affected. It also blows the shit out of pans that occur in the wrong framerate-corrected parts of the source, and maybe even in the right corrected parts of the source.

kiarrens wrote:(Entire Processing Window:
"Frame parsing progress: 100%
Timecode file created successfully
Frame modification progress: 0.00%
Number of data chunks does not match frame count")

I double checked the frame count in Vdub and it is indeed 120 FPS...
All of the other episodes I've run through the program have worked, but they were all encoded WMV9, and these two are divx521 (Xvid MPEG-4 codec according to Vdub), so maybe that's the issue?

Try separating the segments based on true framerate and run each one through instead. For instance, go to the 29.97fps segments, which you can find by seeing a [D] in the status bar (next to the in/out point marker buttons) occur 4 times in a row, and use Direct Stream Copy to save that segment to a new AVI, making sure to cut on keyframes. Then take the 23.976 segments (noted by having 5 [D] frames in a row), and save them to new AVIs. Usually, 29.97fps is limited to the opening and ending - maybe the eyecatch - and 23.976 is typically the main body of the program and the next episode preview. After you've run them through individually like that (provided it works), then just make sure all the framerates are the same and use Direct Stream Copy and the Append... function to piece them back together. If some parts are faster or slower doesn't matter unless you want to retain audio sync, in which case some AviSynth splicing is in order. The editing program can handle correcting overly sped-up or overly-slowed footage.