Captured AVI in GKnot ?

[iparout]

Before posting my question, I have to say that I have read both guides regarding this issue (i.e. the one in doom9 site and the sticky in this section), however it wasn't exactly what I was expecting for.

As far as I can understand, none of the above guide, give you the possibility to open up the captured AVI into the Preview Window of GKnot. What I want to do is find a way to load the avi file into GKnot and make it appear on the preview window so as to take advantage of all possibilities that GKnot offers (encoding credits separately, re-calculating bitrate when needed, running a Compressibility check e.t.c).

Is there any way I can achieve what I want ?

I have figured that if I manage to create a .d2v file out of the captured AVI file, then I'd be able to normally open the .d2v file with GKnot and work as I usually do. However I doubt that making a .d2v file out of the AVI is possible. Am I wrong ? If you know a way to do it, please let me know.

Thanks in advance for any help.

[Darksoul71]

Hi !

>>Is there any way I can achieve what I want ?
No, because GKnot uses a unit to access the DVD2AVI project via MPEG2DEC.DLL.

A new function needs to be written to access AVI for the preview function of GKnot. That´s why encoding AVI in GKnot is still quite tricky and needs more work to be done.

-D$

[theReal]

You can use some of the most important functions from Gknot for avi to Divx5 encoding, but not all of them. There has been a guide on how to do it, but I can't find it anymore.


If you enter the number of frames from your avi file, you can use the bitrate-calc, then enter the resolution manually and you can use the resolution calculator.

The compress test you can use like this:
Take a Gknot avisynth script and adapt it for your avi file (you'll need to learn a few avisynth basics to do it, there's no way around it). Uncomment the compress test line "selectrangeevery(280,14)" (or add it to your own, hand-made avisynth script). Open it in VDub and encode it using the following Divx5 compression settings:

Variable Bitrate Mode = "two-pass, first pass"
Log File = c:\compress_test_NNNxNNN.log
Advanced Parameters->Maximum Quantizer = 2 (instead of the default 12)

Set all other settings the way you want to use them (b-frames, pre-processing...) The bitrate you set doesn't matter, I tried everything from 2 to 10000 -> you already set the max quant to 2 which overrides the bitrate setting. Gknot uses some value around 9200, I don't know why (you have to set something, so why not use 9200 ;))

When the encoding is done, take the log-file, replace the "NNNxNNN" with the resolution you chose (i.e. "640x480") and open this log-file in Gknot (with the "Load" Button besides the compress test result field). Voilà! :D

[iparout]

Thank you both for the time you put into answering my question...

I can see how you can do the compressibility test but what about the Credits Encoding which is one of the most valuable features GKnot has ?

[Darksoul71]

Hi !

I can see how you can do the compressibility test but what about the Credits Encoding which is one of the most valuable features GKnot has ?
Well, you can encode movie and credits seperately by hand. Encode your credits at CQ mode (if you use DivX5). After this just substract the credit size from your final movie size and substract credit duration from complete movie length. This should work fine.

So, in example:
You have encoded your credits in 40% CQ mode and the credits are 120 sec long and 30 MB big. So subtract 30 MB from your target filesize (670 instead of 700 MB, etc) and substract 120 sec from the complete movie length.

Hope this helps,
D$

[theReal]

you don't have to subtract the length, you can add the credits to the additional files box in Gknot (and set the frame-count to the length of the movie without credits)

If you make two avs files, one for the movie, one for the credits (just like Gknot does it, using trim(firstframe,lastframe)) you can even use Gknot's Encoder tab. Maybe even the automatic bitrate re-calculation works then. I don't know because I generally don't like too much automatic recalculating. I want to encode the credits manually, try different settings, and when I'm ready, I encode the movie. I don't like to re-encode a whole movie just because I don't like the credits in the end, or because some automatic calculation failed...

[iparout]

I C... Will try that. Thatnk a lot guys.

[iparout]

OK, I just tried what you suggested and I have a few more questions :

The compressibility test was done through AviSynth the way you described and the outcome was good (thanks !).

1) In order to encode the movie in DivX, should I write an Avisynth script again, load it into VDub and then encode, or should I open up the AVI directly in VDub, apply all filters there and encode without the use of Avisynth ? Is there gonna be a difference in quality between those two methods ?

2) Generally, which of the two (Avisynth or VDub) has the best-quality filters, at least as far as the most common ones are concerned i.e Deinterlace\Decomb, Denoise (Teporal Smoother), Bicubic resize ?

Thanks in advance.

[jggimi]

should I write an Avisynth script again I'd let Gknot create the script for you. You could then run the two passes (and muxing) manually, or you could let Gknot do it.should I open up the AVI directly in VDub I think you'll find that an .avs script will be much faster than using filters in vdub. 1) You stay in YUY2 color space, filters for Vdub use RGB color, 2) you can use fast recompress, which is what Gknot uses when it sends the job to vdub -- with Vdub filters you must use full processing mode.

In addition, you can preview your filters without having to do any encoding, by opening the .avs in Vdub or in any player. I use vdub filters only when an equivalent is not available as an AviSynth filter.

[iparout]

Originally posted by jggimi
I'd let Gknot create the script for you. You could then run the two passes (and muxing) manually, or you could let Gknot do it. I think you'll find that an .avs script will be much faster than using filters in vdub. 1) You stay in YUY2 color space, filters for Vdub use RGB color, 2) you can use fast recompress, which is what Gknot uses when it sends the job to vdub -- with Vdub filters you must use full processing mode.

In addition, you can preview your filters without having to do any encoding, by opening the .avs in Vdub or in any player. I use vdub filters only when an equivalent is not available as an AviSynth filter.

I see... Well, how about the quality of Avisynth filters when compared to VDub ones ? Especially the ones I mentioned in my previous post ?

To what it's worth the AVI will be frameserved from Premiere into Avisynth or VDub, cause Premiere has much more editing possibilities than any other program.