www.makemkv.com

There hasn't been an update to the version since I posted this a few months back.

Mike - Any word on if this is getting addressed in an upcoming version?

Reversion to 1.12.2 did cause the errors to go away as you said. However I'd still like to see this to get ironed out. I'm still a year or 2 out from 4k and will be using this to catalog my 1080p disks during that time.

Just downloaded and installed 1.12.3. Here is what I'm seeing. Hash check failed for file 00800.m2ts at offset xxxxxxx, file is corrupt. Hash check failed for file 00800.m2ts at offset xxxxxxx, file is corrupt. Hash check failed for file 00800.m2ts at offset xxxxxxx, file is corrupt. Hash check fail...

Update: I apologize. Neither of these are UHD disks. I found this thread through a link and didn't check the forum header. It's still a bug, but I'll repost it in the proper forum. I get a milder form of this error: Hash check failed for file 00800.m2ts at offset xxxxxxx, file is corrupt. Hash check...

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 se...

I found a very simple solution to this on my system. I ran MMKV in single drive access and ran it as administrator. Both of these solved it and i am now able to do a full back up of the Blu-ray 2d I'm still getting the same failure either with full backup or a rip. Can you tell me if you have any o...

I found a very simple solution to this on my system. I ran MMKV in single drive access and ran it as administrator. Both of these solved it and i am now able to do a full back up of the Blu-ray 2d I'm not in front of my PC just now, but in case I have trouble later, can you point me to where I can ...

I figured I'd start a new thread about this as both myself and another user have been able to reproduce the issue consistently. The short version is that for the international 3d/2d blu ray steelbook release of Thor Ragnarok, the 3D disk rips without issue, but the 2D disk fails repeatedly at the sa...

I convert the 3D MKV file to SBS (side by side), if you go this route you can use any standard playback software if your projector or TV has SBS - most do. Does it matter if it's left-right or right-left encoding? This is for an Epson 3700 projector. The manual says: Frame Packing Side by Side Top ...

I tried to rip the 2D version twice and it failed right at the end. I thoroughly cleaned the disk with Leader lens cleaner also after the first fail. I was directed to the MakeMKV Disk Read Error page in the log window. I'm sure glad the 3D version was fine though since that's the version I really ...

I have an international steelebook that came with a 3D and normal BR disk included. It has this cover art. The 3D version ripped fine, but I'm having trouble with the 2D version. Keeps erroring out. Do you happen to have the same version? Are you able to rip the 2D disk properly? I have the exact s...

MakeMKV support indicates this is a read error upstream from the program. They pointed me to this page: /errors/read/ "The simple workaround is to copy all files from the disc to the hard drive manually, without MakeMKV running. If you succeed in this, there is a fast and simple way to convert ...

I have an international steelebook that came with a 3D and normal BR disk included. It has this cover art. The 3D version ripped fine, but I'm having trouble with the 2D version. Keeps erroring out. Do you happen to have the same version? Are you able to rip the 2D disk properly?

I can't speak for all cases, but in the couple I spot-checked, the 2D stream on a 3D disk when ripped without the MVC stream was identical in size (down to the byte) of the stream from the 2D disk. Also 3D disks often lack director commentaries and other bonus audio and subtitle tracks. In most case...

Maybe it was a one-off because I just did Appendices 9/10 from the second Hobbit set. They didn't require any post-processing. Maybe it was a mastering issue with the first set that they worked out the kinks on before the second.