[SOLVED] MakeMKV v1.17.8 - "This application version is too old. Please download the latest..."

[dtech]

That worked. I'm done with this but good luck getting the proxy to work, that could be handy for some.

The real situation is that it only doesn't work with certain drives, while other ODDs work perfectly. It doesn't work with my ASUS BW-16D1HT (3.10-MK) drive, but others have no problem with it, and even in this 64+32 bit combination they have no problem with their UHD drive.

What exact optical drive model do you have and what firmware is on it?

[flojo]

What exact optical drive model do you have and what firmware is on it?

Asus BW-16D1HT 3.10 (2 models, same as yours)
Pioneer BDR-XD07S (slim model)
LG BP50NB40 (NB50) (slim model)
Pioneer BDR-212V (2 models)
LG WH14NS40 (although this is a really bad drive, I should trash it)

The exact firmwares I'm not sure, I got all firmware from Coopervid and they work.

On a RPi 3, they worked as expected under Debian/Raspian, but none worked as expected in CoreELEC. To be clear, they're all semi-functional in CoreELEC's Kodi, as in Kodi can detect the disc as a "Blu-Ray" and even browse the disc's FS, but Kodi cannot play anything from the disc, not in player mode or by accessing the .m2ts directly.

In my opinion this isn't solely a MakeMKV problem or possibly at all, but this is definitely a CoreELEC distro problem.

Something seems to be blocking, but I'm not too sure if non-blocking would help :-/. I was going to install 1.47 armhf sg3_utils build here https://sg.danny.cz/sg/sg3_utils.html, but I gave up trying to figure that out.

Why didn't CoreELEC use Debian and dpkg or even Alpine and APK? Once you've chosen to use Systemd, who are you kidding with the labeling of embedded "JeOS". I scoured their forum trying to rationalize the usage of 64/32, but the only legitimate reason I saw for not using pure 64-bit was for Widevine support, although I'm not sure if that is still a valid reason.

[dtech]

Thanks for the drive list, it's a very nice selection.

I don't usually use CoreELEC, I just did it for testing.

At first, the usage of the 64/32-bit hybrid system could really be traced back to Widewine CDM, but this is no longer valid, because 64-bit has been available for some time. I suspect that it may be more of a kernel driver incompatibility in the BSP 4.9 kernel.
I had a similar built-in tuner driver problem with the 3.14 kernel under LE-AML, but it might be something else in the background under CE, I don't know...

However, makemvcon on-the-fly decrypt works flawlessly under native 64/64-bit on the same box (X96, SoC: S905X), and the Meson8* devices (S805/S8X2) are also flawless under 32/32-bit, there are no bus errors. This does not prove that there is a system problem, nor a SCSI kernel driver error.

I tried to draw some conclusions from this, which appears at the same time as the bus error, but I didn't see this in the kernel log under CE, but it appears under LE-AML:

Code: Select all

Unhandled fault: alignment fault (0x92000021) at 0x00000000e3b08b11

This unaligned memory access error is an unknown area for me, and my knowledge is not enough to understand it, but something like this might be the case: https://github.com/glenvt18/libdvbcsa/issues/1

I found a pretty good description about this error:
https://blog.quarkslab.com/unaligned-ac ... perly.html

However, because the makemkvcon code is closed source (excluding the OSS part), only the developer(s) can verify the truth of this statement.

[mayorun]

I've upgraded osmc 2024.10-1 to debian bookworm (just like any other debian bullseye release). Everything still seems to work fine. Then I've compiled makemkv 1.17.9 OSS with:

./configure --disable-gui --disable-qt5
make -j4
sudo make install

And after the "make install" of makemkv-bin, I manually installed the makemkvcon armhf version with:
sudo install -t /usr/bin bin/armhf/makemkvcon

Then - you may have to rename or move existing files first:
sudo ln -s /usr/lib/libmmbd.so.0 /usr/lib/arm-linux-gnueabihf/libbdplus.so.0
sudo ln -s /usr/lib/libmmbd.so.0 /usr/lib/arm-linux-gnueabihf/libaacs.so.0

Registering makemkvcon with the current beta-key always failed with "invalid key".
I thought it's still worth a try. I had to mount /dev/sr0 manually (to /mnt), osmc found the disc and played the main movie!

I've also enabled 64 bit kernel by adding "arm_64bit=1" on the bottom of /boot/config.txt - I'm not sure if this was important.

[dtech]

On the one hand, I don't know how you were able to update, because OSMC 2024.10 is basically based on bullseye.
Furthermore, glibc v2.31 is integrated under Debian 11 (Bullseye), so makemkvcon versions above v1.17.7 do not work.
As far as I know, OSMC strongly does not recommend updating with APT, especially a dist-upgrage.

And on the other hand, based on your description, you are using a Raspberry Pi and not a Vero 4+ or V.

Unfortunately, your description doesn't contain any usable information. What drive did you try and what disc?
Have you tried a factory-pressed AACSv2 DRM-protected UHD disc with a UHD-friendly drive that has a LibreDrive-compatible firmware?

The fact that the beta key doesn't work raises quite a few questions. From there, makemkv decrypt doesn't work either.