
It makes it really easy with graphical handles and auto-play from where you drag the start of the trimmed clip.ĭisclaimer: I know OP asked about Handbrake. This is the one thing I've found Quicktime is actually useful for. It'd be interesting too I think(tho not really a concern to most people) what the power consumption is like in both cases.Īnyway, just thought I'd post that, not trying to start an argument or anything, just a data point.As an alternative, you could use Quicktime if you're on a Mac. I don't dispute that x264 CLI can be tuned to give better results, but if you are looking for a package to click some buttons and get some results, I don't think I'd turn my nose up at QSV. In practical terms to me, that makes QSV much more interesting. Quality wise, I didn't run a test, but using hte eye ball test of skipping through to various points I don't see any outstanding issues. Resulting file for QS was 1.12 GB in 9 minutes encode.

Resulting file for x264 was 1.22 GB, in 13 minutes encode. Handbrake with QSV, preset to balanced (which is the slower of the 2 options) and CQ 20, no idea if it matters. Handbrake with x264 I set to veryfast, left at CQ 20, no other changes.
Clipwrap vs handbrake software#
You give someone a software package and they ask what to use.Īnyway, I was scaling some 1280x720 down to 640x360. But since we're talking Handbrake as a software package, not well chosen settings of the x264 CLI, I don't think it's completely unfair. Now, to be fair, this is using only a single build of Handbrake, using whatever x264 it uses. So tonight I did a very fast/informal test. The only downfall I've seen to RipBot, and this is most likely operator error, is that I haven't had much success making MKVs with multiple audio tracks, unlike Handbrake which makes it so easy to do. Like you said, it's tougher to get going than HandBrake, but it works very, very well in my experience for the most part. Maybe it's because my computer's ancient, but I find RipBot to be far faster overall for Blu-Rays, and the Demuxing/Remuxing process seems to work so incredibly well. The reason I don't like Handbrake for Blu-Rays is that at least in my experience, it can be painfully slow going through the whole process with BD images. Handbrake makes it a snap to include or remove every little thing you can think of. I usually want English subs no matter, but sometimes want Spanish subs for when I have my Spanish-speaking friends come over to hang out. The Miyazaki movies usually have exceptionally good dubs (which I typically can't stand), but sometimes I still want to watch it with the original Japanese language track. I also found it better for adding multiple language/sub tracks, which I do want sometimes, like in anime. This was really important when I went through the long process of converting my entire DVD library. Well, at least in my experience, Handbrake is awesome for DVDs because it is so darn easy to create massive queues and let it just get to work. Atak (the Developer) has shown that his next version will allow for this so you can have the commentary track or dubbed language as a secondary audio stream (in. this is Ars so you can likely go deeper.Īlso of note: Currently RipBot does not allow multiple Audio Streams to be muxed, where Handbrake does. Im not sure that distinction is necessary for the audience or if that level of detail might be a distraction or confusing, but hey. I know I use the phrase sometimes, but they are GUI Front ends that automate the individual frame servers and encoders and muxing tools into a singe interface thats easier to use.

Perhaps I might reword the references to Handbrake and RipBot as encoders (referring to the conclusion section). I've bookmarked and will be using using this as a reference when I introduce people to the wonderful world of transcoding and understanding the various tools that are out there.

My own views of the pros and cons of each application match yours (I might add that all tools and codecs in RipBot are user upgradeable - As X265 is in such heavy development, I've been updating that on a weekly basis as the last 1.18.1 shipped with x265 1.4 and we are at 1.5+200 currently in stable).

Thank you - Very well presented and structured.
