View Full Version : Xvid 2nd pass crash (no way out...)
Movie Maniac®
26th January 2004, 12:45
I've got problems with the latest release of Xvid.
I'm tryin' to compress a double pass avi file, but I wasn't able to reach my goal.
The first went OK but there's no way to get the second one started.
I receive always the same crash message from bot Virtualdub and Virtualdubmod:
Originally written by Virtualdub(Mod)
An out-of-bounds memory access (access violation) occurred in module 'xvidcore'...
...while passing start message to video compressor (VideoSequenceCompressor.cpp:284).
I've tried to use both "fast recompress" and "full processing mode".
I'm using Avisynth 2.5.3+Virtualdub(mod) 1.5.10 with the latest binaries available (the latest available release "XviD-1.0-RC1-25012004.exe") (downloaded from koepi's site), with 1GB of DDR 333mHZ ram and an athlon 2600+ (333mHZ) cpu.
sysKin
26th January 2004, 13:11
Could you send me/paste full crash report from vdub? Stack trace is the interesting part :)
Radek
Movie Maniac®
26th January 2004, 13:44
Ok
I came out with the solution...
Seems that the stats reader bundled with the latest release of Xvid, is useless :'(
I needed to force some KF, and since my stats editor doesn't work with the new Xvid .pass file, I used the koepi's stats reader, which opens also the new .pass files.
I orced the KF and saved to file...
but the new file isn't in the new format, it's in the old .stats format.
And that was the cause of the crash... I didn't verify the new file, since I thought it was in the new format :(
Is there any doc that explains deeply the new .pass format?
I'd like to update my stats editor in order to work with it...
Thx
Bye
olnima
26th January 2004, 14:13
Please put also an eye to this thread:
http://forum.doom9.org/showthread.php?s=&threadid=69582
Greetz
Olnima
sysKin
26th January 2004, 14:48
I would highly *not* recommend forcing keyframes this way. Add keyframe zones during 1st pass and you have your keyframes.
The stats file is pure text, it shouldn't be difficult to decipher it - frame type, quantizer (on 1st pass), kblocks, inter-blocks, skip-blocks, total size, size of motion&header.
Have fun,
Radek
Movie Maniac®
26th January 2004, 15:08
Originally posted by sysKin
I would highly *not* recommend forcing keyframes this way. Add keyframe zones during 1st pass and you have your keyframes.
I've always done this way with old Xvid without any problem. I think it's faster than adding one frame per time in the frames zone. What's wrong with this? I'm asking becouse I'm curious, I'm serious and not kiddin' you (sometimes peoples seems not to understand me)
Anyhow, I'd like to try this new feature.
Is it sufficient for me to add for example the frame number and select "start with key frame"?
I mean... suppose I need the frame n. 7981 to be a K. I add a new zone and put the starting frame at 7981, then select start with KF and click OK, and that's all?
Thanks for your support...
zulu
26th January 2004, 15:16
I mean... suppose I need the frame n. 7981 to be a K. I add a new zone and put the starting frame at 7981, then select start with KF and click OK, and that's all?
yepp.
my keyframeenforcer can create those keyframe zones from ifo, chapterxtractor or smartripper files but is not ready for the public yet. if you're interested...
Movie Maniac®
26th January 2004, 15:17
Hi there Zulu
nice to meet you again :D
I'm really interested.
Obviously if you can :D
bye
sysKin
26th January 2004, 15:20
Originally posted by Movie Maniac®
I've always done this way with old Xvid without any problem. I think it's faster than adding one frame per time in the frames zone. What's wrong with this? I'm asking becouse I'm curious, I'm serious and not kiddin' you (sometimes peoples seems not to understand me)It's all about curve compression. It will not be able to scale such frame correctly because fake frame type "i" will not match its size or motion/texture distribution (two last columns in stats file). It will also be surprised when the actual frame turns out to be too big (than predicted) and will decrease quality of next p-frames to keep up with estimated curve.
Nothing really dreadful, but less effective.
Is it sufficient for me to add for example the frame number and select "start with key frame"?
I mean... suppose I need the frame n. 7981 to be a K. I add a new zone and put the starting frame at 7981, then select start with KF and click OK, and that's all?Yes, that's all. I've heard that there is a problem with it, I'll investigate more but it did work when I last tried.
zulu
26th January 2004, 15:22
zones are saved to the registry.
i'll send you a copy as soon as i'm back home.
Movie Maniac®
26th January 2004, 15:29
Originally posted by zulu
zones are saved to the registry.
Yes, I've found them looking into the registry...
i'll send you a copy as soon as i'm back home.
Thx
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.