How does RB determine "Restart from" point?

[laserfan]

I set-up a batch file and accidentally set the working directory to a too-small hard disk. RB got most of the way thru and stopped as disc space ran-out. I aborted & moved all the files to a different drive; also changed the "Working Path" in the job. I edited too the undone .avs files to point to the new .d2v locations.

But I notice that RB wants to re-start at v02003700001039.m2v, and it appears certain v02003700001037.m2v (at zero bytes) and v02003700001038.m2v (at 716kB) are corrupt.

Any way to convince RB to re-start at 1037 instead of 1039?

Sorry to ask, but the darn thing is at 85% and if there's a way not to re-do from scratch I'd like to try! :o

[jdobbs]

It determines them by count. The value "Encode_Progress=" in the REBUILDER.INF file keeps track of how many of the required encodes have been completed. The count isn't incremented until the encode is complete, so it isn't likely that it would be off. But if for some reason you want to start a little earlier, you can always subtract from the counter.

[laserfan]

It appears to be working just fine now!

Thanks jdobbs for your amazingly fast reply! :eek:

:thanks: