More > JRiver Media Center 32 for Linux
installJRMC - MC installer for Linux
Awesome Donkey:
Yep, that'll do it. This kind of thing can happen if running MC as sudo, for example. Glad to hear it's sorted now. :)
AllanM:
Hi. I have JRiver MC install on my Linux server (Ubuntu) and I want to use a Pi connected to a stereo in another room with JRiver. I figure I would just install JRiver on the Pi and use it as a renderer using the iPad app to control it. If I understand how this works, I just need to install JRiver MC on the Pi and I can play to it from my iPad (JRemote). I've done this and it works well.
I would also like for MC to start automatically on reboots.
My question is what's the best option to choose when installing MC for this purpose. I'm installing on a stock Pi OS (64 bit). I just installed with the default options, but is there a leaner or better install for my purposes?
Thanks.
Awesome Donkey:
The installJRMC script should work fine that way on a Raspberry Pi. Just set Media Center to start with the OS by going into MC's Options > Startup and make sure the run on startup option is set to Media Center.
Awesome Donkey:
Heads up, if anyone is updating to or using the newest Ubuntu 24.04 LTS that was just released, do know that MC32 is not currently installable due to the libwebkit2gtk-4.0-37 dependency not being able to be met. It doesn't work with the script with the --compat switch either, probably gotta wait for a MC32 update to workaround it.
BryanC:
I added noble support in installJRMC v1.0.2 for *buntu >= 24.04 as well as a new "--mcrepo" option to select your preferred MC repo manually for fun or troubleshooting.
I tried running the noble MC version on Fedora 40 and it worked fine:
--- Code: ---installJRMC --install local --mcrepo noble
--- End code ---
I'm not sure how many people are using my Fedora/CentOS repo, but I'm curious if anyone would be for/against switching the fedora rpms in my repo to the noble repo. I'm tempted since it seems to work OK on Fedora 40 and would be the latest and greatest, but I have not tested on F39 or lower or any of the CentOS derivatives.
Since there's now a fairly wide compatibility gap, I'm also thinking of a way to automatically select the appropriate MC base version for older distros and/or legacy MC releases and providing warnings/workarounds if there are issues.
Is there a list of which MC versions correspond to each Debian base version? IIRC sometimes it has switched mid-version so a tree of the repo would help!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version