www.makemkv.com

Billycar11 wrote: ↑

Fri Mar 15, 2024 10:10 am

sounds like the drive is rebooting give it more power

Knowing what the SCSI error messages are might help. I have ripped a UHD disk using a Verbatim 43888 using only "USB bus power", and so I won't assume that these drives are inherently power-hungry.

Saved AACS dump file as /home... My guess is that you have a "new" release of this particular movie that no-one has tried to rip before. You might need to email that dump file to svq@makemkv.com and wait for it to be processed... Curious though - you have a VID-related problem with a UHD ...

Please DO NOT upgrade this drive's firmware!

You might need to cross-flash this drive, but please obtain expert help from someone on this forum before doing any such thing.

FYI here is the diff between the two discatt.dat files generated for the same UHD disk: $ diff -u one.dat two.dat --- one.dat 2024-03-14 00:22:24.646444299 +0000 +++ two.dat 2024-03-14 00:23:40.718586569 +0000 @@ -4,8 +4,8 @@ 00000030: 2e6d 616b 656d 6b76 2e63 6f6d 2f6c 6962 .makemkv.com/lib 0000004...

The files are used for MakeMKV to track information it needs for processing the disk. AFAIK their stated aim is to ensure that MakeMKV can handle a "back-up" as much like the original disk as it possibly can. As such, I would therefore expect the contents of these files to be consistent a...

I have created decrypted back-ups of my UHD disks, each of which has a MAKEMKV/discattd.dat file. And I have discovered that each of this files contains something which looks like a VID: 04 00 00 80 00 00 00 10 [next 16 bytes, could be a VID] Now if these next 16 bytes are a VID then I would expect ...

Question is if i didn't install the -bin tarball is this here the problem ? MakeMKV has two tarballs: - makemkv-oss-1.17.6.tar.gz - makemkv-bin-1.17.6.tar.gz You need to install both of these, because the -oss tarball only creates front-ends and library APIs to execute the contents of the -bin tarb...

Try adding to your ffmpeg configuration parameters when you recompile it. I strongly suspect you have not built the shared ffmpeg libraries that MakeMKV needs.

The build scripts use pkg-config to locate libraries to compile against, and I suspect it has found the wrong installation of ffmpeg. There is an environment variable called PKG_CONFIG_PATH which determines which directories pkg-config searches, and the order to search them in. It sounds like you ne...

I have managed to compile MakeMKV 1.17.6 on Fedora 39, which uses ffmpeg 6.0: ffmpeg-6.0.1-3.fc39.x86_64 ffmpeg-devel-6.0.1-3.fc39.x86_64 You appear to have a "linker" error. The av_channel_layout_from_mask function should exist in libavutil: $ nm -D /usr/lib64/libavutil.so.58.2.100 | grep...

Manufacturer: PIONEER Product: BD-RW BDR-XD08U Revision: 1.02 Serial number: Firmware date: 2022-12-27 The Pioneer firmware needs to pre-date December 2022 for the drive to be LibreDrive-compatible. In effect, that means firmware revision 1.01 whereas your drive has revision 1.02. On the bright sid...

I find the reports of unreliability completely unfounded based on my experience. Consider: 6 people are playing Russian Roulette, and the first 5 people to play tell the 6th person that there's obviously nothing to worry about... :? I also own a Verbatim 43888, and it hasn't failed yet either. But ...

What could be the possible reasons for MakeMKV, a software used for ripping and backing up DVDs and Blu-ray discs, failing to recognize the disk drive on a PC despite the PC itself successfully detecting the drive? On Linux, MakeMKV needs read/write access to each drive's /dev/sgN and /dev/srM devi...

Billycar11 wrote: ↑

Tue Feb 20, 2024 3:25 am

no the pioneers no longer work out of the box unless you buy them from a flasher

FYI, the word "flasher" can also be used to mean something else entirely! (I hope! )

https://dictionary.cambridge.org/dictio ... sh/flasher

SamuriHL wrote: ↑

Tue Feb 20, 2024 1:05 am

EVERY UHD contains bus encryption so that's pointless.

And some non-UHD discs also contain bus encryption. The point is that KEYDB.cfg was created before bus encryption (and UHD!) even existed and so obviously its format doesn't support it.