Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[BryanC]

installJRMC

This program will install JRiver Media Center and associated services on most major Linux distros.

You can always find the latest version of installJRMC, changelog, and documentation in my repository.

tl;dr One-line MC install

Code: [Select]

curl https://git.bryanroessler.com/bryan/installJRMC/raw/master/installJRMC|bash
Instructions

Download and unzip installJRMC from the attachment below or grab the latest stable version directly:

Code: [Select]

curl -O https://git.bryanroessler.com/bryan/installJRMC/raw/master/installJRMC &&
chmod +x ./installJRMC &&
./installJRMC [--option [ARGUMENT]]
Running `installJRMC` without any options will install the latest version of JRiver Media Center from the official JRiver repository (Ubuntu/Debian) or my unofficial repository (Fedora/CentOS) using the system package manager (i.e. --install repo). If any other option is passed, then the install method (--install repo or --install local) must be specified, to make it possible to install services and containers independent of MC.

Options

Code: [Select]

$ installJRMC --help
--install, -i repo|local
    repo: Install MC from repository, future updates will be handled by the system package manager
    local: Build and install MC package from official source package
--build[=suse|fedora|centos]
    Build RPM from source DEB but do not install
    Optionally, specify a target distro for cross-building (ex. --build=suse, note the '=')
--compat
    Build/install MC without minimum dependency version requirements
--mcversion VERSION
    Build or install a specific MC version, ex. "32.0.6"
--arch ARCH
    Specify the MC architecture, ex. "amd64", "arm64", etc (default: host architecture)
--mcrepo REPO
    Specify the MC repository, ex. "bullseye", "bookworm", "noble", etc (default: latest official)
--outputdir PATH
    Generate rpmbuild output in this PATH (default: ./output)
--restorefile RESTOREFILE
    Restore file location for automatic license registration
--betapass PASSWORD
    Enter beta team password for access to beta builds
--service, -s SERVICE
    See SERVICES section below for the list of services to deploy
  --service-type user|system
      Starts services at boot (system) or user login (user) (default: per-service, see SERVICES)
--container, -c CONTAINER (TODO: Under construction)
    See CONTAINERS section below for a list of containers to deploy
--createrepo[=suse|fedora|centos]
    Build rpm, copy to webroot, and run createrepo.
    Optionally, specify a target distro for non-native repo (ex. --createrepo=fedora, note the '=')
  --createrepo-webroot PATH
      The webroot directory to install the repo (default: /var/www/jriver/)
  --createrepo-user USER
      The web server user if different from the current user
--yes, -y, --auto
    Always assumes yes for questions
--version, -v
    Print this script version and exit
--debug, -d
    Print debug output
--help, -h
    Print help dialog and exit
--uninstall, -u
    Uninstall JRiver MC, service files, and firewall rules (does not remove library or media files)

Services

Code: [Select]

jriver-mediaserver (user)
    Enable and start a mediaserver systemd service (requires an existing X server)
jriver-mediacenter (user)
    Enable and start a mediacenter systemd service (requires an existing X server)
jriver-x11vnc (user)
    Enable and start x11vnc for the local desktop (requires an existing X server, does NOT support Wayland)
  --vncpass and --display are also valid options (see below)
jriver-xvnc (system)
    Enable and start a new Xvnc session running JRiver Media Center
  --vncpass PASSWORD
    Set vnc password for x11vnc/Xvnc access. If no password is set, the script will either use existing password stored in ~/.vnc/jrmc_passwd or use no password
  --display DISPLAY
    Manually specify display to use for x11vnc/Xvnc (ex. ':1')
jriver-createrepo (system)
    Install hourly service to build latest MC RPM and run createrepo
    By default installs as root service to handle www permissions more gracefully

By default, MC services use a sane `--service-type` listed next to the service name in the Services description. User services can be manipulated as an unprivileged user, for example: systemctl --user stop jriver-mediacenter and begin at user login. System services are manipulable as root, for example: sudo systemctl stop jriver-servicename@username.service and begin at system boot. Note that it is possible to run all services of a particular user at boot using sudo loginctl enable-linger username.

Multiple services (but not --service-types) can be installed at one time using multiple --service blocks:

Code: [Select]

