Log in

View Full Version : Vrtual dub crashes analyzing source


Makocha2
3rd March 2009, 02:49
I have a problem with AutoGK 2.55:

After demuxing and indexing the program calls virtual dub for analyzing source.

But instantly crashes giving this error message:

An out-of-bounds memory access (access violation) occurred in module 'DivX'...
...while decompressing video frame 0 with "DivX 6.8.5 YV12 Decoder" [biCompression=32315659] (VideoSource.cpp:1832).

But i'm using XVID as encoder.
after this the program continues and finishes witout any error giving a correctly playable file.

Does anyone experienced this error and how have you fixed it ?

yetanotherid
3rd March 2009, 12:53
What are you converting? DVDs or another AVI?
It's just that it sounds to me (and I'm only guessing) that even though you're converting to Xvid, it's the DviX codec doing the decoding of the original file, and it's with that codec that VDM is having problems. I don't know why that'd be the case, except maybe to guess again that DivX version 6 wasn't around when VDM was released so maybe they're not compatible.

I'd try uninstalling the DviX codec and see if the problem goes away.
There's probably a way to keep it installed, but get the XviD codec or the default system one to do the decoding work, but I'm not sure how... aside from maybe reinstalling the XviD codec and telling it to be the default decoder.

I don't have the DviX codec installed so can't tell you if version 6 is normally a problem. Maybe someone who knows better may come along. I assume though that VDM doesn't have any built in codecs of it's own, so uses the default system codec for decoding DVDs, and maybe somehow the DviX codec has taken over from that one and they don't play well together. I still don't always fully understand how programs decide which codec to use for a decoding job when there's multiple codecs installed that'll do it, so as I said, all the above is guesswork. My first step though would be to uninstall the problem codec if you're not using it.

Makocha2
4th March 2009, 00:52
Thank you for your answer.

I reinstalled AutoGK and now it don't give me that error anymore. mabe something went wrong during first installing.