Options check in future releases....

[hyperion]

Hello

A suggestion to the 'auto' function of GK.

1) Luma-Correction, (When I do it manually i take 'av. luma Noise' +1 and gain 35% gain. Is there a downside to this..? It seems that the GK-Default.vcf has it turned off.

2) Many guides suggest that 'anti-frezze' is always on. In GK-Default.vcf it is off.

3) In 'both' passes it seems that GK only goes down to 100% bits/(pixel*Frame) if I have entered a too high bitrate.
A function to go for 70% like suggested in many guides. (A input box perhaps..)
Hopes that this isnt too many questions, suggestions for one thread.

Tks for a great program...

P.S. Avi/mpeg1 support would be nice :D

[TheWEF]

first of all, GK-Default.vcf is not used if you encode via the gknot-gui. so editing it will not change anything. the settings used are the same though, you see that in the *_gknot.log files.

Originally posted by hyperion
1) Luma-Correction, (When I do it manually i take 'av. luma Noise' +1 and gain 35% gain. Is there a downside to this..? It seems that the GK-Default.vcf has it turned off.

gknot manipulates the stats-file. it's "luma-corrected" already. so it's not a good idea to use luma-correction in nandub again.

Originally posted by hyperion
2) Many guides suggest that 'anti-frezze' is always on. In GK-Default.vcf it is off.

if you don't get shit or freezes (like me) you don't need it. and encoding is much faster without. atm anti-shit is not supported.

Originally posted by hyperion
3) In 'both' passes it seems that GK only goes down to 100% bits/(pixel*Frame) if I have entered a too high bitrate.
A function to go for 70% like suggested in many guides. (A input box perhaps..)

i don't understand that one...


wef.

[hyperion]

3) In the Gui (first pass), If the bits/(pixel*Frame) goes over 100%, GK recalc the bitrate to 100% and continue to the second pass, and encode... (Am i totally wrong here...)

If it is a high compressable movie, i mean...

Hopes this cleans things up...

Tks in advance...

[TheWEF]

yes, to stay as close to the desired filesize as possible. result is maximum quality for the give resolution.
why go for a smaller filesize if the user wanted even more?

i highly recommend to do a short comp-check before encoding anyway.

wef.

[hyperion]

Hey again...

Well for one thing i would like as much movie on one disc as possible without a Quality-loss. In all the the guides it is recommended to go for 70%. Why not make an an option to 'auto' recalc the biterate to this. (after the first pass i mean.;))

I for one would use it all the time..

Am i getting on anyone's nerves...

The experts nightmare
hyperion

[TheWEF]

100% is better quality than 70%.
100% is the best possible quality and maximum filesize for a given filter combination (resizing, noise,...).

but (example):
70% at 640x272 looks better than 100% at 544x224. that's why 70% is recommended.

got me?

wef.

[hyperion]

Yes, I think so. We all have to learn something every day...

Tks for all your answers, No new questions from at the moment, but 'i'll be back'

Cheers..
hyperion