What is "error -372" ?

[theReal]

Since I'm using the newest Avisynth 1.06b (installed through Gknot 0.26b) I eventually get a strange error in avisynth. Suddenly, during encoding or watching in Mediaplayer, the sound starts to go in a loop and the picture goes black and shows an error message:

AVISource: failed to decompress frame xxx (error -372)

When I play or encode it again, the error doesn't occur (or occurs at another frame). I scanned the HD and it doesn't seem to have any errors.

It's quite annoying to find, after having encoded for hours, a video file that is mostly an encoded avisynth error message...

[onlyonesandman]

Originally posted by theReal
Since I'm using the newest Avisynth 1.06b (installed through Gknot 0.26b) I eventually get a strange error in avisynth. Suddenly, during encoding or watching in Mediaplayer, the sound starts to go in a loop and the picture goes black and shows an error message:

AVISource: failed to decompress frame xxx (error -372)

When I play or encode it again, the error doesn't occur (or occurs at another frame). I scanned the HD and it doesn't seem to have any errors.

It's quite annoying to find, after having encoded for hours, a video file that is mostly an encoded avisynth error message...

I have the same problem. It is probably because your avi file is corrupted. If you use the DivFix error check utility it'll probably report an error on the frame it starts reporting the "can't decompress' message.

I haven't found a solution, but I was wondering if you have found one since your last post.

Onlyonesandman

[theReal]

I haven't found a real solution except that not setting Real Producer to "lower" or "idle" priority seems to help, as well as not stressing the computer/harddrives too much while encoding. With normal priority and left pretty much alone it hasn't happened again.

Also, this does not apply to VDub - VDub doesn't cause any problems with avisynth, even if set to "idle" priority.

Then, I can't use DivxFix because the source is two mjpeg files (only keyframes) which work perfectly with VDub, avisynth and realproducer, except for a few times when suddenly the error was reported (on the next try the error was gone, so it can't be the files, right?)

Maybe it's just that if avisynth can't read the next frame quickly enough because it's set to low priority and the harddrive is under stress with other applications, then it assumes the next frame is unreadable. I don't know...

That's why I tried to find out what the hell "error -372" and "error -379" (which also occured once) means. Is there a list of avisynth error-numbers where we could look it up?