features for 0.28 final

[len0x]

Now that I'm getting more stable with alpha versions and before
hitting beta stage I'm thinking about the following new features to implement (feedback from seniors is really welcome here :) )

1) as I already described in another thread, I'm ready to do simple auomation which doesn't require you to press codec settings buttons everytime you do encode. Defaults can be picked up and used instead (like a first step to profile system). Although first time you will have to create default settings (unless we provide defaults with the installer, but for me it's tricky, coz registry contains not only codec, but decoder postprocessing settings as well - I don't wanna mess around with that...)

2) Compressability check. I've had some interesting chat with Jonny over email. I hope I remember correctly what was it about correctly :) Basically we can do comp check with diff quantizer and predict total size based on that quantizer. Having that we can do this (in case of using credits):
- quicky do comp test for credits with quant you're usually use
for that and predict size of them
- then recalculate bitrate & size for the main movie
- and do comp check for main part

So basically you know all the bitrates before you start encode and recalculation on the run time is not needed anymore (of cource for that to work properly you have to process audio before...)

3) Support for crop&resize inside the codec. I've heard some weird stuff about it, but it shouldn't be difficult not to include filters and just set some registry fields...

So what do you think?

p.s. some minor cosmetic things which are submitted at SF will be done as well... So don't post such things here - I can't remember all of them - need rather a proper list :)

[Doom9]

I don't know if it's worth bothering about the internal crop and resize options of the codec.

[N_F]

Originally posted by len0x
3) Support for crop&resize inside the codec. I've heard some weird stuff about it, but it shouldn't be difficult not to include filters and just set some registry fields...
I'd say the general opinion is not to use the internal crops and resizers. Avisynth does that work better.

[jonny]

So basically you know all the bitrates before you start encode and recalculation on the run time is not needed anymore (of cource for that to work properly you have to process audio before...)

Make attention on this! :)
Recalculations at runtime is always needed (since an error is present in comp.test/size prediction).
The goal of my suggestions is to give to users more analisys tools (so the user can have an idea of the final credit size and how this affect the rest of the movie)

One more suggestion:
It will be a good idea to use an higher % of sampling for the credit analysys (so for example use 10% for credits if the comptest is with 5% of the movie).
This is because the lower is the clip length, the higher is the error on size prediction.

It's all for now :)
Good work!

jonny

[len0x]

Originally posted by jonny
Make attention on this! :)
Recalculations at runtime is always needed (since an error is present in comp.test/size prediction).


True, I didn't mean that I'd like to remove recalculations, just that they are not important for ppl who don't encode stuff in the GK...


Originally posted by jonny
One more suggestion:
It will be a good idea to use an higher % of sampling for the credit analysys (so for example use 10% for credits if the comptest is with 5% of the movie).
This is because the lower is the clip length, the higher is the error on size prediction.


Yeah, I was thinking about that myself...

[len0x]

Originally posted by Doom9
I don't know if it's worth bothering about the internal crop and resize options of the codec.

That's what I wanted to hear :)

Just curious is anybody actually using those features ?..

[maurus]

Originally posted by N_F
I'd say the general opinion is not to use the internal crops and resizers. Avisynth does that work better.

I agree with this.

[jonny]

True, I didn't mean that I'd like to remove recalculations, just that they are not important for ppl who don't encode stuff in the GK...

I see, i've misunderstood you :)

[colordog]

If I may humbly throw in a suggestion?

As a previous user of v. 0.2x of GKnot (thanks WEF!), I'd adjust the brightness and gamma using the luminance filter in DVD2AVI. As I understand, that color information from DVD2AVI is now ignored since we've switched to faster YV12 - and I'm certainly enjoying a great speed encrease. :D

With the 0.28 alphas, I've been using Tweak to change the brightness and contrast of movies - I thought it might be useful if on the "Save and Encode" screen where filters are choosen, if four variable boxes for Tweak are provided. Thus, the user could pop in a Tweak number, hit "Preview", then close the preview, quickly adjust the number if it isn't right, quickly preview again, etc.

