INTERACT FORUM
More => Old Versions => JRiver Media Center 29 for Linux => Topic started by: Wheaten on March 18, 2022, 02:58:31 pm
-
removed
-
I am getting following error message. I removed the pub key from the error message to be cautious
$ sudo apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease
Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
Get:6 http://dist.jriver.com/latest/mediacenter buster InRelease [3,621 B]
Err:6 http://dist.jriver.com/latest/mediacenter buster InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY CXXBXXCXXXXXXDX
I am getting this error message after following steps
sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter29.list -O /etc/apt/sources.list.d/mediacenter29.list
sudo apt-get update
Any help is much appreciated. Thank you
I am installing for JRiver MC for 1st time with master license to be purchased yet
I also tried updating public key using
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys CXXBXXCXXXXXXDX
but received the message
gpg: keyserver receive failed: No data
-
Looks like you have missed the step to get the key:
$ sudo apt install gnupg2 wget ca-certificates
$ which apt-key
$ wget -nc http://dist.jriver.com/mediacenter@jriver.com.gpg.key
$ sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter29.list -O /etc/apt/sources.list.d/mediacenter29.list
-
Thank you for looking into my query.
I did run all the commands
wget -nc http://dist.jriver.com/mediacenter@jriver.com.gpg.key
File ‘mediacenter@jriver.com.gpg.key’ already there; not retrieving.
I am putting the whole script I ran with error messages I am getting
[ sudo apt install gnupg2 wget ca-certificates
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ca-certificates is already the newest version (20210119).
gnupg2 is already the newest version (2.2.27-2).
wget is already the newest version (1.21-1+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@audiopi:~ $ which apt-key
/usr/bin/apt-key
pi@audiopi:~ $ wget -nc http://dist.jriver.com/mediacenter@jriver.com.gpg.key
File ‘mediacenter@jriver.com.gpg.key’ already there; not retrieving.
pi@audiopi:~ $ sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter29.list -O /etc/apt/sources.list.d/mediacenter29.list
--2022-03-19 23:00:25-- http://dist.jriver.com/latest/mediacenter/mediacenter29.list
Resolving dist.jriver.com (dist.jriver.com)... 216.14.187.181
Connecting to dist.jriver.com (dist.jriver.com)|216.14.187.181|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 94
Saving to: ‘/etc/apt/sources.list.d/mediacenter29.list’
/etc/apt/sources.li 100%[===================>] 94 --.-KB/s in 0s
2022-03-19 23:00:26 (5.32 MB/s) - ‘/etc/apt/sources.list.d/mediacenter29.list’ saved [94/94]
pi@audiopi:~ $ sudo apt-get update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:3 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB]
Get:6 http://dist.jriver.com/latest/mediacenter buster InRelease [3,621 B]
Err:6 http://dist.jriver.com/latest/mediacenter buster InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C30B25C6077765D5
Reading package lists... Done
W: GPG error: http://dist.jriver.com/latest/mediacenter buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C30B25C6077765D5
E: The repository 'http://dist.jriver.com/latest/mediacenter buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
/code]
-
looks like there is something wrong at JRiver site ?
you can also try this, and ignore the complaints regarding ......deprecated......
$ wget -q "http://dist.jriver.com/mediacenter@jriver.com.gpg.key" -O- | sudo apt-key add
$ sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter29.list -O /etc/apt/sources.list.d/mediacenter29.list
$ sudo apt-get update
$ sudo apt-get install mediacenter29
-
Thank you Wheaten for your assistance. I took a different route. Since I am not technical and R Pi Os seems to need constant tinkering especially with playing YouTube . I bit the bullet and installed chromium OS.
Chromium OS allows Linux terminal so I installed the arm 64.deb file and JRiver played silky smooth. Better YouTube user experience is an added bonus.
If its not against the forum rule, I can keep updating how a newbie is navigating through chromium os with Linux on Raspi 4 from a music playing perspective.
-
I used ChromeOS as my main machine for a while: https://yabb.jriver.com/interact/index.php/topic,114616.msg792648.html#msg792648
Linux and MC for Linux ran well on it.
Probably best to start a new thread on it.
-
Late to the party here as usual and a novice at RPi and Debian, but a couple of questions on what seems to be a very straightforward set of instructions, thanks very much for putting this together.
I basically just want my RPi 4 to enable me to use a non-DLNA amp as a DLNA node (a JRiver zone). There will be no local media. So:
1. I'm confused by this:
"It preferable to add the same account to the external storage (like NAS) to access the media files.
Code: [Select]
username=<username to access the remote storage>
password=<password for remote storage>"
In a use case like mine, does this refer to the username/password for the JRiver media server?
2. If I'm using JRiver media server, do I need to follow the fstab instructions? If so, does this instruction apply: "Change vers=3.0 to the SMB version supported by your NAS"? I tried specifying the IP of my media server and all other options as in your example, but got an invalid parameter error. This is my entry:
\\xxx.xxx.x.xxx /mnt/music cifs credentials=/home/pi/.credentials,nofail,vers=3.0,x-systemd.automount,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
2. Do I need to buy a license for the Linux version or can I run it in trial mode the way I can Windows, to make sure this is a workable option? If there is a trial mode, do I need a JMR file?
3. I followed all the instructions (with the exceptions noted above) and I see a JRiver Media Center icon under "Sound & Video" as described in the instructions, but when I try to start JRiver I get two black "Information" dialog boxes with only an OK button. This may be related to omitting the steps above, but FYI in case that tells you anything.
Thanks again.
-
Late to the party here as usual and a novice at RPi and Debian, but a couple of questions on what seems to be a very straightforward set of instructions, thanks very much for putting this together.
I basically just want my RPi 4 to enable me to use a non-DLNA amp as a DLNA node (a JRiver zone). There will be no local media. So:
1. I'm confused by this:
"It preferable to add the same account to the external storage (like NAS) to access the media files.
Code: [Select]
username=<username to access the remote storage>
password=<password for remote storage>"
In a use case like mine, does this refer to the username/password for the JRiver media server?
2. If I'm using JRiver media server, do I need to follow the fstab instructions? If so, does this instruction apply: "Change vers=3.0 to the SMB version supported by your NAS"? I tried specifying the IP of my media server and all other options as in your example, but got an invalid parameter error. This is my entry:
\\xxx.xxx.x.xxx /mnt/music cifs credentials=/home/pi/.credentials,nofail,vers=3.0,x-systemd.automount,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
2. Do I need to buy a license for the Linux version or can I run it in trial mode the way I can Windows, to make sure this is a workable option? If there is a trial mode, do I need a JMR file?
3. I followed all the instructions (with the exceptions noted above) and I see a JRiver Media Center icon under "Sound & Video" as described in the instructions, but when I try to start JRiver I get two black "Information" dialog boxes with only an OK button. This may be related to omitting the steps above, but FYI in case that tells you anything.
Thanks again.
If you are just using MC on the Pi as a DLNA renderer, you don't need to connect to any samba shares or whatever.
Your MC that's playing material to the Pi MC DLNA Zone will push the tracks over the network.
The trial is the same as windows MC trial except that trial extensions don't work and if you install then remove and reinstall MC you'll lose the trial.
Make sure that Mac address randomization is NOT enabled on your Pi.
You should set the Media Network Advanced Audio and Video buffering disabling flags on if your Pi is running off of an SDCard.
Media Network advanced on the Pi you can disable the DLNA server and DLNA controller functions since you are only using the Pi as a renderer.
-
Will an rpi4 2gb be man enough to run as a TV client do you think?
I need to add another TV client to stream dvb-s2 and iptv channels from my server. It doesn't really need to do anything else other than be a JRiver client, but I'd like a decent viewing experience.
Rpis are obviously hard to come by right now, but I've been offered a couple of 2gb units and I don't think they'll cut the mustard.