Donald24
1st April 2002, 09:04
Hello folks,
I coded Titanic yesterday in 2-pass for a 4-CD rip, with an estimated avi filesize of about 2.6GB (video only). I knew about the FAT 2GB filesize limit, so I did code on a NTFS partition.
I am using the latest Vdub version (1.4.9).
At the end of the second pass, Vdub crashed (I think while writing the frame-index) leaving a avi file of exactly 2600MB, that is useless. No player wants to open that file. Vdub wants to recreate that keyframe-index, which is obviously taking longer, than to encode that movie again.
I didn't have any success in using div-fix, it is crashing when reaching the 2GB barrier.
Is that a regular behavior of Vdub? I can remember, in Mpeg2Avi times a second avi was saved after an avi-filesize of 2GB to overcome that problem. Doesn't Vdub have such a routine? Or was it an irregular behavior?
Is it possible to rescue that data without much effort? I mean, the movie is rendered only index is missing...
Thanks mates,
Don
I coded Titanic yesterday in 2-pass for a 4-CD rip, with an estimated avi filesize of about 2.6GB (video only). I knew about the FAT 2GB filesize limit, so I did code on a NTFS partition.
I am using the latest Vdub version (1.4.9).
At the end of the second pass, Vdub crashed (I think while writing the frame-index) leaving a avi file of exactly 2600MB, that is useless. No player wants to open that file. Vdub wants to recreate that keyframe-index, which is obviously taking longer, than to encode that movie again.
I didn't have any success in using div-fix, it is crashing when reaching the 2GB barrier.
Is that a regular behavior of Vdub? I can remember, in Mpeg2Avi times a second avi was saved after an avi-filesize of 2GB to overcome that problem. Doesn't Vdub have such a routine? Or was it an irregular behavior?
Is it possible to rescue that data without much effort? I mean, the movie is rendered only index is missing...
Thanks mates,
Don