www.makemkv.com

If by "old DVD of local events" you really mean some DVD+/-R, it's probably not very surprising that disc rot has occured to it. In that case you might want to use ddrescue or alike to salvage what can possibly be from the disc.

The problem with the situation here is not so much that MakeMKV might be tampered. Rather it is that the we have no idea what the "extra layer" might contain, e.g. something that trigger / leverage a loophole or so in gzip or tar. (Of course it is not very likely for it to be malicious or ...

Btw BDRFlash (NOT Billy's auto flasher; although if it also uses nothing more than SPTI it should work as well) can be used on Linux through wine. It's just that instead of using the "dosdevice" / "drive letter" automatically created by wine (which points to /dev/sr*), you need t...

If it is really pan and scan (i.e. the "scan" is not always the center part of the widescreen version), then it's probably "implemented" with multi-angle. I have no actual experience with multi-angle DVD but I do know that they exist. It's just that I never thought that it would ...

First time I heard of such thing. Assuming the film is originally widescreen as usual, does the "fullscreen version/mode" look "squeezed" or cropped? (Assuming it's not the other way round -- that the "widescreen version/mode" is just a cropped fullscreen "fattened...

Drive platform: Pioneer RS8F01 Firmware version: ID83 Btw, is this one of those BDR-212UHBK from/for the Japan market instead of BDR-212UBK? EDIT: Ahh looks like my guess is correct: https://www.cdrinfo.pl/artykuly/artykulPioneerBDR212S12X12English/ P.S. Btw the firmware (updater that includes the ...

For the problem of 1.17.6/7+ not working with a non-LibreDrive (on Linux), the best workaround is probably the sdf_Stop setting. See e.g. https://forum.makemkv.com/forum/viewtopic.php?f=3&t=41692 Your drive happen to have firmware that is not (considered as) LibreDrive. Somehow only 1.01 and 1.0...

So it looks like the seller lied about updating the drives to firmware version 3.0. It doesn't matter. If you want UHD support you need MT1959 (although AFAIK there's no 3.xx firmware for MT1939 either). But more confusingly this says it is drive platform MT1959 What are you referring to by "t...

It's still somewhat strange and suspicious (even though I know this "double-gzip'ing" issue has happend before), especially when it didn't happen when the version was first released but after such a long time.

Makemkv currently doesn't have a host certificate that works with discs later than MKBv81...When combined with the public MKBv82 device keys, libredrives can still update the latest keydb database using software like SamuriHL's Keydb Tool . This way you won't need to submit a dump of your MKBv82 bl...

is it just mistake and admin forget to update No, unless the files were for reasons changed very recently without getting a version bump. The checksums in the txt are the same one in https://aur.archlinux.org/cgit/aur.git/commit/?h=makemkv&id=f50faf9f9bab163ce1342474ff4c1c6d7b178478. It has bee...

I suspect it's because when the author claims UHD support, they didn't consider bus encryption. (On the github repo, they list UHD support as "Native Support (without patched firmware)", which sounds to me that they didn't exactly "work on" anything regarding UHD support.) Maybe ...

No idea how the decryption of normal BDs works Technically it's somewhat a blackbox since that part of MakeMKV is not open-source. I think it essentially "emulates" a blu-ray player in the case of LibreDrive and calculates / derives the VUK as per how AACS "should work" -- excep...

Well as I already mentioned, obviously you need HOME properly set to /root (assuming that's where you have .MakeMKV/settings.conf put). As per https://nginx.org/en/docs/ngx_core_module.html#env and https://ketzacoatl.github.io/posts/2017-03-04-lua-and-openresty-part-4-using-envvars.html, apparently ...

No idea what's "openresty" but sounds like to me it's just that makemkvcon would be run as another user in that case and therefore reads a different .MakeMKV/setting from a different HOME (which is not /root).