Log in

View Full Version : Handbrake settings


Vman94
14th February 2010, 18:06
Was just playing around with handbrake today and wanted to see what settings everyone recommends? i want pretty max quality without the sizes being like 20 gigs per movie. Ive bee told that 80% quality should be pretty good and use decomb instead of deinterlace? anyone else have any idea and suggestions? i would love to hear your input. Thanks a lot guys. PS. I use vegas afterwards to convert to mp4 and wmv if that matters to any of you.

Vman

Inspector.Gadget
14th February 2010, 19:10
Re-encoding twice is silly.

invisible
23rd February 2010, 22:47
I use the bitrate controls and change it depending on content. Usually around 2000. It would be better if handbrake used the x264 option of qp, then 18 would be ideal (in some cases). Although I don't know why you're converting to wmv, an inferior format.

porfitron
23rd February 2010, 22:57
We've posted DivX Plus compatible settings at DivX Labs, since DivX Plus HD devices are coming out this year from our CE partners (e.g. Philips, Seagate, etc...).

If you choose MKV as the format and AAC for the audio, these are the advanced settings we recommend:

level=40:ref=2:bframes=2:subq=6:mixed-refs=0:weightb=0:8x8dct=0:trellis=0:vbv-maxrate=20000:vbv-bufsize=25000

I've also used these settings with MP4 container to play stuff on my PS3 and they work great.

Dark Shikari
23rd February 2010, 23:00
I use the bitrate controls and change it depending on content. Usually around 2000. It would be better if handbrake used the x264 option of qpQP should never be used. Handbrake defaults to CRF, like it should.

nurbs
23rd February 2010, 23:27
level=40:ref=2:bframes=2:subq=6:mixed-refs=0:weightb=0:8x8dct=0:trellis=0:vbv-maxrate=20000:vbv-bufsize=25000
Seriously? I mean nothing against level 4.0 and if you recommend fast encoding settings that's alright, but only 2 refs and b-frames, no 8x8 DCT and no mixed refs. Are those limitations on what the DIVX Plus HD devices will be able to play back?

Dark Shikari
24th February 2010, 00:00
level=40:ref=2:bframes=2:subq=6:mixed-refs=0:weightb=0:8x8dct=0:trellis=0:vbv-maxrate=20000:vbv-bufsize=25000
Seriously? I mean nothing against level 4.0 and if you recommend fast encoding settings that's alright, but only 2 refs and b-frames, no 8x8 DCT and no mixed refs. Are those limitations on what the DIVX Plus HD devices will be able to play back?No, they're limitations DivX came up with in order to make x264's output worse so they can more easily compete with it ;)

porfitron
24th February 2010, 00:02
Seriously? I mean nothing against level 4.0 and if you recommend fast encoding settings that's alright, but only 2 refs and b-frames, no 8x8 DCT and no mixed refs. Are those limitations on what the DIVX Plus HD devices will be able to play back?

Hi Nurbs, actually, 8x8dct would be fine, since DivX Plus HD supports both High and Main, and 3 b-frames would be fine. Our latest x264 recommendations are here ( http://developer.divx.com/docs/divx_plus_hd/Creation_with_x264/ ), and as devices are released and we play with HandBrake some more we'll come up with some other recommendations, but as it is, the one I posted seems to be working pretty well as a fast encode.

porfitron
24th February 2010, 00:08
No, they're limitations DivX came up with in order to make x264's output worse so they can more easily compete with it ;)The settings are meant for hardware decode compatibility... if you haven't noticed, we've been sending some love at x264 and GUI projects... is that what the kids call competition these days ;-)

invisible
24th February 2010, 02:31
QP should never be used. Handbrake defaults to CRF, like it should.

Works for me (particularly for very still cartoons or pixels). Will somebody come to my house and rough me up if I use it?

Dark Shikari
24th February 2010, 03:21
Works for me (particularly for very still cartoons or pixels). Will somebody come to my house and rough me up if I use it?QP is intended only for testing purposes. It disables MB-tree, adaptive quantization, and much more.

invisible
24th February 2010, 04:04
QP is intended only for testing purposes. It disables MB-tree, adaptive quantization, and much more.

My mistake. I guess I need to update more often.