Encodes 'abort' at 100%, yet output seems ok ... ?

[absinthe]

I'm using Xvid 1.0.2

For some reason, my 2-pass encodes are aborting at 100% completion on each pass ... and yet my final outcome product seems ok.

In other words, I configure each pass manually in VirtualDub, then start them from Job Control. The next morning I awaken to find VirtualDub VirtualGone :D. It's closed completely. When I open it up and look in job control, the first pass says 'aborted' and the second pass never started.

I went through this 2 or 3 times, and then decided to just go ahead and start the second pass. Second pass also "aborted" at 100%. Yet as far as I can tell, my output file seems okay (and in job control, both passes were 'aborted'). Go figure.

I've done dozens of encodes this way and have never had this problem. I always use virtually the same settings. And the problem didn't start when I upgraded to the new v1.0.2.

Any ideas?

-abs

[absinthe]

Aw, c'mon now. Someone must have an idea ... :p

I've discerned that it's only this particular encode job on which this happens. It's a 2-hour movie which I'm encoding at 640x352 and adjusting the frame rate down from PAL to 23.976. The script is simply three lines (Mpeg2source, LanczosResize, and AssumeFPS).

Now if I add a 'Trim' command to the script and only encode half the movie, or an even shorter segment, it will encode all the way through, no problem.

I don't think it's just a matter of length, though, as I've definitely encoded longer movies (though perhaps with a smaller resolution ... and they were probably with the 1.0.1 version of the codec).

Again ... even though the encode (of the whole movie) aborts, it does so at 100% and the movie comes out fine as far as I can tell.

-abs

[lordadmira]

It could be that the end of the source file is corrupted. Even if it plays OK it depends on AVISynth's or VirtualDub's idea of corruptedness. Try encoding just the last 5 minutes of the movie. Also make sure "shutdown when complete" wasn't checked. If you double click on the job line in the job control it will display any error message if there was one.

LA

[aiataga]

There is nothing to do with codec and source.
I’ve got the same behavior with ffv1.
It’s VirtualDub's (1.6.0 build 21540) jobs problem.

[Edit] added version info

[niamh]

try another version of Vdubmod

[Bogalvator]

Are you using AviSynth? If so, maybe revert to v2.54 to see if that helps.

[absinthe]

Hey all. Thanks for the replies. Sorry I've been a day or two getting back, but I've been in bed with what was apparently a 24-hour bug.

Anyway, I'm using Vdub 1.5.10 and VDubMod 1.5.10, and this error occurred in both of those applications, several times each in fact. My AviSynth version is 2.54 already.

I am intrigued by the idea that maybe the end of my source file was corrupt, but by now I've deleted the VOBs from my hard drive. No biggie anyway. It never happened before nor since, and maybe it won't return. And as I've said, my output file seems fine as far as I can tell.

One thing I have learned from this thread: double-clicking on the error messages in Job Control will show the error (thanks lordadmira :)). I had no idea; I had been looking around for some kind of *.log file. Apparently, double-clicking will also reset a completed job, allowing you to run the job again if you wish, I assume. I had been wondering why there didn't seem to be a way to do that.

-abs

[Andrey]

As I remeber, this is last Vdub versions error. Search for Koepi post about it...
BTW, this error should not occur if you start the task manually, not using Job Control.
To solve it use latest stable vdub.

[absinthe]

Originally posted by Andrey
As I remeber, this is last Vdub versions error. Search for Koepi post about it...
BTW, this error should not occur if you start the task manually, not using Job Control.
To solve it use latest stable vdub.

I believe 1.5.10 is the latest stable Vdub (1.6.0 being "experimental").

-abs

[Manao]

The latest stable, imho, is still 1.5.4.

1.5.10 is far too unstable ( Deadlock issues, and job control not working )