Makemkv to handbrake vs only handbrake
-
- Posts: 48
- Joined: Fri May 29, 2020 5:17 pm
Makemkv to handbrake vs only handbrake
In terms of speed, encoding quality, space savings, whats better? Using makemkv to rip an mkv from the bluray, and then compressing with handbrake, or compressing straight from the bluray with handbrake?
Re: Makemkv to handbrake vs only handbrake
Handbrake cannot encode "straight from BD"; it has to have something in between to remove the encryption. If that something is MakeMKV as a stand-alone ripper or acting as a proxy to remove the encryption, the results will be identical, for the same handbrake settings.
Using MakeMKV as a proxy limits you to the speed of the encode. Using MakeMKV separately, you can be ripping more than one disk while handbrake is encoding the first.
Using MakeMKV as a proxy limits you to the speed of the encode. Using MakeMKV separately, you can be ripping more than one disk while handbrake is encoding the first.
-
- Posts: 48
- Joined: Fri May 29, 2020 5:17 pm
Re: Makemkv to handbrake vs only handbrake
Cool, but i thought handbrake could decrypt and rip blurays aswell? Maybe i was mistaken.
-
- Veteran User
- Posts: 4859
- Joined: Wed May 04, 2011 11:06 pm
Re: Makemkv to handbrake vs only handbrake
No it can’t.
For ripping use a ripping tool like makemkv.
For encoding use an encoder like HB.
That way you can chop and change if needed.
For ripping use a ripping tool like makemkv.
For encoding use an encoder like HB.
That way you can chop and change if needed.
Re: Makemkv to handbrake vs only handbrake
Handbrake uses libraries to read DVD and BD structures, but those libraries do not remove encryption. In both cases, though, there are THIRD PARTY libraries that can do the decryption to a point. The BD library requires access to a "key" file to work.
Even when the 3rd party libraries work, they do not handle errors well. When the data stops flowing, handbrake assumes that the rip has finished, and stops encoding... without saying that there was an error, because it didn't know it.
Even when the 3rd party libraries work, they do not handle errors well. When the data stops flowing, handbrake assumes that the rip has finished, and stops encoding... without saying that there was an error, because it didn't know it.