Not a big thing really, but I (perhaps mistakenly) thought this would be an easy thing to do.

Finally, thanks to WEF for licensing this, and to all the developers working hard and generating new bugfixes so damn fast!

[WTS]

Originally posted by len0x
That's what I wanted to hear :)

Just curious is anybody actually using those features ?..

I sometimes use those features in cases where I'm more interested in speed than quality.

[sh0dan]

Originally posted by colordog
If I may humbly throw in a suggestion?

As a previous user of v. 0.2x of GKnot (thanks WEF!), I'd adjust the brightness and gamma using the luminance filter in DVD2AVI. As I understand, that color information from DVD2AVI is now ignored since we've switched to faster YV12 - and I'm certainly enjoying a great speed encrease. :D


It is possible to map these settings to ColorYUV, as it is capable of doing all these adjustments (and much more).

[decadence]

If I may humbly throw in a suggestion as well,I
would find very usefull a small feature in order
to cut the avi in an exact size when you go for
two cds,which i imagine would relative easy as my
limited knowledge would allow me to say.

[colordog]

@decadence

I'm not sure I'm understanding your exact request, because it already seems to exist on all the versions of GKnot. On the 'Bitrate' tab, you can specifiy the exact file size that you wish your AVI to come out to.

Do you mean that you want GKnot to cut a ~1400MB AVI into two 700MB files for you automatically after muxing? That might be cool. I manually do that with Nandub, but automation of that would be nice. :)

[colordog]

Oh yeah -

Could add a radio button be added for TomsMoComp under Deinterlace options? (If it's easy, that is).

[CHAOSMAN33]

maybe add support for more filters, like autodub has a pull down window for every time of thing, ie. deinterlace, ivtc, smoothing etc.

[Rash]

Originally posted by len0x
Just curious is anybody actually using those features ?..

I used them in all my non-GKnot encodings. I do prefer AVISynth resize though (I'll never use the internal feature anymore ;)).

[len0x]

Originally posted by colordog
Oh yeah -

Could add a radio button be added for TomsMoComp under Deinterlace options? (If it's easy, that is).

It is easy.. what's the parameters for the filter - (1,5,1) ?

[colordog]

@len0x

Yuppers - it's even already REM'ed out in the Aviscript. :)

[decadence]

yeap,that's what i mean colordog,glad
you find it cool.

[Blankman]

1) Encoder paths and any other application paths should be placed in a main tab like "Options" where it is easily accessiable instead of being hidden away in "Encoder Control", or spread across several locations.

2) The .setting files contain:
..... "Nth Pass debug file name"="c:\\newrc.txt"
..... "MP4 File Name"="c:\\test.divx"
..... "YUV Dir Name"="c:\\yuv"
near the end of the file. A root path override option (i.e. F:\Temp may be used instead of C:\) would we useful.

3) Support for customized VirtualdubMod job scripts throught either a simple "Edit" button on the Encoder Control Panel, or an ASCII editable job script template file. The latter with a pulldown for selecting a job script template would provide sufficent flexibility for the advanced to stay within Gnot.

4) Ability to set text editor and media player of choice for "Edit" and "Preview" buttons.

5) "Edit" button alreadys give me the ability to cutsomize my AviSynth scripts, but it would be even more convient if I could construct my own AviSynth script template for Gnot to complete and submit for encoding.

6) Ability to queue up and schedule background execution of Compressibility Check.

7) I should be able to adjust cropping in increments of 1 not 2. It can be perfectly acceptance to have odd values on all four crop boundaries. (Just give me the darn gun. If I shoot myself, so be it.) Only the image dimension on both axis needs to be a multiple of 2 for YV12. Except when deinterlacing. Then the image dimension on both axis needs to be a multple of 4 because the 2x2 square is taken from a field and not from a frame.

[len0x]

all this probably describes ideal version of GK, which we will get to eventually :)