installJRMC --install repo --service jriver-x11vnc --service jriver-mediacenter
jriver-x11vnc versus jriver-xvnc

jriver-x11vnc shares your existing X display via VNC and can be combined with additional services to start Media Center or Media Server. Conversely, jriver-xvnc creates a new Xvnc display and starts a JRiver Media Center service in the foreground of the new VNC display.

Containers

Coming soon!

Firewall

`installJRMC` automatically creates port forwarding firewall rules for remote access to Media Network (52100-52200/tcp, 1900/udp DLNA) and Xvnc/x11vnc (if selected), using `firewall-cmd` or `ufw`.
Note: `ufw` is not installed by default on Debian but will be installed by `installJRMC`. To prevent SSH lock-out, Debian users that have not already enabled `ufw` will need to `sudo ufw enable` after running `installJRMC` and inspecting their configuration.

Examples

Code: [Select]

installJRMCInstall the latest version of MC from the best available repository.

Code: [Select]

installJRMC --install local --compatInstall a more widely-compatible version of the latest MC version.

Code: [Select]

installJRMC --install repo --service jriver-mediacenter --service-type userInstall MC from the repository and start/enable jriver-mediacenter.service as a user service.

Code: [Select]

installJRMC --install local --compat --restorefile /path/to/license.mjr --mcversion 32.0.6Build and install an MC 32.0.6 comptability RPM locally and activate it using the /path/to/license.mjr

Code: [Select]

installJRMC --createrepo --createrepo-webroot /srv/jriver/repo --createrepo-user www-userBuild an RPM locally for the current distro, move it to the webroot, and run createrepo as www-user.

Code: [Select]

installJRMC --service jriver-createrepo --createrepo-webroot /srv/jriver/repo --createrepo-user www-userInstall the jriver-createrepo timer and service to build the RPM, move it to the webroot, and run createrepo as www-user hourly.

Code: [Select]

installJRMC --install repo --service jriver-x11vnc --service jriver-mediacenter --vncpass "letmein"Install services to share the existing local desktop via VNC and automatically run MC on startup.

Code: [Select]

installJRMC --install repo --service jriver-xvnc --display ":2"Install an Xvnc server on display ':2' that starts MC.

Code: [Select]

installJRMC --uninstallUninstall MC, services, and firewall rules. This will not remove your media, media library/database, or library backup folder.

Additional Info

Did you find installJRMC useful? Buy me a coffee!

[BryanC]

installJRMC will still migrate older libraries by default and did not seem to conflict with the new feature (at least on Fedora), once I have tested the built-in mechanism further I will remove it.

[Awesome Donkey]

For the fun of it, I tried installJRMC in OpenSUSE Tumbleweed... and it mostly works. The big issue is it can't resolve and install a couple dependencies which prevents installation (even when using --compat), which for whatever reason aren't present in Tumbleweed but do appear to be in Leap. Those dependencies being freetype, freetype-devel and freetype-tools.

It can be a bit of a pain hunting them down and manually installing them to workaround the issue, but once you do the MC install should be pretty smooth and it runs rather well.

Great work, as always!

[bob]

For the fun of it, I tried installJRMC in OpenSUSE Tumbleweed... and it mostly works. The big issue is it can't resolve and install a couple dependencies which prevents installation (even when using --compat), which for whatever reason aren't present in Tumbleweed but do appear to be in Leap. Those dependencies being freetype, freetype-devel and freetype-tools.

It can be a bit of a pain hunting them down and manually installing them to workaround the issue, but once you do the MC install should be pretty smooth and it runs rather well.

Great work, as always!

I wonder why it would need a -devel package (freetype-devel)?

[Awesome Donkey]

Dependencies of freetype, had to install the two to get freetype to install. At least that seems to be how it is in OpenSUSE, I'm just a little bit baffled why freetype is missing and not installable from the repos in OpenSUSE Tumbleweed but is available and installable in OpenSUSE Leap. Oh well, I'll re-test that again at some point when I do another clean install.

[BryanC]

Dependencies of freetype, had to install the two to get freetype to install. At least that seems to be how it is in OpenSUSE, I'm just a little bit baffled why freetype is missing and not installable from the repos in OpenSUSE Tumbleweed but is available and installable in OpenSUSE Leap. Oh well, I'll re-test that again at some point when I do another clean install.

