www.makemkv.com

Just got my new LG drive sorted to accept UHD disks on my Mac but having real issues on my first attempt. MakeMKV throwing up error messages as follows on attempt just to make a backup copy:

MakeMKV v1.12.3 darwin(x64-release) started
Optical drive "BD-RE HL-DT-ST BD-RE BE16NU50 1.01d" opened in OS access mode.
Backing up disc into folder "/Users/xxxxxxx/Movies/backup/BLACK_PANTHER"
Loaded content hash table, will verify integrity of M2TS files.
Hash check failed for file 00045.m2ts at offset 5025294336, file is corrupt.
Hash check failed for file 00045.m2ts at offset 12652308480, file is corrupt.
Hash check failed for file 00045.m2ts at offset 12692416512, file is corrupt.
Hash check failed for file 00045.m2ts at offset 12692613120, file is corrupt.
Hash check failed for file 00045.m2ts at offset 12868184064, file is corrupt.
Too many hash check errors in file 00045.m2ts.

..and that's just a third of the way in.

A verdict?

Try version 1.12.2 on it; older versions can be downloaded from /download/old/

Make sure disc is clean. These are read errors.

xmenw wrote:Make sure disc is clean. These are read errors.

What he said. Happens again, clean and repeat.

Thanks for the feedback guys. I actually cleaned the disk several times following the advice of an alcohol and water mix (I used isopropyl plus water) and it did actually make it through the hashtag error notices to the end of the backup process but the result was pretty awful. I will try going back a MakeMKV generation to see if that makes a difference in the next week or so and report back.

I'm just hoping its not the drive.

Mike confirmed a bug in the newer version. Using the previous version may result in a succesful rip.

st4evr wrote:Mike confirmed a bug in the newer version. Using the previous version may result in a succesful rip.

I wasn't aware the Mike confirmed a bug in 1.12.3. When did that happen? My 1.12.3 seems to be working very well so far.

rivey wrote:

st4evr wrote:Mike confirmed a bug in the newer version. Using the previous version may result in a succesful rip.

I wasn't aware the Mike confirmed a bug in 1.12.3. When did that happen? My 1.12.3 seems to be working very well so far.

Here:

http://www.makemkv.com/forum2/viewtopic ... 12&t=17754

Following the advice here I've reverted to 1.12.2 and trying a different disk, giving it a clean beforehand.

Same result.

The drive will start off well ripping through the disk at up to 14.0x speeds, gets half way through and the error messages come back. Another clean, this time the drive slows right down and the error messages come right at the start. Another clean. The drive's at a snails pace now before giving up. I'm shattered at this result. The BE16NU50 is brand new, I had it reverted to the previous firmware and is the only one recommended to work on a Mac as its an external drive. If the drive is at fault I've really nowhere to go, and I've spent so much money on this already.

I just experienced the same thing, coincidentally on the Infinity War disk (region-free international version). I ripped the 2D and 3D versions of the film and both threw this error throughout the initialization process, and then just at the beginning of the rip. They both ripped successfully and seemed to play fine, though I'd have to do a full viewing to know for sure.

I then tested my Black Panther disks which I knew were ripped properly a few months back I've done a full viewing of that film. The same strange errors presented during initialization and at the beginning of the rip.

I decided to try reverting to 1.12.2, and the errors went away on all disks. Just as an aside, I haven't had to use a keys_hashed.txt to rip any of my disks so far. Let me know if there's any logs I can provide to help squash the bug (if it is indeed one).

A propos to the earlier comments but with the latest version (1.14.2) does anyone know if there are ongoing issues with this version or is it now safe to upgrade, given the earlier issues with 1.12.3 and processing these disks?

sorry that's 1.14.1.
I've found something interesting with this latest version: not sure if its the upgrade or just the disk but with MISSION IMPOSSIBLE FALLOUT, processing it successfully with this newer version, however the file is unplayable on my media player (Dune Solo 4K) which says the file type is unsupported. I've checked the file and on the face of it it seems no different to, say, ANT MAN AND THE WASP which has the same video specs (mpeg H, HEVC, H265) but was processed with the earlier 1.12 version and plays fine. I'm going to process the same disk with the earlier version and see what happens, but has anyone else had this problem?

ok an update.
I've managed to produce a workable mkv file of FALLOUT 4K which will play on the Dune by getting rid of all the PGS files using MKVToolnix after producing an mkv file from MakeMKV 1.14.1, so it turned out to be the disk after all (at least as far as my media player is concerned). Whew! Always good to find a solution. Wonder why it happened.

So if I cannot rip Mission Impossible Fallout, it is the fault of the Disc which mean I need to replace it? I got the following message on two different drives.

The volume key is unknown for this disc - video can't be decrypted
DEBUG: Code 0 at 3-&G:T%sH~_VhW_a:29396115
DEBUG: Code 0 at 3-&G:T%sH~_VhW_a:213134262
Failed to open disc

audioguy wrote: ↑

Tue Dec 04, 2018 10:45 pm

So if I cannot rip Mission Impossible Fallout, it is the fault of the Disc which mean I need to replace it? I got the following message on two different drives.

The volume key is unknown for this disc - video can't be decrypted
DEBUG: Code 0 at 3-&G:T%sH~_VhW_a:29396115
DEBUG: Code 0 at 3-&G:T%sH~_VhW_a:213134262
Failed to open disc

https://www.makemkv.com/forum/viewtopic ... 12&t=16883

See section 'How do I discover the key for a disc I have?'.