about point 7 - you're wrong: http://www.avisynth.org/index.php?page=DataStorageInAviSynth

the only thing I'm changing - I'll relax width from mod4 to mod2
(not required for deinterlacing)

[SubConscious]

I was just wandering if it is possible:

1)To have the ability to encode credits in two passes but with very low bitrate. That way the size will be small and the picture better. I don’t mind if it takes me 10 minutes more to have better quality for my credits.

2)To remove all the useless tabs in the main window like Ripping, Nandub Files, Stats File Editor, Subtitles, File List Writer, Help(who uses the help from the program when we have the guides) and move the Encoder tab after Resolution. Small useless changes, I know, but I would like to see something like that.

Continue the good work!!!

[colordog]

I do use the Ripping Tab (to quickly launch DVD2AVI and DVDdecrypter, and occassionally use the Subtitles tab.

What is the purpose of the "Nandub Files" and "Stats File Editor" and "File List Writer"? I've encoded hundreds of things with GKnot, and never used those, come to think of it.

[len0x]

1) That would be no, for now... (it's a pain to implement at the moment and we have more priority stuff to do first...)

2) The only tab we can remove now safely is I guess "File List Writer", others are used for divx3 I think...


2ALL
P.S. Features for 0.28 are finalized - after alpha 12 there will be no more additions, just bugfixes...
(I decided to leave comp test for now, since Jonny has Enc which does the job...)

[crusty]

N_F:
I'd say the general opinion is not to use the internal crops and resizers. Avisynth does that work better.

So true. And sometimes necessary. I've used scripts with many filters in a row, and some of those needed to be before crop, some where best put behind it, and some I would place only after resizing. With the internal codec tools you might gain in speed, but you lose bigtime in flexibility.

WTS:
I sometimes use those features in cases where I'm more interested in speed than quality.

I suppose you mean on things like TV captures or something. I haven't tried the internal filters because basically everybody in this forum says not to use them. Is the speed difference noticeable?

Len0x:
the only thing I'm changing - I'll relax width from mod4 to mod2

Isn't there some way to automate the mod requierements?
Say for instance your using a filter chain with mod2 and then you want to add a filter that only works in mod4...it would be nice if GK would somewho give a warning then, or automatically check if mod4 would be possible, and then change to mod4.
Just a suggestion...keep up the good work you guys!

[len0x]

Originally posted by crusty
Isn't there some way to automate the mod requierements?
Say for instance your using a filter chain with mod2 and then you want to add a filter that only works in mod4...it would be nice if GK would somewho give a warning then, or automatically check if mod4 would be possible, and then change to mod4.
Just a suggestion...keep up the good work you guys!

The way GK works right now is you crop&resize first and then do filters (otherwise lots of things could be done easier). I prefer solution which works always (like right now), so unless you starting messing with resolution/crop manually everything should work ok...

[BiaTch 5.0]

