Linux > JRiver Media Center 33 for Linux
Feature Parity with Windows for Home Theater
nathan_h:
Is there a similar thread about what is “missing” from the Mac version versus Windows?
mattkhan:
--- Quote from: nathan_h on August 18, 2024, 04:08:00 pm ---Is there a similar thread about what is “missing” from the Mac version versus Windows?
--- End quote ---
No. My impression is Mac and Linux are 2 peas in a pod in that regard.
Outlaw Audio:
--- Quote from: mwillems on August 18, 2024, 01:06:30 pm ---Are we talking about all feature gaps that might affect home theater use? There are a few others too, although some of them may be harder (or impossible) to fix:
5) Remote control and media keys
On Windows MCE remote controls and keyboard media keys work as expected in JRiver. Using them on Linux is challenging and requires significant work on the user's part.
There are two separate remote/media key issues. The first issue is that some media key presses don't seem to be implemented or work correctly. For example, using a standard MCE remote that worked perfectly on Windows, I have never managed to get the remote control number keys working in theater view on Linux the way they do on Windows. This is the case even using the exact same Linux environment that the devs use for testing (XFCE4 on Debian). Theater view on Linux just doesn't seem to respond to the number keys on the remote control at all even though they're sending the correct keypresses. To be clear, typing numbers on the keyboard works fine, but the remote control number keys do not work even though they're sending the same keycodes! Check out this thread for a recent(ish) example of another user struggling with remote control configuration seeing a similar issue: https://yabb.jriver.com/interact/index.php?topic=136975.0.
Second, there's a separate issue in that many common Linux desktop environments (DEs) (like Gnome, KDE, and I think Cinnamon too) consume some of the media keypresses and expect programs to use the MPRIS API to get them, but JRiver does not use MPRIS so using any remote or media key that the DEs "manage" requires a user workaround. So for many Linux users the most common remote or media keys (play/pause, stop, volume control) will fail out of the box, and require some fairly laborious workarounds to get them working (remapping keys using custom JRiver configuration, and then remapping the remote to hit those new keys).
To summarize, if you spin up JRiver on a default install of Debian (which uses the Gnome desktop environment as a default), Ubuntu (uses a modified Gnome as default), or Fedora (also Gnome by default), the majority of the remote control keys just won't work with no feedback as to why they're not working, and only some of those keys can be made to work via workarounds on the user side.
--- End quote ---
+++++++++++++++++1
This isue alone consumed a lot of time, sweat, blood and frustration and eventually led me to scrap Linux as my HTPC OS
mwillems:
--- Quote from: mattkhan on August 18, 2024, 04:26:00 pm ---No. My impression is Mac and Linux are 2 peas in a pod in that regard.
--- End quote ---
I think most of the same issues will apply, but I'm not sure how Mac handles remote controls/media keys or keeping screens on so 5) and 6) may or may not apply. I'm pretty sure all the rest of these issues apply equally to mac, but we'd need someone who is running MC on Mac to start a thread with any special or idiosyncratic Mac issues.
Hendrik:
We'll be looking over these for MC33.
Just one thing to point out, the Netflix topic will likely not be supported for DRM reasons, as was guessed already above. We can only offer this on Windows due to Microsofts WebView2 OS-level component that integrates with DRM, without that with just plain Chromium or such it would not work even on Windows. As far as I am aware, no such capability exists on Linux.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version