If you can post some links to them I will add a manual workaround.

[shortie]

How should I upgrade from MC 31 to MC 32? Should I use the -u option first or ...  ? In the past I've just done the install and manually edited the services definitions to start the new version as opposed to the old one but I have a feeling that's not really the right way to go about it.

[BryanC]

How should I upgrade from MC 31 to MC 32? Should I use the -u option first or ...  ? In the past I've just done the install and manually edited the services definitions to start the new version as opposed to the old one but I have a feeling that's not really the right way to go about it.

`./installJRMC --install repo --service jriver-mediacenter` (for example) will install the latest version of MC32 (mediacenter32 package), migrate the library, and replace the existing service file with one pointing at mediacenter32. After you've confirmed everything is good to go, uninstall mediacenter31 using your package manager and optionally delete "~/.jriver/Media Center 31".

[shortie]

`./installJRMC --install repo --service jriver-mediacenter` (for example) will install the latest version of MC32 (mediacenter32 package), migrate the library, and replace the existing service file with one pointing at mediacenter32. After you've confirmed everything is good to go, uninstall mediacenter31 using your package manager and optionally delete "~/.jriver/Media Center 31".

Maybe it's the way I did things but I had to go in and edit /lib/systemd/system/jriver-mediacenter@.service to change it from mediacenter31 to mediacenter32. I just ran a vanila ./intallJRMC to install/upgrade. I'm on Ubuntu 22.04.

[BryanC]

Maybe it's the way I did things but I had to go in and edit /lib/systemd/system/jriver-mediacenter@.service to change it from mediacenter31 to mediacenter32. I just ran a vanila ./intallJRMC to install/upgrade. I'm on Ubuntu 22.04.

You'll need to specify the `--service jriver-*` option or else the service files will not be (over)written. You can trigger it manually without reinstalling MC by omitting the --install option, for example: `./installJRMC --service jriver-mediacenter`

[Awesome Donkey]

If you can post some links to them I will add a manual workaround.

I just did a clean OpenSUSE Tumbleweed install and ran the script and as expected encountered the issue while trying to install the built .rpm file...

Code: [Select]

Problem: nothing provides 'freetype' needed by the to be installed mediacenter32-32.0.9-1.x86_64
 Solution 1: do not install mediacenter32-32.0.9-1.x86_64
 Solution 2: break mediacenter32-32.0.9-1.x86_64 by ignoring some of its dependencies
However, after the script automatically cancels and quits you can force install the .rpm manually ignoring the freetype dependency and MC32 appears to run just fine, but that has me thinking... maybe this dependency can be removed or changed? Because freetype2-devel, libfreetype6 and libXft2 are installed with the clean OpenSUSE Tumbleweed install. Maybe one of these would suffice (my guess would be libfreetype6 since it provides freetype2)?

Alternatively, yes, you can manually install freetype, freetype-devel and freetype-tools from the OpenSUSE Leap repos. This can be a bit of a pain though, so maybe just changing/removing the dependency is the better option?

EDIT: I installed rpmrebuild and modified the .rpm built by the script. I changed the freetype dependency to libfreetype6 (as it provides freetype2), but I also had to change the libwebkit2gtk-4.0-37 dependency to libwebkit2gtk-4_0-37 otherwise it would give an error about it being missing too. After that the .rpm installs fine, so two dependencies need to be changed for the .rpm build for OpenSUSE Tumbleweed.

[BryanC]

I didn't test but did look up package names in the SUSE package search, could you try with dev installJRMC to see if it's working now? I'm still a little confused re: leap/tumbleweed differences, don't want to fix one just to break the other.

https://git.bryanroessler.com/bryan/installJRMC/raw/dev/installJRMC

[Awesome Donkey]

Yep, it works great now.

Looking at the repos for Leap and Tumbleweed, it appears both uses libfreetype6 and libwebkit2gtk-4_0-37. The only weird thing is both Leap repos have freetype still, must be a legacy thing.

You can search in the repos for all three here and compare:

Tumbleweed:
https://download.opensuse.org/tumbleweed/repo/oss/x86_64/