Originally posted by len0x
(I decided to leave comp test for now
Major bummer :(

[BiBo]

@len0x

2ALL
P.S. Features for 0.28 are finalized - after alpha 12 there will be no more additions, just bugfixes...
(I decided to leave comp test for now, since Jonny has Enc which does the job...)

:scared:
There's a little change request for the auto-splitting (for 2 CDs):
Since I use to put additional stuff onto the 2nd CD, it would be nice NOT to split at exactly the half, but to completely fill the first disk and put the rest on the second.
That might be not too much work to do?

[len0x]

the only thing that can be done easily is settings like this:
"reserve space on each cd in Mb: "

All other settings will not be generic (some ppl whant to include subs or other stuff on both CDs, some only on second, and some do 3cd rips...)
Too many options and opinions...

[cult]

Could you please fix the way you have to enter your own size of final avi?I mean the way you have to highlit a number and write upon it in the box MB

[len0x]

that'd be the best solution, I guess.
No need to specify additional parameters...

[cult]

yes,no additional parameters,I agree.I only mean the way.Suppose you have 700mb in the box.If you want to put 25 you have to highlite the"70" and overwrite them.Sometimes it doesnt work though.It could be better to let you erase the number or whatever numbers you want and put the number you want.I cant explain it better

[len0x]

I already made that combo-box editable (will be in alpha 15...)

[cult]

thank you:)

[MinosK]

HELLO!!

Your GKNOT version is really great...
Why don't you make "Split final file into CDs" feature to split it.. but in cd2 to include some time of the first (30 sec maybe)...

Originally posted by len0x

(I decided to leave comp test for now, since Jonny has Enc which does the job...)

What do you mean?? The comp test isn't working well in beta?

A request... Can you make GKNOT to save the Encoding Queue? Just to prepare our movies, save the queue and load it whenever we want to encode..

Thank you....

[TheWEF]

Originally posted by MinosK
Can you make GKNOT to save the Encoding Queue?

that's a pretty difficult change an will not be in 0.28.

i still can't see what it's good for anyway! you can prepare all your movies to the point where you are about to press the button to add the job - there you just close the encoder window. later you just select your project slot, press "add job" and the queue is reestablished in a second...

wef.

[len0x]

Originally posted by MinosK
HELLO!!
What do you mean?? The comp test isn't working well in beta?


Read my first post of this thread - and you'll know what I mean :)

Regarding saving - yes, it'll take a while before we implement that...

[len0x]

Originally posted by TheWEF
i still can't see what it's good for anyway! you can prepare all your movies to the point where you are about to press the button to add the job - there you just close the encoder window. later you just select your project slot, press "add job" and the queue is reestablished in a second...

wef.

Funny - I never used slots :)

[buzzby]

Don't know if you can add this feature cos it might only be a part of the divx codec but would it be posibale to get the codec to remember the last lot of setting it was given. I try to get all of my encodes to conform to the new divx home profile. Any way getting to the point would it be possibale to get GKnot to remeber the last resolution used and the FPS rate. Also it is possiable to get the credits option to remener all of the last settings.



Thanks for your time



Buzz

[len0x]

I have slight difficulty understanding what you're actually asking for, because:

1) On the main window -> option tab you can save default settings for the codec... (and never use codec settings anymore)
2) Resolution & crop is being restored every time GK starts, so all you have to do just open d2v and press save avs straight away...
3) Why do you want credits to be restored since last time I checked every movie had different start position for them :)

[buzzby]

To get a divx movie to conform to a profile like the home profile you cannot use normal credit incoding i now incode the credits on a 1-pass at 250kbs which does the job that is what i like to be remembered. Also within the divx codec you have to type in the resolutuion of the movie and the frame rate and it is recoreded in the summery section of the avi. I know GKnot rembers all of the settings it was the settings within the codec that i was wondering if they could be remember.

Hope this is clearer or i have not setup the defaults correctly


Thanks for your time again and a great product



buzz

[len0x]

1) credits - they are encoded as 1 pass quant base. I'm pretty sure you can find which quantizer will be equal (on average) 250Kbps
Then this setting can be saved forever...
2) are you doing crop&resize inside codec ? not in the AVS ?
(and couldn't find fps settings you're talking about) We are not gonna support them anyway, but I still see no probs saving them as defaults on the main window -> Options -> Codec defaults...

[buzzby]

Hi ithink i have sorrted out the credit encode default settings that fine.

I resize within GKnot i don't use the codec to resize.

Have now looked at the defualt setting in the optioons tabs it seems that the codec itself will not let you remember the resolutions so i'll fill it in if i want.

Thanks for you time it looks like it now remembers all i need it to



buzz

[Liquid Crash]

I think that you should join together all the divx3 related tabs like nandubfiles and stats file editor, because gordian knot looks pretty intimidating to people who dont know much about dvd ripping. and the file list editor is really useless as well! that would tidy up gordian knot a lot.

[len0x]

next beta will have an option to hide all those tabs (which will be enabled by default).

[Big_Berny]

Could you add an option to make greyscale-credits?
It would be great

Big_Berny

