More > JRiver Media Center 21 for Linux
Quick start guide for installing JRiver Mediacenter 21 ARM for Raspberry Pi
Mark_NL:
--- Quote from: Dewd on January 01, 2016, 03:39:53 pm ---I'm a relative Linux Noob, but am finding my way around. Have access to an expert as well - lol
So, I have a Raspberry Pi 2B
It came with the preloaded Noobs card (Raspbian Wheezy)
I have followed the instructions above, but when I try launch MC in the GUI, I just get a white panel / window that overlays the GUI. JRMC21 shows up on the Panel at the top of the screen and I can close the white window by closing MC from the panel at the top of the Linux GUI . I see the CPU spiking as if it were starting an app, but that's all.
Any idea what I might have done wrong?
--- End quote ---
Are you sure you did this part of Mr. Willems's Quick start guide?
...........Now enter the following into the terminal.
--- Code: ---cd /boot
sudo nano config.txt
--- End code ---
This will show you the file config.txt in the text editor nano. You'll see a lot of information in the config file already, scroll down to the bottom of the file using the direction keys on your keyboard and enter the following two lines exactly as shown:
--- Code: ---framebuffer_depth=32
framebuffer_ignore_alpha=1
--- End code ---
Then save the file by pressing Ctrl+O, then enter. Then press Ctrl+X to exit, and you should be back at the terminal. Now close the terminal and reboot the pi.
tom539:
Hello,
thanks a lot for this tutorial - works great :)
But I have a problem to configure WebGizmo-layout: after a change (e.g. delete a standard-view like "Composer") and [OK], the change is lost and standard-view is still active.
Thanks for any help.
Dewd:
Yes, I was sure I had done that, but I still went and checked the config.txt file. The two lines were there right at the end, as expected. So I commented them out and saved and rebooted. Same problem. I went back in and took the comments out, saved and rebooted and it worked fine. Weird, but at least it's working now.
--- Quote from: Mark_NL on January 02, 2016, 04:04:52 am ---
Are you sure you did this part of Mr. Willems's Quick start guide?
...........Now enter the following into the terminal.
--- Code: ---cd /boot
sudo nano config.txt
--- End code ---
This will show you the file config.txt in the text editor nano. You'll see a lot of information in the config file already, scroll down to the bottom of the file using the direction keys on your keyboard and enter the following two lines exactly as shown:
--- Code: ---framebuffer_depth=32
framebuffer_ignore_alpha=1
--- End code ---
Then save the file by pressing Ctrl+O, then enter. Then press Ctrl+X to exit, and you should be back at the terminal. Now close the terminal and reboot the pi.
--- End quote ---
mwillems:
--- Quote from: tom539 on January 02, 2016, 10:01:10 am ---Hello,
thanks a lot for this tutorial - works great :)
But I have a problem to configure WebGizmo-layout: after a change (e.g. delete a standard-view like "Composer") and [OK], the change is lost and standard-view is still active.
Thanks for any help.
--- End quote ---
You need to restart between changes for them to take effect in WebGizmo if I recall correctly.
mwillems:
--- Quote from: jimwc on December 30, 2015, 06:10:11 pm ---Update: running MC21 with sudo only fixes the "no close" problem for a little while. Maybe this has something to do with the VNC session going to sleep at some point after rebooting the Pi?
I recently executed sudo apt-get update, and noticed that the first line on the console says
"Hit http://dist.jriver.com wheezy InRelease"
Could this be my problem since I am running Raspian Jessie? Do I need to reinstall MC21 for jessie by somehow changing something in the following?
wget -q "http://dist.jriver.com/mediacenter@jriver.com.gpg.key" -O- | sudo apt-key add -
sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter21native.list -O /etc/apt/sources.list.d/mediacenter21.list
Again, many thanks in advance for tolerating all of my Linux noob questions.
-Jim
--- End quote ---
The release is fine. The hanging on close you're experiencing is likely just MC taking a while to shut down. In my experience it might take up to thirty seconds to close on the pi. Does it eventually close if you close the program and leave and come back?
Running MC as root is not advised.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version