Leap 15.4:
https://download.opensuse.org/distribution/leap/15.4/repo/oss/x86_64/

Leap 15.5:
https://download.opensuse.org/distribution/leap/15.5/repo/oss/x86_64/

[shortie]

You'll need to specify the `--service jriver-*` option or else the service files will not be (over)written. You can trigger it manually without reinstalling MC by omitting the --install option, for example: `./installJRMC --service jriver-mediacenter`

Maybe it's just me but could you add this to your instructions? It wasn't, and still isn't, the obvious way to make this all happen.

[sergioz]

Hi! I'm sorry but I need some help: I have Linux Mint 21.3 and MC 31 already installed.

I tried downloading directly InstallJRMC (version 1.0 and 1.01) but all I can get is:

Package update failed!
Error: JRiver Media Center installation from remote repository failed

and the same result if I do 'copy and past' of the "curl..." command in a terminal.
It's the first time in all these years. Please.... some suggestion?

Thanks

Sergioz

[Awesome Donkey]

Try running it with the --debug flag and see what it says and post it here.

[sergioz]

Thank'You, here the result with curl ecc:

'curl -O https://git.bryanroessler.com/bryan/installJRMC/raw/master/installJRMC && chmod +x ./installJRMC && ./installJRMC --debug
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 60659    0 60659    0     0  61543      0 --:--:-- --:--:-- --:--:-- 61520
Debug: Running: main --debug
Debug: Running: init
Starting installJRMC
Debug: Detected host platform: linuxmint 21.3 amd64
Debug: Using host platform: ubuntu 21.3
Debug: Running: parseInput
Debug: Debugging on
Debug: installJRMC version: 1.0-dev
Debug: Running: setMCVersion
Determining latest MC version
Debug: Running: installPackage --silent buildah
Debug: buildah already installed, skipping installation
Debug: buildah rm debian-working-container
9c2790cb4b71c0628fbc32f1fbb9180115ac70873b2298396b70a93bc6ade27b
Using MC version 32.0.12 determined by containerized package manager
To override, use --mcversion
Debug: MVERSION: 32, MC_VERSION: 32.0.12, MC_PKG: mediacenter32, MC_RPM: /home/john/output/RPMS/x86_64/mediacenter32-32.0.12.x86_64.rpm
Adding universe repository
Debug: sudo add-apt-repository -y universe
[sudo] password di john:         
Installing JRiver Media Center from remote repository
Debug: Running: installMCFromRepo
Debug: sudo rm -rf /etc/apt/sources.list.d/mediacenter*.list
Debug: Running: installPackage wget
Debug: wget already installed, skipping installation
Debug: sudo apt-get update -y -q0
Ignorato:1 http://packages.linuxmint.com virginia InRelease                   
Trovato:2 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu jammy InRelease
Trovato:3 https://dl.google.com/linux/chrome/deb stable InRelease             
Trovato:4 http://archive.ubuntu.com/ubuntu jammy InRelease                     
Trovato:5 http://ppa.launchpad.net/flacon/ppa/ubuntu jammy InRelease           
Trovato:6 http://packages.linuxmint.com virginia Release                       
Trovato:7 http://security.ubuntu.com/ubuntu jammy-security InRelease           
Trovato:8 http://archive.ubuntu.com/ubuntu jammy-updates InRelease             
Trovato:9 http://archive.ubuntu.com/ubuntu jammy-backports InRelease           
Scaricamento di:11 https://ppa.launchpadcontent.net/savoury1/chromium/ubuntu jammy InRelease [18,1 kB]
Trovato:12 http://dist.jriver.com/latest/mediacenter bullseye InRelease
Errore:11 https://ppa.launchpadcontent.net/savoury1/chromium/ubuntu jammy InRelease
  Le seguenti firme non sono state verificate perché la chiave pubblica non è disponibile: NO_PUBKEY 374C7797FB006459
