![]() More important for high-motion stuff.Īgain, higher is better. Higher is better, but takes longer to encode. Exhaustive would take much longer, but probably wouldn’t give any benefit whatsoever. UMH will typically give the best quality. Motion Estimation Method: Uneven Multi-Hexagon (umh) Should have a larger effect on film than it does on animation. It also doesn’t add much time to have enabled, so I’d leave it on. It can save some bitrate though anyway, and some people have noticed 1-2% larger file sizes without it (which means you should get an overall quality increase with a static file size in most cases, since I haven’t heard of any negative effects). So where it should help the most, it probably doesn’t. Everyone seems to point at leaving this at Auto so the encoder can decide when to use what, and I’d tend to stick with that.Ī fun bit from mplayerhq.hu – there’s often not a lot to gain from this except during fades where it’ll save some bitrate… except that apparently the “adaptive b-frames” that’s on by default tends to avoid b-frames during fades. ![]() None is bad, and if you’re intent on choosing one, Spacial should be better than Temporal according to the documentation. Feel free to pump this up to 16 if you want – it probably won’t make a lick of difference though unless for some reason it decides that more than 3-4 was needed. There’s another option called “adaptive b-frames” which is on by default (and there’s no setting to turn it off in Handbrake), so the encoder will use however many B-Frames it sees fit to use. I’ve never seen anyone give a good reason to turn it off. You get some quality at the cost of some speed. ![]() Just make sure your video plays fine afterwards. That said, go crazy if you want and try 16. Really high diminishing returns for something you probably won’t notice, and something that might cause issues if you ever try to play your video in a hardware player. According to a document at mplayerhq.hu, while going from a setting of 1 to 2 would improve the signal-to-noise by 0.15dB, going from 6 to 12 would typically improve the signal-to-noise ratio by only 0.02dB but result in a 15-20% longer encoding time. Unfortunately, reference frames are subject to diminishing returns. However if you go too high, both hardware and *some* software players can choke. Here’s a list of the x264 settings I chose in Handbrake, and why: Therefore, I grabbed a torrent of the same TV show, and aimed to create a better quality encode at a smaller file size.īefore dumping into the x264 settings, it’s worth noting that I used a 2-pass encode, and mixed the audio down to a 160kbps Dolby Surround encode. Of course, the best way to see how well you’ve done is to find something to compare it to. File size of between 250-400mb for each 1-hour episode (about 42-44 mins). High quality, even if it takes a while to encode. In short, here’s what I’m looking to get from my encode: Recently, I grabbed the latest version (0.9.3), and decided to encode a TV series from DVD. I’ve used Handbrake in the past to encode movies and various TV series from DVD source. I pulled information on each setting from a few different websites, and while I don’t have any “final results” to show you (and the write-up wasn’t quite completed), hopefully the information’s useful in helping you to better determine what each setting does (and how it will affect encode time and quality), and to come up with your own settings. I wrote this up quite a while ago, and it’s been sitting as a draft since. It’s quite long, but you can find it here. Update (June 25 2012) – I have a more complete & updated version of this write-up now.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |