Nandub Keyframe distances

[scmccarthy]

How do I change the default keyframe max and min dist from 300,100 to 500,24? I like to allow for fast cuts between cameras and concentrate keyframes more at the scene changes.

Stephen

[manono]

Hi-

If you haven't already, go into the Options Tab and uncheck "Hide Advanced Tabs". Then in the Stats File Editor Tab you'll see that the default max/min keyframe distance is 300/50. After opening the first pass stats file in the NanDub Files Tab, fool around in there to change the max/min to anything you like.

[scmccarthy]

@manono

Problem is I want 500/24 to be the default. Is there some registry hack I can perform?

After I change it, do I have to hit auto and save? I would love it if I did not have to intervene on the automatic encoder for this, since this applies at all the movies.

I do a lot of editing of the Avisynth file prior to encoding:# SOURCE
video=mpeg2source("D:\MATRIX_RELOADED_DISC_1\KEYMAKER\KEYMAKER.d2v")
audio=wavsource("D:\MATRIX_RELOADED_DISC_1\KEYMAKER\KEYMAKER.wav")
audiodub(video,audio)
AssumeFPS(24,FALSE)
# TRIM
trim(0,35913)
# CROPPING
crop(12,58,696,360)
# RESIZING
BicubicResize(752,320,0.1875,0.5)The wave file is really an mp3 file. I can let Nandub deal with it as avi audio instead of wav or mp3 audio. In BeSweet, change framerate from 999 to 1000, set delay from the ac3 file, and choose the Wave-MP3 lame option. The wavefile as avi audio trick solves my synch problems.

Anyway, I diverted the topic to explain what I do do to intervene GordianKnots automatic encode process. I want to avoid intervening between the two passes however. You can understand that right? It would be a lot easier. Also, I am a little rusty on exactly how I must save the stat file. I guess I will look it up again, but I am not sure if I am getting keyframes closer than 50 frames at times.

Cancel that, I just checked by opening my avi file in VDMod. There are keyframes closer that 24 frames, so maybe it does not use this info anyway. It does not matter to me, just want to know how to control the keyframe placement if it is still possible.

*Sigh*, the question is, can I change the default as it is shown on the stat file editor?

Stephen

[manono]

Hi-

Unless you load a GKnot VCF before encoding, you're using the NanDub default keyframe settings (max/min=10 sec./24 frames). If you don't like those settings, then set them the way you want, and create your own VCF in File->Save Processings Settings, and just load that whenever you open NanDub to do some encoding. Then those keyframe settings will be transmitted into the stats file, and you don't have to fool with it in the Stats File Editor Tab.

Also, most people believe the alternate scene detection algo is better than the default one. It's in Options->Preferences->Scene, and check the "Use Alternate" box.

Edit: I was thinking about this some more. What I suggested will work only if you do the encoding yourself directly in NanDub. If you do it through GKnot, then it has its own ready-made VCF files. You'll find them in the GKnot->NanDub folder. The thing is, I don't know which ones it uses under which circumstances. So, maybe change them all after opening them with something like Notepad. For example, the GordianKnot_default.vcf has this at the top:

VirtualDub.video.SetDivX(0,9999);

and you'd change that to how many seconds you want for the maximum number of seconds between keyframes (20?). And then further down you find:

VirtualDub.video.SpaceKF(100);

And you'd change that one for your minimum keyframe distance (24).

[scmccarthy]

@manono

20 sounds about right. Changing the VFC files changes GKnots default behavior. Changing GordianKnots settings in the registry is another. If all else fails, recompiling the sources is the third.

I already switched to 24 seconds, I will try the 9999->20 switch too and see how it goes.

Stephen

[scmccarthy]

I know enough not to change the first pass VCF, but not much more for sure.

Stephen