Ubuntu Desktop Install and Integration with VLC
Posted: Tue Aug 11, 2020 5:14 pm
I am running the latest Ubuntu Desktop distribution (Ubuntu 20.04.1 LTS). I have used the Snap package manager to install MakeMKV v1.15.2. All appears to work fine, but I noticed the supporting files are not being installed correctly for use with VLC and the like.
As it would appear the Integration tab only works with the Windows and Mac ports of MakeMKV (based on a thread discussing the introduction of libmmbd with MakeMKV v1.15.0), I believe manual intervention is required to achieve the same level of integration. This is no big deal as I'd been doing this prior to v1.15.0, so I'm familar with the process.
In the Direct Blu-ray playback with VLC thread, Mike provides instructions to create a symbolic link for libmmbd.so.0 in our local user library path (/usr/lib/). Assumedly, this location enables the functionality for all users on the system (rather than just installing into the ~/lib/ directory for your user only). However, I'm wondering if we're missing a couple of steps as I have VLC complaining that it cannot find libaacs for Blu-ray disc playback.
In prior versions of the application, we needed to create respective symlink aliases for libaacs or libbdplus (both pointing to libmmbd). With the introduction of the Integration tab, these symlinks were created silently in the background. For example, use of the Integration tab on macOS appears to create those aliases in the user's home folder (~/lib/) pointing back to libmmbd as follows:
As shown, macOS uses the '.dylib' extension on that OS. I'm not familiar with the naming scheme on Ubuntu, but I'm guessing the extension is '.so.0' per the example in the instructions provided by Mike. If that's the case, shouldn't we also have symlinks for libaacs and libbdplus in the /usr/lib/ directory?
To be direct: is it as simple as creating a symlink called /usr/lib/libaacs.so.0 and /usr/lib/libbdplus.so.0 to libmmbd.so.0 at the MakeMKV installation location? Do we think the installation from Snap has crated some other fundamental problem? Would a complete compile do something different to fix the issue?
A little background: I am new to Ubuntu, but familiar with Linux. I'm exploring the use of Ubuntu Desktop as my OS of choice for an encoding system. This rig is, effectively, an appliance to do nothing but rip discs and encode. I'm hoping to avoid Windows altogether, and I believe the core tools I use (FFMPEG, MakeMKV, Handbrake, etc.) all offer a Linux port.
As it would appear the Integration tab only works with the Windows and Mac ports of MakeMKV (based on a thread discussing the introduction of libmmbd with MakeMKV v1.15.0), I believe manual intervention is required to achieve the same level of integration. This is no big deal as I'd been doing this prior to v1.15.0, so I'm familar with the process.
In the Direct Blu-ray playback with VLC thread, Mike provides instructions to create a symbolic link for libmmbd.so.0 in our local user library path (/usr/lib/). Assumedly, this location enables the functionality for all users on the system (rather than just installing into the ~/lib/ directory for your user only). However, I'm wondering if we're missing a couple of steps as I have VLC complaining that it cannot find libaacs for Blu-ray disc playback.
In prior versions of the application, we needed to create respective symlink aliases for libaacs or libbdplus (both pointing to libmmbd). With the introduction of the Integration tab, these symlinks were created silently in the background. For example, use of the Integration tab on macOS appears to create those aliases in the user's home folder (~/lib/) pointing back to libmmbd as follows:
Code: Select all
~ % ll lib
total 0
drwxr-xr-x 4 username staff 128B Apr 29 15:45 ./
drwxr-xr-x+ 35 username staff 1.1K Aug 11 09:41 ../
lrwxr-xr-x 1 username staff 56B Apr 29 15:45 libaacs.dylib@ -> /Applications/MakeMKV.app/Contents/lib/libmmbd_new.dylib
lrwxr-xr-x 1 username staff 56B Apr 29 15:45 libbdplus.dylib@ -> /Applications/MakeMKV.app/Contents/lib/libmmbd_new.dylib
~ %
To be direct: is it as simple as creating a symlink called /usr/lib/libaacs.so.0 and /usr/lib/libbdplus.so.0 to libmmbd.so.0 at the MakeMKV installation location? Do we think the installation from Snap has crated some other fundamental problem? Would a complete compile do something different to fix the issue?
A little background: I am new to Ubuntu, but familiar with Linux. I'm exploring the use of Ubuntu Desktop as my OS of choice for an encoding system. This rig is, effectively, an appliance to do nothing but rip discs and encode. I'm hoping to avoid Windows altogether, and I believe the core tools I use (FFMPEG, MakeMKV, Handbrake, etc.) all offer a Linux port.