Gknot compresses Credits badly

[kagoru]

GKnot doesn't do well when compressing credits.
First of all it doesn't let me enter the value at which compress the end credits (it stays at 12). And when I do the credits at that level I get about 30-40 MB Files (way too big imo).
When I use Nandub though and the end-credits-feature and set it to let's say 120kbps I get and 8-10 MB File.

Would it be possible that Gknot let's you enter the kbps for the end credits and uses that value for nandub?

[yosemite]

i put the Encoding Credits Level on "0" and get a Credits-file of ca. 15-20MB

[Acaila]

If only GKnot would incorporate some extra things to decrease credits filesize.

-TemporalSmoother filter at medium-high setting
-Coring filter for scrolling text on black background type of credits
-very low bitrate
-maximum quantizers (mQ=MQ=31)
-bilinear resize instead of bicubic

Doing this manually I get about half the size Yosemite gets, typically 7-10MB, and credits are still very well readable (as if anyone every reads them).

Maybe suggestions for future releases?

[kagoru]

how does GKnot encode the credits anyway?

There is no "constant" Bitrate for nandub, is there?
I have used the end-credits-feature so far and put a 1 at start of end credits (I use divx 3.11a)

@Acaila
How do you handle the flickering? I think it's very annyoing. And what bitrate do you use to encode you credits?


TIA.

[TheWEF]

kagoru, what are you doing? :rolleyes:

well, i will not explain all that again, please read doom9's guide.

...and put a 1 at start of end credits...

???

you should put the number of the first credits-frame here. something like 170000. just move to the right position in the video-window and press the button! - then save TWO avs-frameservers...
later you can select any drf or quality-level you want.

btw.: it's not possible in nandub to compress credits as well (automatically) as with gknot.

wef.

[kagoru]

@ TheWEF

Thanks for your reply first.

I'm sorry when I didn't express myself clearly.
What I meant was:
1) I cannot set DRF because when I try to change it it STAYS at 12, whatever I enter (Maybe a bug)
2)I read doom9's guides. I worked on my movie_credits.avs on my own and put a 1 at start credits because the credits start at 1. This way I tried to get a very small credits.avi.

And for some reason when I do the second pass manually and haven't encoded the credits yet and select the movie_credits.AVS Gknot doesn't encode the credits (only when I'm do first pass).

TIA.

[TheWEF]

Originally posted by kagoru
1) I cannot set DRF because when I try to change it it STAYS at 12, whatever I enter (Maybe a bug)

hmmm... are you sure? can't check atm.
but 12 is a good compression, don't you think? ;)

Originally posted by kagoru
2)I read doom9's guides. I worked on my movie_credits.avs on my own and put a 1 at start credits because the credits start at 1. This way I tried to get a very small credits.avi.

And for some reason when I do the second pass manually and haven't encoded the credits yet and select the movie_credits.AVS Gknot doesn't encode the credits (only when I'm do first pass).

it doesn't work that way.
the credits-stuff only works if you do both passes in one go.
atm the only other option is to do everything manually in nandub.

but the whole purpose of encoding with gknot is to do save some steps and do everything in one go...

wef.

[Acaila]

@Acaila
How do you handle the flickering? I think it's very annyoing. And what bitrate do you use to encode you credits?

I don't do anyting about the flickering, since I haven't found the right tool yet. As for bitrate, I used 1-pass encoding at a bitrate of 250. I could probably go lower without any further degradation of image quality, but haven't tried it yet.

[kagoru]

The 12 in the credits-box refers to the DRF-values, right? So Gknot sets the mDRF to 12 and the MDRF to 12, am I right here?

The disadvantage of this is that you get credits that are about 20-40 MB of size. I tried that on my own with nandub. The only way you get smaller files is to change the Gauge levels as well or to set the credit start to frame 1 (It does work. I tested it. I get files that are 8-10 MB big for 220 kbps).

I don't know how to explain it but I just cannot change the 12 for the credits (even in both-passes-mode). Has someone the problem?

@Acaila
You use DivX 4, don't you? That's why you can use constant bitrate. I have used divx 3.11 (so far).
I tried your filter combination. But the result was too blurred for my eyes. I could hardly read the credits. In fact, I used a sharpen filter @30 which helped a lot.

[sierrafoxtrot]

i noticed the credits DRF sticking at 12 too, the way i got around it was to use the mouse cursor to highlight the "2" in 12 and then hit 6 (or some integer larger than 2). that way i've used DRF 16 for credit encoding. another thing you could try would be to copy eg 31 into the clipboard, highlight 12, and just paste. don't know if it'll work ... try it and see.

[kagoru]

Thanks a lot!
You're right! If I mark the "2" in 12 i can replace it. Unfortunately only with 2,3,4,5,6, but better than nothing ;-). The copy-paste trick you suggested doesn't work though.

thanks again.

[Ripe73]

Save the endcredits.avs in GKnot and open it manual in Nandub and set max-minDRF and bitrate.

[TheWEF]

ok - you are right. i will change that and allow higher drf in the next version.

wef.

[Prizm]

Why encode credits at all? I always chop my DivXs when the last
scene fades to black! That's 30MB of space left to increase the
quality of my movie.

Prizm

[kagoru]

You chop the credits off?
I never do that because as a real movie enthusiast you just can't miss the credits for several reasons:

1) All actors are listed
2) Every song in the movie is listed (not the same as a soundtrack)
3) I like to listen to the music that is played when the credits start

30 MB is a lot for credits imo. That's why I tried to keep the filesize down while keeping the credits readable (my last were 10 MB).
I don't think that 10 MB is gonna improve you quality significantly.

[Prizm]

Yeah, well...I very rarely have a reason to look at the credits. If
I'm that desperate to find out who played a character or whatever, I
can always go rent the movie, or look at the cover.

I understand that it's mutilation of the movie...but in the end, the
fact remains that I still don't watch the credits, and for the sake
of encoding, I'd rather dedicate disc space to something I'll be
watching (the movie), rather than something I wouldn't (credits).
Even if it is only 10MB. Plus it's less hassle when I encode.

But anyways, I hope you find a way to make your credits as readably
small as possible :)

Prizm

[Shaggy]

no offense to anyone but how many people watch the end credits??? i used to delete them on my old rips, i just don't see the point

[Acaila]

Personally I just don't like to mutilate my encodes by cutting the credits off. But I always keep them under 10MB so they don't waste too much space, I can live with 10MB.