[SiXXGuNNZ]

how about selecting you are using a CBR mp3

I tend to use VBR with 1 cd rips only, well because, I can never get a VBR to sync in a 2cd rip.

edit: I would like to explain more why I would like a cbr option, when muxing you either choose vbr or cbr in vdubmod, obviously if you use a cbr it will choose vbr in the script it makes(I assume) since you can't hit a box that says cbr

[BiaTch 5.0]

Chapter Support in GKnot would be good.

[buzzby]

would it be possiable to have another credit encode option so that you can choose to encode credits just as a straigth 1-pass. i only ask beacuse you have to chage the credit encode option each time.

Also would it be possiable for GK to automatically add the res and FPS to the divx profile of the movie it is encoding?




Thanks for you time and great program


Buzz

[drebel]

Could you add an option to make greyscale-credits?
It would be great

Big_Berny

Avisynth has this great option
Greyscale()
I'm pointing this because for example the same option from within the codec (See XviD) has problems with color shifting (usually towards green or brown)

Btw, i'm using this form of script to specially treat start-ending credits :

mpeg2source("F:\THE_IMPOSTOR\VIDEO_TS\impostor.d2v",cpu2="xoxooo")
crop(6,6,708,564)
Undot()
Lumafilter()
Mergechroma(blur(1.4))
start=trim(0,1329).BilinearResize(704,512).Lumafilter(-10,1).Undot().Convolution3D(preset="vhsBQ").deen().Unfilter(10,-50)
main=trim(1330,128815).LanczosResize(704,512).Blockbuster(method="sharpen",block_size=3,detail_min=1,detail_max=100,luma_offset=-1,luma_threshold=10,strength=30).deen("a3d",1,10,14,2.2).UnFilter(10,-10)
end=trim(128816,0).BilinearResize(704,512).Undot().Greyscale().Lumafilter(-10,1).Convolution3D(preset="vhsBQ").deen().Unfilter(50,-50)
return start+main+end


Is there a way to implement this structure of trim-return in GordianKnot?You already have the frame value of first end credits frame.I wouldnt mind if Gnot asks me for the value of the last frame of start credits also...

And one more thing.In avisynth 2.5 because of filters autoload function (inside plugin folder of avisynth ) there 's a problem when calling a filter though LoadPlugin function (one must have either double versions of the filters or just delete the line :( )

regards,
george

[leadman584]

I'd also really like to see a CBR mp3 option in the drop down menu for audio set up. I recently helped a buddy set up his system to use GKnot .028 beta 4, and he is a true newbie. I have several friends who'd like to learn to use this wonderful tool, but my explanations on how to do CBR mp3 outside of this tool is confusing them.

Also I'd like to thank you for making .avs editting easier from within GKnot. If it weren't for the incompatible sound, there would really be no need to exit GKnot to process a video.

[len0x]

Originally posted by leadman584
I'd also really like to see a CBR mp3 option in the drop down menu for audio set up.

beta 6 will do the job...

[leadman584]

Thank ya much, I'll set up an encode with this new version before I go to sleep.

[SnotRat]

I would like to see reverse cropping in Gknot so that it adds black border to the picture. That way you'd have the option of getting a perfect AR without having to crop pixels.

[leadman584]

The CBR MP3 works well. You have made this program very newbie friendly. I have several friends that will enjoy learning to use this version of GKnot. The folks I've tried to help in the past to use GKnot have always stumbled on the VBR(ABR) audio output by previous versions. Thanks to your great work, I don't have to explain what a GUI is:D

[len0x]

Originally posted by leadman584
The CBR MP3 works well. You have made this program very newbie friendly. I have several friends that will enjoy learning to use this version of GKnot. The folks I've tried to help in the past to use GKnot have always stumbled on the VBR(ABR) audio output by previous versions. Thanks to your great work, I don't have to explain what a GUI is:D

be aware that there was a small bug in the beta 6: it always produces 128 CBR stream (no matter which bitrate u specify). It's fixed for the final version...