www.makemkv.com

Hi, flojos hint did the trick. Thank you! Since I had always used tar with the z option to deal with .tar.gz files it didn't come to my mind that I need to use gunzip separately. Especially when even Krusader would not like to open the .gz part. Any idea what's wrong with these files? It's a old Fi...

> And you CAN have multiple versions of MakeMKV installed in different directories. How do you install it to different directories, doesn't it automatically go to /usr/bin? How do you change that? The linux way, download source and compile using ./configure --prefix=/usr/local/makemkv177 or whateve...

You're probably hitting the scanning bug and you're on the right track downgrading to 1.17.7 is the last working version. You'll need to post specifically with a error log of what's going on during your attempt to downgrade before anybody can offer assistance. I don't know if there's a prebuilt pack...

You may be hitting a bug with some drives where it stalls while scanning, downgrading to versions <=1.17.7 may help.

Many topics on the Linux section about this bug.

I don't have any insight but I can only assume that each drive has a key to decrypt disks and maybe these keys are useful for makemkv but that's just me guessing.

If this is the Linux version it could be the endless scanning bug on versions > 1.17.7, see that subforum lots of threads about it. It says Windows 11 and "OS device name: E:" I was replying to this poster who had the same issue but on Linux Mint. I faced the exact same problem under Linu...

If this is the Linux version it could be the endless scanning bug on versions > 1.17.7, see that subforum lots of threads about it.

Sounds like the endless scanning bug on versions > 1.17.7 on Linux, you need to downgrade to that version.

The hashes seem different depending on how it's downloaded, which is weird. On Firefox I get the same bad hash as you do but on Chromium, wget I get the right hashes. 42be3c1aa58025c1e7ca7eee663bb293287e43362e48fcf20adf0846e23a4818 makemkv-bin-1.18.1.tar.gz.firefox b16576651eadec3585e817843a2a1a0ebc...

Just wanted to thank the OP and old and new posters alike for all the information, successfully flashed a Buffalo BRXL-PUS6U3B with HL-DT-ST-BD-RE_BU40N-1.03-NM00000-211810241934.bin to enable LibreDrive functionality. Posting it here for the future Google travelers looking for current information. ...

that's weird edit > I tried here https://forum.makemkv.com/forum/viewtopic.php?t=224 but after I installed, accessing the drives was not possible. Mr. Google pointed me to another site called something like "MakeMKV Unofficial PPD or PDD", when installed accessed the drives first time. Bu...

Here's what I see at the moment. If there's more detailed info that can help, happy to grab that as well. https://i.ibb.co/zsVVwYz/image.png Just wanted to add another vote of confidence for the Buffalo BRXL-PUS6U3B working with UHD after successful flash. Flashing with Marty's Flasher and using HL...

.. Thanks again for the tip, successfully flashed the drive now 1.18.1 scans and rips fine on Linux. Drive Information OS device name: /dev/sr0 Current profile: BD-ROM Manufacturer: BUFFALO Product: Optical Drive Revision: 1.03 Firmware date: 2118-10-24 19:34 Bus encryption flags: 17 Highest AACS v...

For whatever the reason, 1.18.1 seems to prefer libredrives over non-libre drives. I believe your drive and firmware are the same as the poster in this link. https://forum.makemkv.com/forum/viewtopic.php?p=178868#p178868 Your drive platform (MT1959) is capable of supporting Libredrive with the corr...

So after going through the forum trying to find a solution there are more than half a dozen topics that relate to this issue (couple on reddit too)... perhaps it would be helpful to sticky a topic where people could report problematic and working drives for > 1.17.7 on Linux? These are just the topi...