Lettura elenco dei pacchetti... Fatto
W: http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu/dists/jammy/InRelease: La chiave è archiviata nel portachiavi legacy trusted.gpg (/etc/apt/trusted.gpg), vedere la sezione DEPRECATION in apt-key( per i dettagli.
W: http://ppa.launchpad.net/flacon/ppa/ubuntu/dists/jammy/InRelease: La chiave è archiviata nel portachiavi legacy trusted.gpg (/etc/apt/trusted.gpg), vedere la sezione DEPRECATION in apt-key( per i dettagli.
W: Errore GPG: https://ppa.launchpadcontent.net/savoury1/chromium/ubuntu jammy InRelease: Le seguenti firme non sono state verificate perché la chiave pubblica non è disponibile: NO_PUBKEY 374C7797FB006459
E: Il repository "https://ppa.launchpadcontent.net/savoury1/chromium/ubuntu jammy InRelease" non è firmato.
N: L'aggiornamento da tale repository non può essere eseguito in modo sicuro ed è quindi disabilitato come impostazione predefinita.
N: Consultare la pagina man apt-secure( per la creazione di un repository e la configurazione utente.
Error: Package update failed!
Error: JRiver Media Center installation from remote repository failed'

[sergioz]

package not signed

[Awesome Donkey]

Hmmm, I wonder why it's trying to use a .rpm file on Linux Mint, which uses .deb files. Will have to load up my Mint VM and see what it says.

[sergioz]

Ok thank You

[Awesome Donkey]

Oh, I see why now and it isn't an issue with the script itself. It's because your Chromium PPA https://ppa.launchpadcontent.net/savoury1/chromium/ubuntu has no public key, which is causing APT to fail. You'll have to fix your PPAs/repositories before APT will continue as your system is in a broken state because of it (and you'll have to fix it regardless, as currently you won't be able to perform any system updates until it's fixed).

Personally, I'd delete the Chromium repository from your list of PPAs/repositories then run sudo apt-get update to check for anymore errors, then run the script if there isn't any. You'll probably have to manually add the PPA back using the instructions here: https://launchpad.net/~savoury1/+archive/ubuntu/chromium

[sergioz]

Thank for all your job!!

[sergioz]

all done and solved!! 

[drmimosa]

Bryan, I was updating a machine and your repository hung -- a quick google search shows your whole website is down. Hope everything is ok.

[BryanC]

Bryan, I was updating a machine and your repository hung -- a quick google search shows your whole website is down. Hope everything is ok.

Seems to be working for me, hopefully it was just a temporary hosting issue. I'm going to move to something faster soon.

[drmimosa]

Seems to be working for me, hopefully it was just a temporary hosting issue. I'm going to move to something faster soon.

Hello. I found the problem - it was on my end. I am using this DNS server, set at the router:

 https://www.opendns.com/setupguide/#familyshield

Seems that for whatever reason when this is active, I can't reach your repository or website.

Code: [Select]

nslookup git.bryanroessler.com
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; no servers could be reached

When I changed the DNS server to 8.8.8.8 on the local machine, no problem.

Code: [Select]

nslookup git.bryanroessler.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
git.bryanroessler.com canonical name = 1fu4.f.time4vps.cloud.
Name: 1fu4.f.time4vps.cloud
Address: 176.223.132.72


[bob]

It looks like we should be using /usr/share/metainfo now instead of /usr/share/appdata since that's deprecated. Just a heads-up I'll probably change that soon. I assume it will have to be dealt with for non-debian installs.

[erviv]

The installer didn't work for me.  I just installed a fresh copy of Bookworm on my rpi. MC appears to load correctly although I get a warning
arning: Install firewall-cmd or ufw to open firewall ports
Debug: Running: disableCoW

I also get an unreadable info message which pop up on my screen when I try to start JRiver..

Any suggestions.

I did use jrmc Install MC successfully on my other rpi running bullseye.

I see that the river.list file refers to ….bullseye main. I thought I read that this worked on Bookworm, was I mistaken?

[erviv]

The installer didn't work for me.  I just installed a fresh copy of Bookworm on my rpi. MC appears to load correctly although I get a warning
arning: Install firewall-cmd or ufw to open firewall ports
Debug: Running: disableCoW

I also get an unreadable info message which pop up on my screen when I try to start JRiver..

Any suggestions.

I did use jrmc Install MC successfully on my other rpi running bullseye.

I see that the jriver.list file refers to ….bullseye main. I thought I read that this worked on Bookworm, was I mistaken? I changed bullseye to bookworm in jriver.list but that didn’t work either.

[BryanC]

There is no bookworm version of MC but my guess is that the bullseye version should work on bookworm. If you add the --debug option I can see where it is failing, the other warnings shouldn't prevent it from installing.

[erviv]

Thanks BryanC.
I returned the jriver.list file back to bullseye, and run the install.  Results below.

pi-2@raspberrypi:~ $ ./installJRMC --debug
Debug: Running: main --debug
Debug: Running: init
Starting installJRMC
Debug: Detected host platform: debian 12 arm64
Debug: Using host platform: debian 12
Debug: Running: parseInput
Debug: Debugging on
Debug: installJRMC version: 1.0-dev
Debug: Running: setMCVersion
Determining latest MC version
Debug: Running: installPackage --silent buildah
Debug: buildah already installed, skipping installation
Debug: buildah rm debian-working-container
b25a5d27c815be8db74417e397b681614de0e9f830f31695f58458155a4cb433
Using MC version 32.0.20-arm64 determined by containerized package manager
To override, use --mcversion
Debug: MVERSION: 32, MC_VERSION: 32.0.20-arm64, MC_PKG: mediacenter32, MC_RPM: /home/pi-2/output/RPMS/x86_64/mediacenter32-32.0.20-arm64.x86_64.rpm
Installing JRiver Media Center from remote repository
Debug: Running: installMCFromRepo
Debug: sudo rm -rf /etc/apt/sources.list.d/mediacenter*.list
Debug: Running: installPackage wget
Debug: wget already installed, skipping installation
Debug: sudo apt-get update -y -q0
Hit:1 http://deb.debian.org/debian bookworm InRelease
Get:2 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:4 http://dist.jriver.com/latest/mediacenter bullseye InRelease [3,614 B]
Hit:5 http://archive.raspberrypi.com/debian bookworm InRelease                 
Get:6 http://dist.jriver.com/latest/mediacenter bullseye/main amd64 Packages [853 B]
Get:7 http://dist.jriver.com/latest/mediacenter bullseye/main armhf Packages [860 B]
Get:8 http://dist.jriver.com/latest/mediacenter bullseye/main arm64 Packages [831 B]
Get:9 http://dist.jriver.com/latest/mediacenter bullseye/main i386 Packages [871 B]
Fetched 110 kB in 3s (38.2 kB/s)
Reading package lists... Done
Debug: Running: installMesa
Debug: Running: installPackage --no-install-check --allow-downgrades --no-gpg-check mediacenter32
Debug: sudo apt-get -f install -y -q0 --allow-downgrades mediacenter32
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
mediacenter32 is already the newest version (32.0.20-arm64).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
JRiver Media Center installed successfully from remote repository
Debug: Running: symlinkCerts
Debug: Running: migrateLibrary
Debug: Running: restoreLicense
Debug: Running: openFirewall jriver-mediacenter 52100-52200/tcp 1900/udp
Warning: Install firewall-cmd or ufw to open firewall ports
Debug: Running: disableCoW
pi-2@raspberrypi:~ $

MC32 appears as before in the drop down menu under Sounds  & Video, but does not open.

If you don't see the error, I could try Bobs post from Jan 19, 2024 Adding the MediaCentre repo manually. In his post for adding the repo file list he does create for bookworm a jriver.list file ending with "bookworm main"

[Awesome Donkey]

MC32 is successfully installing, so the issue isn't with the script itself. Open a terminal, type in mediacenter32 and post what it says here. I'm going to guess segmentation fault or something.

[erviv]

Hello Awesome Donkey.
I did as you suggested.  There are pages of error messages.

I have copied the last page of so below.  Let me know if you need mo
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/rating-3.png': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/rating-4.png': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/rating-5.png': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/rating.png': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_biography.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_comments.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_ltw1.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_lyrics_1v.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_lyrics_3h.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_mtw1.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_notes.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/MC Ultra III/ult3_tai.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire/background.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire/bgbar.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire/corner.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire/index.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire/main.css': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire/minmax.js': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/background.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/bgbar.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/corner.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/index.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/Lyrics.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/main.css': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/minmax.js': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Noire Viz/notes.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Ocean/background.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Ocean/index.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Ocean/main.css': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Ocean/minmax.js': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Simple/background.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Simple/bgbar.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Simple/corner.gif': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Simple/index.html': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Simple/main.css': No such file or directory
cp: cannot create regular file '/home/pi-2/.jriver/Media Center 32/Visualizations/Track Info/Simple/minmax.js': No such file or directory
pi-2@raspberrypi:~ $

[Awesome Donkey]

Looks like you don't have write permissions on the ~/.jriver directory. I'd enable hidden files in the file manager you're using, go into your home directory and either move the .jriver folder to another temporarily or straight up delete it and see if you can run MC32 then.

[erviv]

Yes,I checked permissions in the file properties and in .jriver while anyone can view or access content only the owner can change content. Owner and group are shown as  root. I tried changing permissions from the file manager but that didn’t work.
So I deleted the file from the terminal. MC now starts. The .jriver dir now has my user (pi-2) as the owner and group.

Thank you.

[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: [Select]

installJRMC --install local --mcrepo noble
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!

[bob]

I added noble support in installJRMC v1.0.2 for *buntu >= 24.04 as well as a new "--base" option to select your preferred debian base manually for fun or troubleshooting.

I tried running the noble MC build on Fedora 40 and it worked fine:

Code: [Select]

installJRMC --install local --base noble
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 a noble MC base. 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!

MC31 was the first with Bullseye as the base requirement. That's the current required base.
MC27 through MC30 have Buster as the base requirement
MC20 through MC26 have Jessie as the base requirement

There have been changes to packages required in between major versions but not to the base requirements.

[BryanC]

Great, 1.1.0 uses the right repos for older versions and a new alpine-based container for checking the latest MC version. This will save about 80MB of disk space and bandwidth on first install.

[fegelmej]

This is a fantastic thread for those who know what you all are talking about.  For us tinkerers it is a challenge. 

I've been running MC 26 on a Raspberry PI 3b fairly stable for years.  Things started getting wonky lately with glitches and 2 second pauses.  Worked through a lot of suggestions from this forum, but didn't improve the situation.  Thought an upgrade to a Pi 5 would settle these issues with its improved processing and RAM. Tried the easy route of slipping the SD card from the 3B to the 5, but no joy.  Won't even boot.  Seems like that should work, but maybe I'm missing something.  Is there a more straightforward approach than all that line code (forgive me) referenced above to move to a new machine?

[BryanC]

This is a fantastic thread for those who know what you all are talking about.  For us tinkerers it is a challenge. 

I've been running MC 26 on a Raspberry PI 3b fairly stable for years.  Things started getting wonky lately with glitches and 2 second pauses.  Worked through a lot of suggestions from this forum, but didn't improve the situation.  Thought an upgrade to a Pi 5 would settle these issues with its improved processing and RAM. Tried the easy route of slipping the SD card from the 3B to the 5, but no joy.  Won't even boot.  Seems like that should work, but maybe I'm missing something.  Is there a more straightforward approach than all that line code (forgive me) referenced above to move to a new machine?

One-line install:

Code: [Select]

curl https://git.bryanroessler.com/bryan/installJRMC/raw/master/installJRMC|bash
Edit: Added to OP

[fegelmej]

That sounds easy!  Thanks.  The 'curl" term is new to me.  Can you define that?

[JimH]

Google it.  It's part of the OS.

[Awesome Donkey]

A sudo apt install curl should install it if it's not already present on the system.

[fegelmej]

A sudo apt install curl should install it if it's not already present on the system.

This was the key to getting it installed.  Thanks to you and Bryan.

[Mastiff]

I installed 31 on the Pi 4 with updated Bookworm in my boat with the script, but I'm unable to uninstall it to upgrade to version 32. This is the command I used:

Code: [Select]

./installJRMC --uninstall --mcversion 31.0.87 --arch arm64
But I get an error message:

Code: [Select]

Error: JRiver Media Center package 'mediacenter31=31.0.87' is not present and was not uninstalled
I have double and triple checked that it's the version I have installed. I first tried without --arch arm64, but that didn't work. Then I tried with it. And it's still not working. Any ideas would be very welcome. 

[Awesome Donkey]

I'd do it manually from the terminal, sudo apt remove mediacenter31.