Nth pass

[clodomiro]

Hi, is there anyway to resume a 5.05 encode? Sometimes after the first pass is ready something happens, like power interruptions, and then I have to do both passes again. I've noticed that if the first pass is concluded I'm left with an avi file (that isn't playable) and 2 small log files, is there any way to use these to make the nth pass? TIA. I'm using .28

A.Lanza

[N_F]

Yes, you can use one of the log-files (the big one). But Gordian Knot doesn't support this at the moment (I've been meaning to report it, but I'm sure len0x is aware of it). Try either doing it manually with VDub or try Enc. Just select multipass nth pass and check the settings.

[clodomiro]

Ok, thanks. I'll wait for the next time I get this problem, as I already restarted the whole process. I tried using both log files with just nth pass checked, but that didn't work, and I've never used vdub manually other than to split and merge sound.

[len0x]

Originally posted by N_F
Yes, you can use one of the log-files (the big one). But Gordian Knot doesn't support this at the moment (I've been meaning to report it, but I'm sure len0x is aware of it). Try either doing it manually with VDub or try Enc. Just select multipass nth pass and check the settings.

If you doing Nth pass - it won't help. Divx 5.0.3 and higher rewrites log files on the fly. If encode is terminated they are left in inconsistent state and cannot be reused. So I'm not gonna support them in GK :)

[hakko504]

any possibility of you automatically saving a copy of the log you are going to use before actually using it?

[N_F]

Originally posted by len0x
If you doing Nth pass - it won't help. Divx 5.0.3 and higher rewrites log files on the fly. If encode is terminated they are left in inconsistent state and cannot be reused. So I'm not gonna support them in GK :)
I can understand why you'd belive this, I did too at first. When you start the n-th pass the log file does indeed seem to be overwritten, but if you stop the encoding in the middle the log-file will be reverted back to it's last working state. So DivX seems to stash it away somewhere.

This is at least the case with 5.03, I've never checked with 5.04 or 5.05, but I don't see why they should have changed it.

[len0x]

May be it's the case if you stop encoding manually in vdubmod...
But what if computer crashes ? Or you kill encoding ?

[N_F]

I'm quite certain it works like I described even if the computer crashes, don't ask me how it works though...

I'll check if noone else will.

[clodomiro]

HI guys, just wanted to say thanks for looking into this.

[len0x]

Originally posted by hakko504
any possibility of you automatically saving a copy of the log you are going to use before actually using it?

that's a good idea, probably even not difficult to implement...

[len0x]

If it was only for DivX log file, I could easily restart encoding from any pass. Unfortunately I'm tired up to vdenc.log, which is used for calculating the number of frames, and overwritten everytime.
So it's not simple to deal with that (definitely not for 0.28.2 final)

[N_F]

Originally posted by len0x
Unfortunately I'm tired up to vdenc.log, which is used for calculating the number of frames
Why do you need to know the number of frames? I haven't understood why vdenc.log is used by GK for normal encodings. For comp. tests, sure, but normal encodings?

[len0x]

Originally posted by N_F
Why do you need to know the number of frames? I haven't understood why vdenc.log is used by GK for normal encodings. For comp. tests, sure, but normal encodings?

For bitrate recalculations and IVTC adjustments...
(normal log file was used instead of vdenc.log in 0.27, it's not something I imlemented...)