INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Linux => Topic started by: mwillems on February 14, 2015, 07:30:55 am
-
This guide to installing JRiver's ARM build for the Raspberry Pi version 1 B+ and the Raspberry Pi version 2. There is now an official licensed ARM build.
Mediacenter works best on a Pi 2, but will work on the Pi 1 B+ (especially if you overclock), but the experience is limited. The steps to get MC running on the Pi are somewhat similar to getting it running on a normal linux system, with a few tweaks.
Setup
Hardware/OS setup:
Install Raspbian onto an SD card using the downloaded NOOBS image from the Raspberry Pi website. They have good instructions (http://www.raspberrypi.org/help/noobs-setup/), and Raspbian works on both the Pi 1 and the Pi 2 (although you need an updated installation medium for the Pi 2).
Configuring Hardware:
At first boot the Pi shows a config utility (called raspi-config). For easy use of mediacenter, I recommend a) setting the Pi to boot into a graphical desktop environment by default (ignore this if you're comfortable with the console), b) choosing the audio output you want by default (HDMI or the Pi's built in audio output*), and c) thinking about whether you want to choose one of the overclock* options in the advanced options. Once you've picked your settings, reboot.
Notes:
Audio: the Pi's HDMI output works great, but the built in stereo jack is not the highest quality output in the world. I wouldn't recommend using it for actual listening. If you have a USB DAC, just ignore that for now, this option is only about the behavior of the Pi's built in audio outputs.
Overclocking: Overclocking can potentially shorten the life of your Pi or cause instability. However, because the Pi now comes with built in thermal throttling, you can overclock using the raspberry pi utility as described above without voiding your warranty (http://www.raspberrypi.org/introducing-turbo-mode-up-to-50-more-performance-for-free/). Overclocking makes a huge difference in performance for the Pi 1; I did not find the Pi 1 usable at stock settings, YMMV. Overclocking is less important for the Pi 2, but it definitely improves performance. I have not personally encountered overclocking related instability with about four different Pis, but that doesn't mean you won't. If you decide to wait to overclock you can get back to the built in configuration utility any time by running
sudo raspi-configin a terminal window
Software Preparation:
After rebooting, you should be looking at the Pi's desktop. If your Pi isn't plugged into to an ethernet line, take a minute to configure your wi-fi adapter to get internet access. Once that's done, open a terminal by clicking on the icon that looks like a computer monitor. Enter the following into the terminal:
sudo apt-get update && sudo apt-get dist-upgrade
sudo apt-get install libx11-6 libc6 libasound2 libuuid1 libidn11 libxcb1 libxau6 libxdmcp6 zlib1g libxext6 libgtk2.0-0 libp11-kit0 libstdc++6 p11-kit libgl1-mesa-glx libcanberra-gtk-module xdg-utils xfonts-75dpi xfonts-100dpi lame vorbis-tools musepack-tools xfonts-unifont
After you enter the first line, you'll be prompted whether to install updates to packages; press "y" to confirm. It may take a little while for the packages to download and install. The same thing will happen after the second line, but it will also likely tell you that some of those packages are already installed; that's fine, this is insurance that you have everything you need. Now enter the following into the terminal
cd /boot
sudo nano config.txt
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:
framebuffer_depth=32
framebuffer_ignore_alpha=1
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.
Installing MC:
After the reboot, it's time to install MC:
mkdir Downloads
wget -q "http://dist.jriver.com/mediacenter@jriver.com.gpg.key" -O- | sudo apt-key add -
sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter20native.list -O /etc/apt/sources.list.d/mediacenter20.list
sudo apt-get update
sudo apt-get install mediacenter20
If you receive an error message after the mkdir line indicating that Downloads already exists, just go ahead with the follow on steps.
After installation completes, you should see MC in the application menu in the upper left hand corner under "sound and video." Open MC, and you're off!
Installing a License:
JRiver offers a 30-day trial, but to keep using the software you'll need to buy and register it. Currently a JRiver for Linux license or Master license will work. There are several ways to install a JRiver License, but the easiest way is to do it on the command line.
When you purchase JRiver, you receive an E-mail with an .mjr file. Download that file to your Raspberry Pi's Downloads directory (the one created above). Then open a terminal by clicking on the icon that looks like a computer and enter the following command: mediacenter20 /RestoreFromFile ~/Downloads/"Media Center20 Linux-YYYYYY.mjr"
Replace the Y's with the numbers from your .mjr file, but otherwise enter the command exactly as shown.
NOTE for advanced users: This will not work correctly if you try to do it via ssh, because Mediacenter needs a display/xserver in order to run. If you have used the headless/VNC setup instructions below, try connecting to the pi using VNC and using lxterminal to register your license.
Audio Setup:
If you're using the Pi's built in audio output (HDMI or stereo), it should just work provided you did the steps above. If you have a USB DAC, you'll need to configure MC to address it just like in normal MC for Linux. That means looking under options --> Audio Devices and looking for a hardware device (an entry for your DAC that has something like "front:" or "surround:" in the name).
Updating:
To update mediacenter (and the rest of your Pi OS) just enter the following line on the terminal:
sudo apt-get update && sudo apt-get dist-upgrade
Troubleshooting Audio
If you followed the steps above and are not getting audio output via HDMI, try the following:
Alsamixer:
In the terminal "alsamixer" and you will see a volume bar (a "graphical" mixer displayed using ASCII characters). Check whether the volume is muted by looking at the bottom of the column: if you see "MM" press the "m" key to unmute and then press escape to exit. If you see "00" then the output isn't muted and that's not the problem (press escape to exit)
Monitor/DVI issues:
Many monitors expect/request a DVI input, which results in the Pi not sending sound to those monitors by default. To find out if that's what's causing your problem, open a terminal, and type sudo nano /boot/config.txt and then find the line that reads #hdmi_drive=2 Remove the "#" symbol, and leave the rest of the line intact. If your file doesn't have that line for some reason, you can just add the line at the end of the file. In either case, save the file by pressing CTRL+O, and exit nano by pressing CTRL+X. Then reboot the Pi and test whether you can get sound over HDMI. Changing that option in config.txt has resolved no-audio issues for several folks with screens that have those issues with HDMI support.
Pops and Dropouts
Pops or dropouts can be caused by a lot of different things and can be tough to troubleshoot. Some users have found that adjusting CPU frequency scaling can help on RPi 2's (RPI 1's won't benefit from this tweak). The following link explains how to set your RPi 2 to stay at maximum CPU frequency (using the performance CPU governor: http://yabb.jriver.com/interact/index.php?topic=95578.msg676554#msg676554
Some notes on getting the most out of MC on the Pi:
The Pi is not a full-featured computer so things will take longer to do on the Pi than on a normal computer. Be patient especially during startup or right after. It might take ten or even thirty seconds for mediacenter to start after you click the icon (depending on whether you have a pi 1 or pi2 and your other settings). Video is not currently supported and the maximize and minimize buttons do not work (at least for me). Other than those two issues, everything I've tested works pretty well.
An Important Note Concerning Power: Pi's are very sensitive to not having enough power; if you plug in too many power hungry USB peripherals it can cause the Pi to reboot or turn off (and corrupt the sd card!). The safest way to resolve this is to use a good powered USB hub and plug the peripherals into that. The best part is that the Hub can also power the Pi itself, so you still only have one wall plug! Some USB hubs won't work very well due to back-power issues, but a recommended list of hubs is available here: http://elinux.org/RPi_Powered_USB_Hubs. To be clear, if you're just plugging in a usb keyboard/mouse and a wi-fi adapter you should be fine with the normal power supply; it's things like external hard drives and USB DACs that need more juice.
Additionally, if you don't want to use a USB hub, you may be able to power more peripherals by adding the following line to your config.txt: max_usb_current=1
That line allows the Pi's USB ports to supply more current to peripherals, which has allowed several forum members to use an external Hard Drive without using a USB hub. [Thanks to Hilton for finding and testing that option.]
Pi's are also sensitive to sudden loss of power: cutting off the power on a pi without shutting down properly can and will corrupt your sd card. For that reason it's important to always shut down your pi appropriately. However accidental power outages do occur, so, as a best practice, consider backing up your sd card with a disk imaging utility once you've gotten everything working the way you want. Another more advanced approach is to hook up a rechargeable battery in between the power supply and the Pi to act as a buffer in case of sudden power loss, and configure the Pi to shut down gracefully when mains power goes out, but that's a more advanced topic.
Running Without a Monitor: If you would like to run the Pi without a monitor attached, that's a slightly more advanced topic. MC needs some kind of "display" in order to run. When a monitor is not attached, the pi will not necessarily start it's display, which will prevent MC from running. The following link provides step by step basic instructions that will provide a relatively easy way to run MC on a Pi with no monitor attached and control it remotely.
http://yabb.jriver.com/interact/index.php?topic=95578.msg674431#msg674431
Status of Features:
What I've tested that works for me:
1) Local audio playback of FLACs and MP3s (Pi 1 and 2)
2) Using the Pi as a library client (Pi 1 and 2)
3) Using the Pi as a DLNA renderer (Pi 1 and 2)
4) Controlling the Pi with gizmo or eos (Pi 1 and 2)
5) Streaming to gizmo from the Pi (works on Pi2, not on the Pi 1)
6) Normal window resizing
7) ALSA-compatible USB DACs
8 ) Using an external hard drive with the Pi (some additional configuration required for some drives)
What I have not tested:
1) DSD (I have no DSD-compatible hardware or files)
2) Airplay, etc. (I have no macs or i-devices to test with)
What is not working/supported:
1) Video Playback
2) Maximize and Minimize buttons
-
Cool! Great work.. :)
-
Thanks! Let me know if I'm missing any steps when you get yours up and running ;D
-
Thanks heaps mwillems. I'm up and running on p2 overclocked. Works on HD recordings fine :)
In case there are other novices like me: At first MC20 appeared under Sound and Video as an app but it would not open. Then I realised I need to add an extra step (I know nothing about Linux so perhaps it is obvious): after entering "sudo apt-get update && sudo apt-get dist-upgrade" i had to enter "y" for yes and wait a few minutes for some updates (i think). And then enter "y" after the next line of code that starts "sudo apt-get". Then I rebooted and all was well.
I reckon if someone like me who had never touched a raspberry pi before today and is not clever with computers can do it, it is promising for MCARM :)
I bought the Pi2 specifically so I can run MC and connect my DIY DAC by i2s and bypass USB for superior audio. So that will be the next challenge. Do you happen to know how to get MC to output i2s on the pi? Perhaps it already does and I do not have to configure anything?
Once again, thank you so much for taking time to share your code findings!
-
In case there are other novices like me: At first MC20 appeared under Sound and Video as an app but it would not open. Then I realised I need to add an extra step (I know nothing about Linux so perhaps it is obvious): after entering "sudo apt-get update && sudo apt-get dist-upgrade" i had to enter "y" for yes and wait a few minutes for some updates (i think). And then enter "y" after the next line of code that starts "sudo apt-get". Then I rebooted and all was well.
I'll make sure to add some clarifications on that.
I bought the Pi2 specifically so I can run MC and connect my DIY DAC by i2s and bypass USB for superior audio. So that will be the next challenge. Do you happen to know how to get MC to output i2s on the pi? Perhaps it already does and I do not have to configure anything?
I'm sorry not to be more help, but I know next to nothing about the i2s outputs on the Pi. Some other folks on the forum have used the HiFiBerry Dac's, which I think use i2s, so they might have some ideas. Regardless, please share your findings when you get it sorted out!
-
Problem: Audio from the Pi2's HDMI is about half as loud as from my other HDMI sources (blue ray and tv hd recorder).
Question: Anyone have ideas of how to increase the Pi's HDMI volume without undermining the sound quality of MC? I found posts on the raspberry forum on how to increase volume, but it involved adding code or installing mixers, and I do not know if they would detract from MC's sound quality.
Thanks for considering :)
-
Problem: Audio from the Pi2's HDMI is about half as loud as from my other HDMI sources (blue ray and tv hd recorder).
Question: Anyone have ideas of how to increase the Pi's HDMI volume without undermining the sound quality of MC? I found posts on the raspberry forum on how to increase volume, but it involved adding code or installing mixers, and I do not know if they would detract from MC's sound quality.
Thanks for considering :)
Is the audio from the Pi's HDMI quieter with all media software on the pi, or just with JRiver? If the former, there's not much JRiver can do about it, you'll need to adjust it in the ALSA settings, or possibly elsewhere. The first thing to check is the volume settings in alsamixer (which should already be installed).
If JRiver is quieter than other players, check and make sure that volume levelling is disabled.
-
Everything is quieter; not only MC.
I will investigate ALSA and how to change the settings after work.
I'm wondering - is there a "best" way to configure ALSA to maximize sound quality with MC? I understand that some digital volume controls can be bypassed so they are bit perfect (sometimes this is achieved when the digital volume is set to maximum), or so they can run at higher number of bits so they introduce less computational artifacts. Anyone any thoughts on what is best for ALSA and MC?
Thank you
-
It turns out the alsamixer had the gain set to 44 or about -17dB (this was on a brand new Pi2 build after following the ARM guide for Pi2). I increased it to -0.3dB (or about that). Interestingly I could not set the gain to 0dB. Does anyone know:
Next problem: For sample rates above 48kHz I change the output format to "no change"; When I play audio then open the dsp settings, MC has switched them back to 48kHz. My audio interface supports higher rates. I will try different output modes later (e.g. kernel, direct etc) and see if that fixes it.
(For anyone like me who had never heard of asla I found these links helpful: https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture
http://en.wikipedia.org/wiki/Alsamixer http://www.volkerschatz.com/noise/alsa.html)
-
Next problem: For sample rates above 48kHz I change the output format to "no change"; When I play audio then open the dsp settings, MC has switched them back to 48kHz. My audio interface supports higher rates. I will try different output modes later (e.g. kernel, direct etc) and see if that fixes it.
Make sure you're addressing one of the hw: devices (they should have a label like "front:" or "surround:" in their description) and you should be able to output higher sample rates.
-
Don't buy ARM devices specifically to run MC on them.
Read the post that announced this beta build:
http://yabb.jriver.com/interact/index.php?topic=95459.msg657558#msg657558
-
Don't buy ARM devices specifically to run MC on them.
Read the post that announced this beta build:
http://yabb.jriver.com/interact/index.php?topic=95459.msg657558#msg657558
I amended my opening post to incorporate this, thanks Bob.
-
Found a small error in the instructions.
Download folder doesn't exist by default and a small typo.
Need to do the following to create the Downloads folder.
mkdir Downloads
cd Downloads
wget http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.66-armhf.deb
sudo dpkg -i MediaCenter-20.0.66-armhf.deb
-
Found a small error in the instructions.
Download folder doesn't exist by default and a small typo.
Need to do the following to create the Downloads folder.
mkdir Downloads
cd Downloads
wget http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.66-armhf.deb
sudo dpkg -i MediaCenter-20.0.66-armhf.deb
That's weird, the "pi" user has a Downloads folder by default (or at least it did when I went through these instructions).
Did you by chance make a new user or log in as root? If so that may be why there was no Downloads folder (root never has normal user folders in its home folder). I'll clarify that above if you can confirm. If the default "pi" user has no Downloads folder by default, I'll note that too.
What was the typo?
-
That's weird, the "pi" user has a Downloads folder by default (or at least it did when I went through these instructions).
Did you by chance make a new user or were you logged in as root? If so that may be why there was no Downloads folder (root never has normal user folders in its home folder). I'll clarify above if you can confirm.
What was the typo?
The typo wasn't a typo, the ~ wasn't working so it must be keyboard issue on my end.
I just used the standard pi user and I wasn't logged in as root.
I was running local x not ssh.
-
The typo wasn't a typo, the ~ wasn't working so it must be keyboard issue on my end.
I just used the standard pi user and I wasn't logged in as root.
I was running local x not ssh.
Got it; the tilde is the standard shell shorthand for the "home directory." I'll add a note above with workaround instructions.
EDIT: added. Thanks for the feedback.
-
Got it; the tilde is the standard shell shorthand for the "home directory." I'll add a note above with workaround instructions.
EDIT: added. Thanks for the feedback.
Just confirming Downloads definitely doesn't exist by default.
pi@raspberrypi ~ $ cd /boot
pi@raspberrypi /boot $ sudo nano config.txt
pi@raspberrypi /boot $ cd ~/Downloads
-bash: cd: /home/pi/Downloads: No such file or directory
-
Just confirming Downloads definitely doesn't exist by default.
pi@raspberrypi ~ $ cd /boot
pi@raspberrypi /boot $ sudo nano config.txt
pi@raspberrypi /boot $ cd ~/Downloads
-bash: cd: /home/pi/Downloads: No such file or directory
Weird; I checked last night with a new install and it was there by default. Just for my peace of mind: you were using the default NOOBS Raspbian installation, not the standalone Raspbian image or the net installer?
-
default NOOBS Raspbian installation
-
Weird. I'll make a few more changes.
-
Alright, followed the directions to the letter - TWICE. While JRiver shows that it is playing, I get NO AUDIO.
I have told it to output to the HDMI in the setup at the beginning. I am hooked up to an HDMI monitor, nothing, nada.
Any advice???
-
Alright, followed the directions to the letter - TWICE. While JRiver shows that it is playing, I get NO AUDIO.
I have told it to output to the HDMI in the setup at the beginning. I am hooked up to an HDMI monitor, nothing, nada.
Any advice???
If you plug some earbuds into the 3.5mm jack is audio playing there? If so try typing "sudo raspi-config" and setting the Pi to force HDMI audio out. If you're not getting any sound from the 3.5mm jack, then it's trying to play to the HDMI output, but it may be an issue with how the Pi is communicating with your monitor.
Is the Pi connected directly to the HDMI input on the monitor (no adapters, etc.)? Do you have another HDMI display you can test? Have you checked the monitor's settings to make sure that it's setup to receive and playback audio? For example, I have an HDMI monitor with no speakers and only a headphone jack; I had to turn on the audio output in the monitor settings and unmute the headphone jack on my monitor before it would work. Do other devices/computers successfully play sound to this monitor?
If all else fails, try typing "sudo nano /boot/config.txt" and adding "hdmi_drive=2" to the end of the file (then reboot). That option is reported to resolve no-audio issues for some folks with screens that have flaky HDMI support.
-
Heard nothing through the HDMI, so I forced it to the audio out jack and heard it, however it was so low, that it is likely playing on my HDMI set, but just too low to hear.
Is there a way to boost the gain in the system? Is there a 'mixer' or control panel which will give me more gain over the output?
I did get it to play 192k FLAC just fine, but would now like to try a USB DAC, and I am sure it is going to need more gain.
Thanks
-
Also, this is a Samsung TV. I normally use the FireTV stick with it, and it plays back quite loud.
All settings are at default in the OS and in J River. I am using both Gizmo and a shared library.
Thanks for the assistance.
-
Heard nothing through the HDMI, so I forced it to the audio out jack and heard it, however it was so low, that it is likely playing on my HDMI set, but just too low to hear.
Is there a way to boost the gain in the system? Is there a 'mixer' or control panel which will give me more gain over the output?
I did get it to play 192k FLAC just fine, but would now like to try a USB DAC, and I am sure it is going to need more gain.
Thanks
I get quite loud volume on the HDMI output, so low volume is not necessarily typical. I have a samsung TV myself and the Pi works fine with it. I assume you've checked the volume settings in both JRiver and on the TV and both are set as high as you can get them?
If that's the case, try typing "alsamixer" into the terminal and check the system volume levels there. If they're below 100%, that's probably your problem.
Other than that, I'm not sure what to suggest except you might want to look around on the Raspberry Pi forums, maybe someone else has had your issue?
-
I get quite loud volume on the HDMI output, so low volume is not necessarily typical. I have a samsung TV myself and the Pi works fine with it. I assume you've checked the volume settings in both JRiver and on the TV and both are set as high as you can get them?
If that's the case, try typing "alsamixer" into the terminal and check the system volume levels there. If they're below 100%, that's probably your problem.
Other than that, I'm not sure what to suggest except you might want to look around on the Raspberry Pi forums, maybe someone else has had your issue?
I think in this case alsamixer is his friend.
-
Must be something with the HDMI. I got it to work fine with the audio output and with a pair of USB Headphones. My guess there is something about the TV and the HDMI implementation. Who knows.
BTW: Alsamixer defaults to 44 - very quiet. You might want to add that to your instructions.
Thanks for the great help!
-
Must be something with the HDMI. I got it to work fine with the audio output and with a pair of USB Headphones. My guess there is something about the TV and the HDMI implementation. Who knows.
BTW: Alsamixer defaults to 44 - very quiet. You might want to add that to your instructions.
Thanks for the great help!
Check the mute on HDMI in Alsamixer.
The hardware output for HDMI is either on or off. The volume is controlled on your TV/Audio device.
-
You shouldn't need this anymore.
libssl1.0.0
-
Ok, thanks for the update; I pulled it from the list of dependencies.
-
How do I check the MUTE in Alsamixer?
I see no such option.
-
How do I check the MUTE in Alsamixer?
I see no such option.
Look at the bottom of the column; do you see "MM" or "OO"? If you see "MM" it's muted. Hit "m" to unmute it.
-
Figured that out, not muted. I am at a loss.
Any ideas guys? The TV is a Samsung and it has always played sound through the OpenElec/Lodi I am running, so I know it is not a hardware issue.
TV Volume at 100%
J River Volume at 100%
Alsamixer at 100% - reporting PCM [db gain: 4.00]
Soundcard is reported as bcm2835 ALSA
-
Did you try adding the line to your config.txt as suggested above?
-
Sorry, saw the line in the config already, but it was commented out by default. Enabled it and all is good.
Display looking for DVI without it and thus wont process audio.
Thanks for the assist.
-
New issue. I am running to HDMI and the audio is fine. Playing 192kHz/24-bit seems to work, though JRiver reports everything I play as 44.1kHz MP3 (coming from a shared library on another computer - no DLNA).
However, a friend I am trying to help out is playing the same to a USB DAC and he is getting drop-out using any file type or sample rate. Played with the buffering in JRiver to no avail.
Any suggestions I can shoot him?
-
New issue. I am running to HDMI and the audio is fine. Playing 192kHz/24-bit seems to work, though JRiver reports everything I play as 44.1kHz MP3 (coming from a shared library on another computer - no DLNA).
However, a friend I am trying to help out is playing the same to a USB DAC and he is getting drop-out using any file type or sample rate. Played with the buffering in JRiver to no avail.
Any suggestions I can shoot him?
This is controlled by the client option in Media Network configuration on the pi (in your case).
Yours is probably set to mp3, his is probably set to none and the pi doesn't have enough horsepower to play what he's trying to play.
-
Changed in both to make sure there is no conversion to MP3.
However, his is connected to a USB DAC (MSB) and he is getting dropouts, while I am connected via HDMI to a TV set and playback is great. Our networks are different and our source storage is different. Assume he needs greater SMB buffering, but wondering where this is set.
Thanks
-
Changed in both to make sure there is no conversion to MP3.
However, his is connected to a USB DAC (MSB) and he is getting dropouts, while I am connected via HDMI to a TV set and playback is great. Our networks are different and our source storage is different. Assume he needs greater SMB buffering, but wondering where this is set.
Thanks
No idea on the SMB.
He's connected ethernet?
You could increase the prebuffering on the Id audio options.
If that doesn't do it you could play with the buffer under the audio device options however I suspect that the issue is more likely bandwidth related if it's happening in the middle of a stream.
-
Yes, connected to the Ethernet on the Pi2.
I assume you mean the pre-buffering in the Tools>Options>Audio, yes?
What about buffering for the USB audio. Is there anything in the USB audio driver?
Thanks
-
Yes, connected to the Ethernet on the Pi2.
I assume you mean the pre-buffering in the Tools>Options>Audio, yes?
Correct
What about buffering for the USB audio. Is there anything in the USB audio driver?
Not that I know of. Just the buffering parameters in MC's ALSA device advanced settings.
-
Thoughts:
1) I would encourage him to try a powered USB hub if the DAC is USB powered. The Pi may not provide enough power for some USB-powered DACs, which could potentially be causing instability or drop outs. If the powered USB hub fixes the issue, there are some things he can try on the Pi as well once we've established that power is the problem.
2) Has he checked the ALSA matrix to see if his DAC is actually supported under linux? It should be listed in the ALSA matrix: http://www.alsa-project.org/main/index.php/Matrix:Main. Some listed devices require special configuration to work correctly (even some fairly common DACs), and aome devices that aren't listed will still work (or work badly).
3) Does he have a Pi 1 or a Pi2? How does CPU usage look during playback? If he's running on a Pi 1, he may need to overclock it.
-
Thanks for the assist:
1) DAC is self powered, though I believe it may require power over the USB as well. I will check into this.
2) DAC is supported.
3) P2 and it is overclocked as well.
-
Thanks for the assist:
1) DAC is self powered, though I believe it may require power over the USB as well. I will check into this.
Try the hub anyway, just to confirm.
2) DAC is supported.
What model is it?
Additionally, has he tried local file playback to rule out network issues (i.e. play a file on the Pi's SD card just to test)
-
Thanks for the assist:
1) DAC is self powered, though I believe it may require power over the USB as well. I will check into this.
2) DAC is supported.
3) P2 and it is overclocked as well.
Hi there.
Something else to consider:
Is anything else plugged into the USB ports? The Pi by default can only supply 600mA to USB devices across all USB ports.
The other thing to check is if the red LED on the board is flashing off and on at all, or a rainbow square appearing in the top right hand corner of the screen with a monitor connected.
These flash to indicate power problems, in which case:
1) Try a bigger 2.1 to 2.4 Amp USB power supply.
2) Try a shorter or different USB cable.
The Pi is very sensitive to getting enough voltage and current. Poor USB cables or power supplies will cause brown-outs which can cause the dropouts. I have found 2 cables that are the same length and look identical perform differently.
Failing that, are you able to try his DAC on your setup?
There are some other things I can suggest to try with changing USB interrupt polling, but lets not go there till you've ruled out power issues.
-
Just an update on my experience with the Pi2 in my little battery powered case.
I've been running the Pi2 at standard 700mHz today and it still plays everything fine. Its running a lot cooler and I suspect I'll get much better battery life out of it too.
I managed to get my little battery setup running for a full day in the office yesterday including a 40 mins drive each way using it in the car. (Streaming via Wifi to the phone and then BT from the phone to the car)
I didn't use it all day, but it was powered on all day and used for about 4-5 hours including the travel time.
-
Just an update on my experience with the Pi2 in my little battery powered case.
I've been running the Pi2 at standard 700mHz today and it still plays everything fine. Its running a lot cooler and I suspect I'll get much better battery life out of it too.
I managed to get my little battery setup running for a full day in the office yesterday including a 40 mins drive each way using it in the car. (Streaming via Wifi to the phone and then BT from the phone to the car)
I didn't use it all day, but it was powered on all day and used for about 4-5 hours including the travel time.
Just FYI the factory default Pi2 clockspeed is 900MHZ not 700 (it's the Pi1 that had a 700MHz default clock); if you've clocked it to 700MHZ, you're actually underclocking (which I expect would dramatically improve battery life).
I agree based on my own experiments that overclocking shouldn't be necessary on the Pi2 for most applications, it's just more or less mandatory for the Pi1. I haven't tried underclocking the pi2, but if that its what you're doing, I'd be interested in your observations about performance.
Also, if you want to squeeze out a little more power, you can use the powersave cpu frequency scaling governor; that would probably net some extra battery life too as it downclocks like crazy whenever nothing is happening. It does result in a performance hit, but if you've got performance to burn...
-
Just FYI the factory default Pi2 clockspeed is 900MHZ not 700 (it's the Pi1 that had a 700MHz default clock); if you've clocked it to 700MHZ, you're actually underclocking (which I expect would dramatically improve battery life).
I agree based on my own experiments that overclocking shouldn't be necessary on the Pi2 for most applications, it's just more or less mandatory for the Pi1. I haven't tried underclocking the pi2, but if that its what you're doing, I'd be interested in your observations about performance.
Also, if you want to squeeze out a little more power, you can use the powersave cpu frequency scaling governor; that would probably net some extra battery life too as it downclocks like crazy whenever nothing is happening. It does result in a performance hit, but if you've got performance to burn...
Yes I've underclocked to 700Mhz and It plays MP3 and FLAC fine though it does occasionally stutter at the beginning of FLAC tracks if you have cross fade turned on and are downsampling or upsampling.
Otherwise its a little slower to render album art on JRemote but still just as usable.
-
Hi!
I'd just like to share an alternative for remote access to the Pi using standard windows RDP which is nice and fast on a local network.
This is a variation on some things I found around the place to make it really simple to remotely login to the Pi desktop.
This method allows you to see the same desktop that's running on the HDMI screen from a remote computer without having a monitor connected to the Pi.
It uses x11vnc which is a full featured and more powerful vnc server than the tightvncserver.
It's also what allows the remote viewing of the HDMI output which tightvncserver cant do.
You'll need to install XRDP too but that's pretty straight forward and the good news is there's a nice noobs install for x11vnc.
First install XRDP as follows:
sudo apt-get update && sudo apt-get install xrdp
Now we edit the config file for XRDP:
sudo nano /etc/xrdp/xrdp.ini
Change the xrdp.ini in the editor so it matches this below. When you're finished press control X and then Y at the prompt to save it.
xrdp1 is the profile we'll use to login to the desktop.
[globals]
bitmap_cache=yes
bitmap_compression=yes
port=3389
crypt_level=low
channel_code=1
# set empty username because VNC auth
# doesn't actually use username, so no
# point in asking the user for one.
[xrdp1]
name=Active Local Login
lib=libvnc.so
username=
password=ask
ip=127.0.0.1
port=5900
[xrdp2]
name=Clean Session
lib=libvnc.so
username=
password=ask
ip=127.0.0.1
port=5901
If you've installed tightvncserver previously you'll need to remove it with:
sudo apt-get remove tightvncserver
Now we can install x11vnc the noobs way.
In the terminal session type:
cd ~/Downloads
wget http://goo.gl/MbfUEp -O isx11.sh
and then press enter to download the installer
Once it has finished downloading, type the following and follow the instructions:
sudo bash isx11.sh
One last change to Mwillems startup script.
sudo nano /etc/MC20start.sh
Copy or edit it to look like this. Mwillems may want to chime in with the precise crontab settings he's using this with so it checks periodically if MC is running and starts it if it's stopped for any reason.
I'm using the same settings in my script but I only start it once at boot.
export USER=pi
ps -e | grep x11vnc || x11vnc :0 -localhost -geometry 1920x1080
export DISPLAY=':0'
ps -e | grep mediacenter || mediacenter20
control X and then y to save
If you haven't created this file previously you'll need to chmod it:
sudo chmod +x /etc/MC20start.sh
And then edit crontab with:
crontab -e
Add this line at the end and then control x and then press y to save.
@reboot /etc/MC20start.sh
Now Reboot with:
sudo reboot
log back in to the SSH terminal session
After a Reboot you can type the following to check all the services are running.
sudo netstat -anpt | grep -E "vnc|xrdp"
You should get something like this.
tcp 0 0 0.0.0.0:3389 0.0.0.0:* LISTEN 2018/xrdp
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 2721/x11vnc
tcp 0 0 127.0.0.1:3350 0.0.0.0:* LISTEN 2057/xrdp-sesman
Now you should be able to use a standard windows remote desktop to login using the ip address of your pi to connect and view your default Pi desktop. :)
VNC will also still work if that floats your boat, but since I mostly work from windows machines RDP works great for me.
x11vnc is still pretty light weight, at idle logged into the GUI desktop I'm using 4% CPU and 10% when playing a 44.1K FLAC. If you go crazy scrolling in the gui it'll use 70% or more of all 4 cores but the audio still didn't stutter for me. The GUI is nice and snappy!
Mwillems if you want to test this out, tidy it and integrate into your guide be my guest!
-
I'm happy to integrate it over the weekend, but one quick question before I do: does your method run correctly if the device is booted without anything attached to the HDMI output? Long ago and far away, I pursued an x11VNC-based method, but found that, precisely because it tries to use the actual GUI output, that it didn't work reliably when the system was run truly headless (either x would fail to launch, or the vnc server would fail).
I'm sure there are configuration steps that will side step all that (and you may have outlined them above), but the main reason I went to tigervnc (or tightvnc) was that it was trivially easy to create a dummy display, sidestepping any issues resulting from the presence or absence of an actual display.
For anyone looking to run the script once a minute to regularly to check if MC is running and restart it, the correct cron entry is * * * * * /path/to/script/scriptname.sh
If you're only running it at boot, you don't need some of the conditional commands in the script. I'll try and integrate this discussion above.
-
I'm happy to integrate it over the weekend, but one quick question before I do: does your method run correctly if the device is booted without anything attached to the HDMI output? Long ago and far away, I pursued an x11VNC-based method, but found that, precisely because it tries to use the actual GUI output, that it didn't work reliably when the system was run truly headless (either x would fail to launch, or the vnc server would fail).
I'm sure there are configuration steps that will side step all that (and you may have outlined them above), but the main reason I went to tigervnc (or tightvnc) was that it was trivially easy to create a dummy display, sidestepping any issues resulting from the presence or absence of an actual display.
For anyone looking to run the script once a minute to regularly to check if MC is running and restart it, the correct cron entry is * * * * * /path/to/script/scriptname.sh
If you're only running it at boot, you don't need some of the conditional commands in the script. I'll try and integrate this discussion above.
does your method run correctly if the device is booted without anything attached to the HDMI output
YES :)
Remember we've forced HDMI mode with the following from my other post.
Here's my /boot/config.txt
Ive changed a couple other things in here:
This changes console resolution to standard 1080p
framebuffer_width=1920
framebuffer_height=1080
This forces HDMI to 1080p 60hz even with no monitor attached.
Which means if you need to plug it in to a monitor or TV after running in headless mode, it wont be in a minicule unusuable resolution.
BTW you need to boot into gui mode for some of the features to work in headless mode.
hdmi_group=2
hdmi_mode=82
I believe because of the above setting I also need to set this to enable HDMI audio
hdmi_drive=2
-
I snarfed the rdp method to add to the Id.
It's working well. I think I'm going to make one change to the /mediaserver mode. I'm going to have it NOT hide the main window since that doesn't serve any purpose on the Id since you need X running anyway.
For people that were running MC "hidden" perhaps I'll make an /iconic option.
What /mediaserver is mostly intended for is to suppress user prompts.
-
Nice one! I was wondering if it might be useful for that given the number of users that asked for a Remote Desktop into the Id.
-
Nice one! I was wondering if it might be useful for that given the number of users that asked for a Remote Desktop into the Id.
It's especially elegant as it still supports cross-platform solutions like VNC
-
Just to add to the RDP discussion.
Windows RDP to the Pi works great from a windows machine but the free iPhone Microsoft RDP app doesn't scale to fit the screen properly. VNC viewer on the iPhone however works perfectly. :) Best of both worlds. :)
-
I changed the /mediaserver mode and have been testing this on my beta Id. It works nicely with or without headless booting now...
-
It's especially elegant as it still supports cross-platform solutions like VNC
The way Hilton did this precludes the use of vnc directly, it uses rdp instead (the vnc server is only listening on localhost).
I'm wondering since there is RDP on just about anything, if it makes sense to support vnc? I assume not but if so how to get around the issue that both need passwords? Since the rdp is riding on vnc wouldn't that require two chained passwords?
-
The way Hilton did this precludes the use of vnc directly, it uses rdp instead (the vnc server is only listening on localhost).
That's not necessarily required, he was piggybacking off of my script (http://yabb.jriver.com/interact/index.php?topic=91227.0) that was intended to be used with no VNC password and using something like SSH for authentication instead. You ssh in with port mapping (using the -L flag), and then run the VNC client once you get there. It was intended for security, not convenience, and limiting the VNC to localhost isn't really necessary.
You could just as easily leave the localhost switch off and have direct access to the VNC client, which with x11vnc is the real screen with support for hardware acceleration. You can always have XRDP listen on a different port, which is exactly what his clean startup option does (5901). You just need to make sure to export the correct display first (I think), and they'll both point at the same display.
Several parts of my script don't need to be there anymore (like the conditional tests, which were aimed at a cronjob running every few minutes, not once on startup), unless you do want to run them at intervals to make sure everything is still running.
I'm wondering since there is RDP on just about anything, if it makes sense to support vnc? I assume not but if so how to get around the issue that both need passwords? Since the rdp is riding on vnc wouldn't that require two chained passwords?
I don't think it has to work that way (see above), I think you can offer them as separate options a the same time. FWIW, my personal experience of linux rdp support has been pretty flaky. I've needed to use it for work, and I always wind up screaming (or just giving up and booting windows). It's great on windows, but...
Modern crossplatform VNC viewers (tiger vnc or ultra vnc) are pretty fast. I get a significantly better "desktop experience" with Tiger VNC than I do with Team Viewer or RDP.
-
Also Hilton, I wanted to thank you for pointing me back to x11vnc. I've now got hardware graphics acceleration on my virtual machines on my headless server, which I've been vainly poking at without much success (futzing with VirtualGL) for a couple months. Turns out when you use the actual hardware output as your VNC $DISPLAY you get some incidental goodies 8)
Well worth a few extra steps with x11vnc.
-
I'm posting instructions for headless operation here because I'm out of space in the first post and didn't reserve the second and third posts for expansion ;)
The following steps outline a very basic method of creating a virtual display and allowing for remote control of Mediacenter on the pi. NOTE: If you're using a different username than "pi", you should replace all instances of "pi" in the code below with your username.
Enter the following commands sudo apt-get install tightvncserver
tightvncserverAfter the second command, you will be prompted for a regular password, pick one you will remember. You will also be asked whether you want to create a view-only password. Type 'n'.
If it worked correctly you should see something like: New 'X' desktop is pi:1
If you see a number other than :1 in that output, use that instead of :1 below. Now enter the following lines in the terminal sudo vncserver -kill :1
vncserver :1 -geometry 1920x1080
You should now have a virtual desktop running on your pi. Test it out by trying to log in from another computer using a VNC client. For example, tigervnc is available for Windows, Mac, and Linux: https://bintray.com/tigervnc/stable/tigervnc/1.4.3
When you start TigerVNC it will ask you for the VNC server details. Enter the ip address* of your pi, followed by ":1". It will look something like 192.168.1.35:1 Once you enter the address, click connect, and it will prompt you for your password.
*If you don't know the ip address of your pi, enter "sudo ifconfig" in a terminal on your pi, and it will tell you. You're looking for a 4-part number separated by periods next to the phrase "inet addr." You want the one in the paragraph labelled eth0 if your pi has a wired connection or wlan0 if your pi has a wireless connection.
You should now be looking at a virtual desktop on your pi, from which you can run MC!
We're not done yet, though, as we still need to configure the pi to start the vncserver and MC on boot. The easiest way to do this is with a cron script. Type "sudo nano ~/headless" into the terminal and type the following#!/bin/bash
export USER=pi
ps -e | grep tightvnc || vncserver :1 -geometry 1920x1080
export DISPLAY=':1'
ps -e | grep mediacenter || mediacenter20 /mediaserver
Once you're done, press CTRL-X, and choose "y" and press "enter" twice. Now type
sudo chmod 755 ~/headless
crontab -e
After you enter the second command, you may be prompted you to choose an editor; if so choose /bin/nano, which should be option 1. Now you should now be looking at a file with some information in it.
If you want mediacenter to launch on boot type the following line at the bottom of the file:@reboot /home/pi/headless > /dev/null
If, instead, you want mediacenter to launch on boot, but also make sure that it's still running and relaunch it if it has crashed, enter the following at the bottom of the file INSTEAD of the previous
* * * * * /home/pi/headless > /dev/null
Once you've added the one you want, press CTRL-X and then "y" and "enter" twice. Now reboot your pi as described above, and within a few minutes you should be able to access MC and your VNC desktop.
There are some limitations to this method. For example, you cannot use this method to control the pi's actual display output, so you couldn't use this to remote control a pi's display when it's hooked up to a monitor.
If you want a more robust solution that doesn't have these limitations (but requires a few more steps), Hilton provided step by step instructions for a fuller featured remote access method which allows using windows remote desktop, and an alternative VNC method that allows you to remotely control the Pi. His method can be found here: http://yabb.jriver.com/interact/index.php?topic=95578.msg666290#msg666290, with some extra configuration bits here: https://yabb.jriver.com/interact/index.php?topic=95578.msg666323#msg666323.
-
Hello,
When I try to follow this guide, I get this error message when installing JRiver.
I can still run it, but it won't actually play music and after I boot the system the only thing that I see is a blinking 'asci prompt' - not X or even the normal command prompt...
Please help
////////
sudo dpkg -i MediaCenter-20.0.110-armhf.deb
Selecting previously unselected package mediacenter20.
(Reading database ... 78723 files and directories currently installed.)
Unpacking mediacenter20 (from MediaCenter-20.0.110-armhf.deb) ...
dpkg: dependency problems prevent configuration of mediacenter20:
mediacenter20 depends on xfonts-unifont; however:
Package xfonts-unifont is not installed.
dpkg: error processing mediacenter20 (--install):
dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils ...
Errors were encountered while processing:
mediacenter20
-
I had a hard time following some parts of your post (does "I can still run it" refer to the pi or to Mediacenter?) You seem to have two probably unrelated issues. I'm not in front of a pi right now, but here are some suggestions:
1) X not starting
This is not a mediacenter issue. Are you sure you:
a) started from a generic NOOBS installation, and
b) set the pi to boot into graphical mode by default as described in the guide?
If you did both of those things and aren't seeing x or the command line login prompt when booting, you may have a corrupted installation. You should always get at least a command line login prompt (a text prompt asking you for a login name). If you see a blinking cursor with no login prompt, you're probably looking at an installation that failed to boot for some reason, possibly due to sdcard corruption (common when power is interrupted without a proper shutdown). To be clear there's nothing about installing mediacenter that should cause boot issues.
2)Installation problem
As to the installation problem, it looks like the dependencies may have changed in the most recent build. I'm not in front of a pi right now so I can't test, but (once you get to a command prompt) I would try the following:
sudo apt-get install xfonts-unifont
Then, if that succeeds, try entering the "sudo dpkg..." command again. That should fix it (although I would appreciate confirmation).
-
Thanks Mate,
It was a bit confusing but it looks like i managed to get JRiver to boot properly and also managed to activate my optical out add-on board.
The last part I'm struggling with getting JRiver and tight VNC to start automatically...
I tried following the instructions posted but they won't start automatically...
Any advice would be welcome!
-
Thanks Mate,
It was a bit confusing but it looks like i managed to get JRiver to boot properly and also managed to activate my optical out add-on board.
The last part I'm struggling with getting JRiver and tight VNC to start automatically...
I tried following the instructions posted but they won't start automatically...
Any advice would be welcome!
Do you mean the instructions two posts above in this thread? If so:
To troubleshoot, boot your pi as you normally would, but don't take any steps to actively start mediacenter. Wait five minutes, and then please post the output of the following five commands:
ps -e | grep vnc
ps -e | grep mediacenter
crontab -l
cat ~/headless
ls -la ~/
If one of the commands has no output, please indicate that as well.
-
Hello Mate,
It looks like it working? I think.
pi@raspberrypi ~ $ ps -e | grep vnc
2271 ? 00:00:00 Xtightvnc
pi@raspberrypi ~ $ ps -e | grep mediacenter
2286 ? 00:00:13 mediacenter20
pi@raspberrypi ~ $ crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
@reboot /home/pi/headless > /dev/null
pi@raspberrypi ~ $ cat ~/headless
#!/bin/bash
export USER=pi
ps -e | grep tightvnc || vncserver :1 -geometry 1920x1080
export DISPLAY=':1'
ps -e | grep mediacenter || mediacenter20 /mediaserver
pi@raspberrypi ~ $ ls -la ~/
total 112
drwxr-xr-x 17 pi pi 4096 May 19 08:26 .
drwxr-xr-x 3 root root 4096 May 6 22:20 ..
-rw-r--r-- 1 pi pi 69 May 18 15:44 .asoundrc
-rw------- 1 pi pi 1029 May 18 19:03 .bash_history
-rw-r--r-- 1 pi pi 220 May 6 22:20 .bash_logout
-rw-r--r-- 1 pi pi 3243 May 6 22:20 .bashrc
drwxr-xr-x 9 pi pi 4096 May 18 15:58 .cache
drwxr-xr-x 14 pi pi 4096 May 18 16:05 .config
drwx------ 3 pi pi 4096 May 18 14:27 .dbus
drwxr-xr-x 2 pi pi 4096 May 18 15:56 Desktop
-rw-r--r-- 1 pi pi 35 May 19 08:26 .dmrc
drwxr-xr-x 2 pi pi 4096 May 18 15:58 Downloads
drwxr-xr-x 2 pi pi 4096 May 18 16:28 .fontconfig
drwxr-xr-x 2 pi pi 4096 May 18 14:27 .gstreamer-0.10
drwx------ 2 pi pi 4096 May 18 14:27 .gvfs
-rwxr-xr-x 1 root root 161 May 18 16:49 headless
drwxr-xr-x 4 pi pi 4096 May 18 15:40 .jriver
drwx------ 3 pi pi 4096 May 18 14:27 .local
-rw-r--r-- 1 pi pi 675 May 6 22:20 .profile
drwxrwxr-x 2 pi pi 4096 Jan 27 08:34 python_games
drwxr-xr-x 3 pi pi 4096 May 18 14:27 .themes
drwx------ 4 pi pi 4096 May 18 14:33 .thumbnails
drwxr-xr-x 2 pi pi 4096 May 18 15:41 Video
drwx------ 2 pi pi 4096 May 19 08:26 .vnc
-rw------- 1 pi pi 266 May 19 08:26 .Xauthority
-rw------- 1 pi pi 2782 May 19 08:26 .xsession-errors
-rw------- 1 pi pi 6870 May 19 08:27 .xsession-errors.old
In other news, perhaps it would be easier to set if JRiver made it's own distribution image? that would come pre-configured with all the files etc? It would also be good to have built in support for thing like https://www.hifiberry.com/digiplus/ (https://www.hifiberry.com/digiplus/) that add optical and coax to the RPI.
-
Hello Mate,
It looks like it working? I think.
pi@raspberrypi ~ $ ps -e | grep vnc
2271 ? 00:00:00 Xtightvnc
pi@raspberrypi ~ $ ps -e | grep mediacenter
2286 ? 00:00:13 mediacenter20
pi@raspberrypi ~ $ crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
@reboot /home/pi/headless > /dev/null
pi@raspberrypi ~ $ cat ~/headless
#!/bin/bash
export USER=pi
ps -e | grep tightvnc || vncserver :1 -geometry 1920x1080
export DISPLAY=':1'
ps -e | grep mediacenter || mediacenter20 /mediaserver
pi@raspberrypi ~ $ ls -la ~/
total 112
drwxr-xr-x 17 pi pi 4096 May 19 08:26 .
drwxr-xr-x 3 root root 4096 May 6 22:20 ..
-rw-r--r-- 1 pi pi 69 May 18 15:44 .asoundrc
-rw------- 1 pi pi 1029 May 18 19:03 .bash_history
-rw-r--r-- 1 pi pi 220 May 6 22:20 .bash_logout
-rw-r--r-- 1 pi pi 3243 May 6 22:20 .bashrc
drwxr-xr-x 9 pi pi 4096 May 18 15:58 .cache
drwxr-xr-x 14 pi pi 4096 May 18 16:05 .config
drwx------ 3 pi pi 4096 May 18 14:27 .dbus
drwxr-xr-x 2 pi pi 4096 May 18 15:56 Desktop
-rw-r--r-- 1 pi pi 35 May 19 08:26 .dmrc
drwxr-xr-x 2 pi pi 4096 May 18 15:58 Downloads
drwxr-xr-x 2 pi pi 4096 May 18 16:28 .fontconfig
drwxr-xr-x 2 pi pi 4096 May 18 14:27 .gstreamer-0.10
drwx------ 2 pi pi 4096 May 18 14:27 .gvfs
-rwxr-xr-x 1 root root 161 May 18 16:49 headless
drwxr-xr-x 4 pi pi 4096 May 18 15:40 .jriver
drwx------ 3 pi pi 4096 May 18 14:27 .local
-rw-r--r-- 1 pi pi 675 May 6 22:20 .profile
drwxrwxr-x 2 pi pi 4096 Jan 27 08:34 python_games
drwxr-xr-x 3 pi pi 4096 May 18 14:27 .themes
drwx------ 4 pi pi 4096 May 18 14:33 .thumbnails
drwxr-xr-x 2 pi pi 4096 May 18 15:41 Video
drwx------ 2 pi pi 4096 May 19 08:26 .vnc
-rw------- 1 pi pi 266 May 19 08:26 .Xauthority
-rw------- 1 pi pi 2782 May 19 08:26 .xsession-errors
-rw------- 1 pi pi 6870 May 19 08:27 .xsession-errors.old
Yes it appears to be working. Are you seeing issues? If you can described what your issues are, I can help. Just to be clear, if you have the Pi plugged into a monitor, you won't see anything because the VNC creates a virtual desktop. The only way to see that desktop is using VNC. So the final test of whether it's working is to use a VNC viewer to try and connect to the pi. The method above is solely for a headless configuration. If you want both remote access and monitor access to look the same, you'll need to use Hilton's method above.
In other news, perhaps it would be easier to set if JRiver made it's own distribution image? that would come pre-configured with all the files etc? It would also be good to have built in support for thing like https://www.hifiberry.com/digiplus/ (https://www.hifiberry.com/digiplus/) that add optical and coax to the RPI.
Let me clarify: I don't work for JRiver, I'm just an enthusiast, so take what I say with a grain of salt, but I'm pretty sure that's more or less what JRiver is selling with their Id Pi product, so if that's what you're looking for, you may be able to get it. The staff at JRiver haven't weighed in on "community" images, so I can't speculate about that.
"Built in" support for the digi is already in the kernel; if it's anything like the hifiberry dac, you only need to enter two or three lines on the terminal to get it working. If you mean "enabled by default in a pre-made image" that might be harder as many of the available i2c audio add ons use the exact same output pins on the Pi. So if you enabled all of them in an image it might not work very well (i.e. interfaces might get confused about which one was actually connected).
-
Thanks Mate,
Much appreciate the help!
It's working very well, I don't want to touch it ;-)
-
Hi There,
I have a tiny issue,
While JRiver runs on my RPI - it seems to have gone to another desktop as I can't see it when I'm connected via VNC - however the music is playing and I can control it with the JRemote app... Any idea on how to fix this? or switch desktops in RPI?
Thanks you!
-
LXDE has a desktop switch on the task bar at the bottom (you can see four squares next to each other), so that will let you change desktops within the virtual VNC session.
Also, which version of MC are you running? Earlier versions hide themselves when you pass the /mediaserver switch; more modern versions only start minimized when you pass that switch. So if you're running an older version, it may not be running on a different desktop, it may just be hidden. Try modifying the script above to remove the /mediaserver argument and see if that helps.
-
I had problems with this before on a full Linux PCs, but the same affliction occurs again with pi install, I can't get my mjr file to install my license.
After first install, MC shows up as expected with the 30 day trial, so I put my master licence code in the register box, which is accepted and I get an mjr file.
So i go into a terminal window and do as instructed elsewhere to restore the licence from file. First time I do this everything seems to be ok, message comes back saying its registered ok. Go into MC and I get a "licence has expired" message. Redo the registration in terminal window and get "segmentation fault". Which obviously means something, but not to me as a Linux newbie.
My .jriver directory's permissions are "pi pi drwxr-xr-x" and the ones below it and the files are similar, which look ok to me. Pi being the user.
So I purged MC and reinstalled and now I just get a segmentation fault. The mjr file is less than 14 days old. So stuck. Anyone any ideas?
Thanks
Paul
-
I had problems with this before on a full Linux PCs, but the same affliction occurs again with pi install, I can't get my mjr file to install my license.
After first install, MC shows up as expected with the 30 day trial, so I put my master licence code in the register box, which is accepted and I get an mjr file.
So i go into a terminal window and do as instructed elsewhere to restore the licence from file. First time I do this everything seems to be ok, message comes back saying its registered ok. Go into MC and I get a "licence has expired" message. Redo the registration in terminal window a find get "segmentation fault". Which obviously means something, but not to me as a Linux newbie.
My .jriver directory's permissions are "pi pi drwxr-xr-x" and the ones below it and the files are similar, which look ok to me. Pi being the user.
So I purged MC and reinstalled and now I just get a segmentation fault. The mjr file is less than 14 days old. So stuck. Anyone any ideas?
Thanks
Paul
-
I had problems with this before on a full Linux PCs, but the same affliction occurs again with pi install, I can't get my mjr file to install my license.
After first install, MC shows up as expected with the 30 day trial, so I put my master licence code in the register box, which is accepted and I get an mjr file.
So i go into a terminal window and do as instructed elsewhere to restore the licence from file. First time I do this everything seems to be ok, message comes back saying its registered ok. Go into MC and I get a "licence has expired" message. Redo the registration in terminal window and get "segmentation fault". Which obviously means something, but not to me as a Linux newbie.
My .jriver directory's permissions are "pi pi drwxr-xr-x" and the ones below it and the files are similar, which look ok to me. Pi being the user.
So I purged MC and reinstalled and now I just get a segmentation fault. The mjr file is less than 14 days old. So stuck. Anyone any ideas?
Thanks
Paul
The segfault is unrelated to the registration issue, and will be hard blocker, so let's work that issue first. Did you follow the guide above exactly? A segfault is usually the result of a missing dependency, so take especial note of the list of dependencies in the instruction post.
The current build of MC requires a dependency that wasn't previously required; the guide is up to date now, but if you used the guide before a few days ago you may be missing xfonts-unifont. If you think that might be your issue, try: sudo apt-get install xfonts-unifont
Once you get your segfault worked out, we'll start working the license issue.
-
Thanks for the swift response.
I just ran the install for xfonts-uni font and it says it's already installed. 0 upgraded 0 newly installed etc, so it not that.
I did install it a week ago and followed the instructions to the letter, wouldn't know what to do if I deviated from them.. No errors came back during the install. Thought they were clear and excellent. MC did work until I tried to instal the licence. It's the licence not installing properly that seems to have caused the issue. Would redoing it all from scratch be worthwhile?
-
You'll need to try what I suggested in my prior post. Make sure you have all of your dependencies installed. The segfault and the registration issue are probably unrelated.
EDIT: I see you edited your post, I'll respond below.
-
mwilliams
Seems like taptalk on the iPad is making a mess of my posts and their timing so now using a computer. It seems like you read the repost of my original post before I had a chance to edit it with what I wanted to say. I have tried your suggestion with no success. So tomorrow, going to go with a complete reinstall with the revised instructions, just in case I missed anything.
-
A reinstall might help. It's also important to note that only the most current build of MC for ARM will accept a license, so you should make sure you have the most up to date version.
-
LXDE has a desktop switch on the task bar at the bottom (you can see four squares next to each other), so that will let you change desktops within the virtual VNC session.
Also, which version of MC are you running? Earlier versions hide themselves when you pass the /mediaserver switch; more modern versions only start minimized when you pass that switch. So if you're running an older version, it may not be running on a different desktop, it may just be hidden. Try modifying the script above to remove the /mediaserver argument and see if that helps.
Thanks Mate.
I've installed version 20.0.66
Where do I find the command line and media centre 'switch'?
I've now messed it up completely and basically get two instances of MC running on the Pi...
I also tried looking at the other desktops to try and find it but without luck...
Please advise, thank you!
-
Thanks Mate.
I've installed version 20.0.66
Where do I find the command line and media centre 'switch'?
I've now messed it up completely and basically get two instances of MC running on the Pi...
I also tried looking at the other desktops to try and find it but without luck...
Please advise, thank you!
With that version, it's almost certainly the mediaserver switch that's the issue. Type in the terminal sudo nano ~/headlessYou'll then see: #!/bin/bash
export USER=pi
ps -e | grep tightvnc || vncserver :1 -geometry 1920x1080
export DISPLAY=':1'
ps -e | grep mediacenter || mediacenter20 /mediaserver
On the last line, delete "/mediaserver", then hit ctrl-x, press y, and enter twice. That should fix the issue after a reboot.
By the way, if you want to update to a newer licensed version (which you will eventually as the build you're using will time out in June), enter the following commands into the terminal
wget -q "http://dist.jriver.com/mediacenter@jriver.com.gpg.key" -O- | sudo apt-key add -
sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter20native.list -O /etc/apt/sources.list.d/mediacenter20.list
sudo apt-get update && sudo apt-get dist-upgrade
In the future if you want to update again, you only have to enter the last line (sudo apt-get update...).
These instructions are in the first post now, but weren't there when you followed the guide because there wasn't a licensed version until recently.
I've now messed it up completely and basically get two instances of MC running on the Pi...
I also tried looking at the other desktops to try and find it but without luck...
Please advise, thank you!
A reboot should resolve those issues unless you're doing something drastic.
-
Thanks Mate,
I followed your advice and now the MC window is back! ;-)
I have a couple of new problems though,
I bought a master license upgrade (already had a MC 20 win license) - but when I input it, either via the terminal or type it in MC it says it cant find the license or 'segmentation error' when using the terminal... Do I need a specific Linux license?
Also,
I've taken another look at the HiFiberry digi+ set up instructions and noticed there was a stage I skipped - It says: Remove the following lines from /etc/modprobe.d/raspi-blacklist.conf on Raspbian. If you’re using another distribution, check where it configures module blacklists.' - I couldn't find this folder/file - do you have any idea where I could look for it?
Lastly,
I feel like a complete N00b but the 'start button' at the top left corner of the desktop (where you could reboot from the GUI) - went missing... I tried messing with it but with no success.
Thanks very much mate!
-
Thanks Mate,
I followed your advice and now the MC window is back! ;-)
I have a couple of new problems though,
I bought a master license upgrade (already had a MC 20 win license) - but when I input it, either via the terminal or type it in MC it says it cant find the license or 'segmentation error' when using the terminal... Do I need a specific Linux license?
The master license will work for this (I use it myself). To be clear, you don't enter the registration code from the command line, you use the .mjr file that you got when you registered on the command line (as described in the first post). Is that what you mean?
When you're entering it in the terminal are you doing it in the VNC desktop or through ssh or something else? Be as specific as you can be.
Also,
I've taken another look at the HiFiberry digi+ set up instructions and noticed there was a stage I skipped - It says: Remove the following lines from /etc/modprobe.d/raspi-blacklist.conf on Raspbian. If you’re using another distribution, check where it configures module blacklists.' - I couldn't find this folder/file - do you have any idea where I could look for it?
No clue about that, I've never seen a "raspi-blacklist.conf" file, so those instructions may be outdated. You should ask HiFiberry what they mean.
Lastly,
I feel like a complete N00b but the 'start button' at the top left corner of the desktop (where you could reboot from the GUI) - went missing... I tried messing with it but with no success.
Thanks very much mate!
I don't know, I've never seen it go missing before. You can always reboot by typing "sudo reboot" into the terminal.
-
The master license will work for this (I use it myself). To be clear, you don't enter the registration code from the command line, you use the .mjr file that you got when you registered on the command line (as described in the first post). Is that what you mean?
When you're entering it in the terminal are you doing it in the VNC desktop or through ssh or something else? Be as specific as you can be.
Thanks Mate,
I tried inputting the license as per the command posted (obviously referring to the right file name for my license) both via SSH and through MC on the graphical interface from the help menu - when doing this I actually plugged the Berry to a screen, keyboard etc ;-).
I hope I solve this before the trial expires ;)
Thanks again for all the help, really appreciated!
-
Thanks Mate,
I tried inputting the license as per the command posted (obviously referring to the right file name for my license) both via SSH and through MC on the graphical interface from the help menu - when doing this I actually plugged the Berry to a screen, keyboard etc ;-).
I hope I solve this before the trial expires ;)
Thanks again for all the help, really appreciated!
The terminal method is more reliable than the help menu method, and the terminal method works fine if you do it when using a virtual terminal in the GUI (whether VNC or actually hooked up to a monitor).
If you need to do it via ssh, you need to export a working display first. If you've setup the headless method described above, you'd enter "export DISPLAY=:1" press enter, and then try the terminal license restore.
-
I'm thinking the build 110 really shouldn't have issues with entering the registration info from the help dialog box.
Are you certain you have an internet connection on the pi? That a requirement to reach the license server.
-
Still cant register my master licence.
Completely reinstalled a noob raspbian onto a freshly formatted sd card. followed mwillems instructions to the letter, using ssh from my macbook pro, all steps completed properly without error until I came to register. I do have v110, mc runs but says its in trial mode and I do have internet access as I got all the updates etc OK. The permissions on my .jriver folder are "drwxr-xr-x pi pi" where pi is the user, so i think they are OK.
The registration results in a "segmentation fault" error again, but at least I am not alone here.
Any ideas anyone?
-
Still cant register my master licence.
Completely reinstalled a noob raspbian onto a freshly formatted sd card. followed mwillems instructions to the letter, using ssh from my macbook pro, all steps completed properly without error until I came to register. I do have v110, mc runs but says its in trial mode and I do have internet access as I got all the updates etc OK.
The registration results in a "segmentation fault" error again, but at least I am not alone here.
Any ideas anyone?
Try running the command on a virtual terminal (like lxterminal) in the GUI on the pi instead of via ssh (i.e. use VNC or hook it up to a monitor). Or see my post immediately above Bob's for an explanation of how to make it work via ssh.
I'm thinking the build 110 really shouldn't have issues with entering the registration info from the help dialog box.
Are you certain you have an internet connection on the pi? That a requirement to reach the license server.
I've never actually had the help menu registration work on Linux for me including on this build.
-
Try running it on a virtual terminal (like lxterminal) in the GUI on the pi instead of via ssh (i.e. use VNC or hook it up to a monitor). See my post immediately above Bob's for an explanation of how to make it work via ssh.
I've never actually had the help menu registration work on Linux for me including on this build.
Interesting.
I tested that before uploading this build. Perhaps a certificate issue on your pi? Try:
sudo c_rehash /etc/ssl/certs
-
Thanks for those ideas, I ran the certs command as suggested by Bob and that ran through OK. Then went and tried again using ssh, still get set fault error. Connected the pi to the tele with keyboard mouse and used the terminal in the pi's gui and got a different message "Could not restore licence from file XXXXX.mjr". The licence file is less than a week old.
Does this mean anything to either of you?
-
Thanks for those ideas, I ran the certs command as suggested by Bob and that ran through OK. Then went and tried again using ssh, still get set fault error. Connected the pi to the tele with keyboard mouse and used the terminal in the pi's gui and got a different message "Could not restore licence from file XXXXX.mjr". The licence file is less than a week old.
Does this mean anything to either of you?
When you run ssh into the pi do you think you are getting a X session?
If you aren't running it from another linux machine you probably are not.
From another linux machine
ssh -X the.ip.address.of.your.pi
-
Interesting.
I tested that before uploading this build. Perhaps a certificate issue on your pi? Try:
sudo c_rehash /etc/ssl/certs
That worked, I succeeded in doing a help menu registration.
-
That worked, I succeeded in doing a help menu registration.
Hey Guys,
I tried this and it didn't work for me (via help menu registration...)
Also,
I may have noticed a couple of bugs with this version, where shoudl I post them? In this thread? Or start a new one?
Thank you for all the kind help!
-
You should probably start a new thread for your registration issues.
Bugs should be posted in the build thread (not this one): http://yabb.jriver.com/interact/index.php?topic=97630.0
-
Always have Enjoyed Media Center 20 on Windows, Thank you to the folks behind this project.
I am new to Linux. Have MC20 working on Pi 2.
In the first forum post I see normal window re-sizing has been tested.
I also see maximize and minimize buttons are not working.
Not sure if I understand. Can this MC20 be displayed in larger window or even a full window? If so, how can I accomplish this?
-
Always have Enjoyed Media Center 20 on Windows, Thank you to the folks behind this project.
I am new to Linux. Have MC20 working on Pi 2.
In the first forum post I see normal window re-sizing has been tested.
I also see maximize and minimize buttons are not working.
Not sure if I understand. Can this MC20 be displayed in larger window or even a full window? If so, how can I accomplish this?
The window can be resized in the same way any window can be resized in windows or linux. Hover over the window boundary and click and drag. It's just the maximize and minimize buttons that don't work.
-
Not sure if I understand. Can this MC20 be displayed in larger window or even a full window? If so, how can I accomplish this?
The window can be resized in the same way any window can be resized in windows or linux. Hover over the window boundary and click and drag. It's just the maximize and minimize buttons that don't work.
May I add as linux newbee struggling with this, you can resize as in (MS)windows;
Just not used the available methods often; (obviously) right click on button on the taskbar and "maximize" or make mediacenter window active (click on it), press ATL + Spacebar and "maximize".
An other difference to get used to is the focus: a child window (sub window) as in >tools>options can get behind the main (mediacenter) window.
-
Thanks for the suggestions. The alt - spacebar - m, brought down a menu with Maximilian as one choice.
Solved my problem.
-
It´s my first Post here! Using MC for HD-Audio since years on Win, on Mac 1 year ,since three weeks on RP. Bought few days ago upgrade Master-License.
Have installed MC20 v.110 on new RP2 as in the Guide advised, no peripherals yet. MC20 appears as a fixed small less inch squared Window on upper left Corner of desktop, no chance to move, maximize or minimize. Within MC20 all works best, too the internal Setup Menues are placed center to the Desktop and can be moved and sized. Should be solved before installing Hifiberry DIGI+, because this brings some trouble with the new kernel too.
How can I get the Mainwindow of MC20 be moved and sized or placed center by Startup?
i.g. Have running MC20 101 Testversion full function on other RP1 and RP2 with Hifiberry DAC (RP1) and DIGI+ (RP2) full bandwidth, handled with JRemote perfectly, with older Kernelversion, but this seems to expire 08. June, so i want have a running licensed system.
-
Have you tried resizing the window by dragging at the edge of the window?
Alternatively have you tried right clicking on the taskbar entry and selecting "maximize"?
-
If you're getting persistent audio dropouts on an RPi 2, some users have found it helpful to change their CPU scaling governor to keep the Pi at maximum CPU frequency. Here's how to do it in a way that will survive reboots.
Type sudo apt-get install cpufrequtils
touch /home/pi/governor.sh
chmod 755 /home/pi/governor.sh
nano /home/pi/governor.sh
Then enter the following text:#!/bin/bash
for n in {0..3}; do cpufreq-set -c $n -g performance; done
Save by pressing CTRL-X, y, and then enter twice.
Now type sudo nano /etc/rc.local
And add the following above the line that reads "exit 0" /home/pi/governor.shSave by pressing CTRL-X, y, and then enter twice.
-
I have installed the Mediacenter on a Raspberry Pi 1 B+ and it runs flawless as an audio server. Today I had to restart the Raspberry and a message popped up "Support for MC will end on 10 June 2015". Does that mean, that only the support ends or will stop also the software ?? If the latter, how to continue?
-
I have installed the Mediacenter on a Raspberry Pi 1 B+ and it runs flawless as an audio server. Today I had to restart the Raspberry and a message popped up "Support for MC will end on 10 June 2015". Does that mean, that only the support ends or will stop also the software ?? If the latter, how to continue?
Early builds of MC for ARM were free "beta" builds that will time out on June 10th; the software will stop working entirely after that date. MC for ARM is now "official," so if you want to keep using MC you will need to update to the current version and install a license. If you already have a JRiver Linux or Master license, you're all set, you'll just need to install a more current MC build and install the license (instructions in the first post).
If you don't have a license yet, you'll need to buy one (either a linux license or a master license).
-
I am new to Raspberry and Linux.
As the instructions here are very clear I managed to set up the latest MC 20 version with the MC 21 Master Key.
What I miss is to get the HiFiberry Dac+ working.
In the meantime I use a Fiio X5, which is a compatible DAC.
-
I use the DAC+ on one of my installations. It's been several months since I set it up, but I'm pretty sure I just followed the instructions here:
https://www.hifiberry.com/guides/configuring-linux-3-18-x/
My recollection is that the driver blacklisting step wasn't entirely necessary, but try it their way anyway. The most important part is probably adding the relevant line to the config.txt, and then fixing your ALSA config.
-
Thank you!
Its all set up now and performs nicely!
-
When I first heard about JRiver on Pi2, I was really excited. I backed up my OSMC image and reimaged my Pi2 with the latest Raspian build. I'm pretty fluent in Linux system management, so I felt like I knew what I was doing. The instructions at the top of the thread are concise and clear, and I had no problem understanding them.
I've been searching for a good solution for a single use case - TV recording and remote playback. I only have OTA TV and I like to record a dozen or so shows each week and watch them as I have time. I use my Media Center PC to record. I used to use WMC, but recently upgraded to JRiver and am very happy with the TV features - schedule management, DNLA playback on my Sony Blu-ray player, etc. It all works great - in fact, with the exception of not having a stream position indicator during pause or FF/RW, DLNA content is more complete than WMC.
However, I have to say, I'm a bit disappointed with the JRiver/Pi experience. When I first heard that JRiver ran on Pi, I was excited because I *thought* I could forego DNLA and go right to the JRiver theater view experience - how much better would that be than simple DLNA?!
Well, after I installed JRiver on my overclocked Pi2, I noticed several show stopper issues:
1) The JRiver screen will only expand to cover 1/8 of my TV screen and it's locked into the upper left corner right below the menu button.
2) There's no theater mode, huh? So I'm supposed to watch my shows on 1/8 of my screen?
3) Doesn't matter anyway - video playback is totally busted - at least on my deployment.
Now, I'm wondering what I'm missing? Are people just using this for music playback? If so, why is everyone talking about hooking the Pi up to their TV and using HDMI sound? I'm sure I'm missing something. Any thoughts?
John
-
Now, I'm wondering what I'm missing? Are people just using this for music playback? If so, why is everyone talking about hooking the Pi up to their TV and using HDMI sound? I'm sure I'm missing something. Any thoughts?
You are not missing anything. Theater View is not supported on any of our Linux versions yet, and on top of that video is not supported on ARM yet.
I'm not sure the Pi2 would be fast enough to play any large variety of videos anyway, not without hooking up some sort of hardware acceleration, which is yet another topic entirely.
-
You are not missing anything. Theater View is not supported on any of our Linux versions yet, and on top of that video is not supported on ARM yet.
I'm not sure the Pi2 would be fast enough to play any large variety of videos anyway, not without hooking up some sort of hardware acceleration, which is yet another topic entirely.
Thanks for the quick reply Hendrik - I understand the terrain now. :) I guess my plan to beautify my TV playback won't work with JRiver yet (unless I'm willing to set up a Windows PC to act as a client next to my TV... possibility, but I'm not ready to go there yet).
Regarding Pi2 hardware being fast enough to play video - well, I was running OSMC on it before I reformatted my Pi2 with Raspian. It was pulling mp4 and wmv movies from a NAS on my network and playing them just fine through the Pi2's HDMI output. I also had it front-ending next-pvr running on my media server. If Kodi can do it, surely JRiver can, right? Heck, my Pi2 wasn't even overclocked when I had OSMC doing it. No flutter, no stutter - picture was beautiful. Just FYI -
http://mymediaexperience.com/raspberry-pi-xbmc-with-raspbmc/
I supply the link not to advertise other server software, but rather to illuminate the fact that the Pi2 does have the horsepower to play both MPEG-2 and H.264 video without overclocking, though overclocking a little can help.
Thanks again - I'll continue to wait anxiously for JRiver to add features to the linux version and happily upgrade my license when it does.
John
-
Hello -
I followed the instructions at the beginning of this thread. I have a couple of problems that I hope someone can help me with. After using the "sudo apt-get install" command it looks like everything installed except for "libg11-mesa-glx" which I'm told is not found. I went ahead with everything else and rebooted. Upon reboot, I have no wifi connection. I notice that now I have a new Wifi program which is good. However I have no wifi connection - it tells me "dhcpcdui not running". There is a tab to access "Wifi Network (dhcpcdui) Settings" but nothing shows up when I select it. I am sure the reason I have no Wifi connection is because I need to set it up.
Any ideas what I did wrong?
Thanks!
-
Hello -
I followed the instructions at the beginning of this thread. I have a couple of problems that I hope someone can help me with. After using the "sudo apt-get install" command it looks like everything installed except for "libg11-mesa-glx" which I'm told is not found.
Could you post the exact error message you received? Did you make sure to run "sudo apt-get update && sudo apt-get dist-upgrade" first? What happens if you try to install and run mediacenter anyway?
I went ahead with everything else and rebooted. Upon reboot, I have no wifi connection. I notice that now I have a new Wifi program which is good.
Nothing in the instructions should have affected your wi-fi connection, unless you were running a much older version of NOOBS and had never upgraded it.
Did you have wi-fi working before? What does a "new wifi program" mean? Did you start from a fresh NOOBS Raspbian install or an existing one?
-
Could you post the exact error message you received? Did you make sure to run "sudo apt-get update && sudo apt-get dist-upgrade" first? What happens if you try to install and run mediacenter anyway?
There is now an icon in the upper right hand corner that displays 2 monitors - typical icon for network connection. When I hover the cursor over it, it displays "dhcpcd not running".
I can right click on it to get a window of choices. One is "Wifi Network (dhcpcdui) Settings". I assume this is where I can put in my wifi password. But when I click on it, nothing happens. I did run everything according to your instructions and rebooted after the nano sequence.
Nothing in the instructions should have affected your wi-fi connection, unless you were running a much older version of NOOBS and had never upgraded it.
I should have the latest version as I just purchased the raspberry pi with Noobs and Raspian 2 days ago from Canakit via Amazon.
Did you have wi-fi working before? What does a "new wifi program" mean? Did you start from a fresh NOOBS Raspbian install or an existing one?
Yes I did have wifi working before. I used an existing install that I did earlier in the day.
Why did it not accept the install of libg11-mesa-glx? I am sure I typed it in correctly.
Thanks for your help!
-
There is now an icon in the upper right hand corner that displays 2 monitors - typical icon for network connection. When I hover the cursor over it, it displays "dhcpcd not running".
I can right click on it to get a window of choices. One is "Wifi Network (dhcpcdui) Settings". I assume this is where I can put in my wifi password. But when I click on it, nothing happens. I did run everything according to your instructions and rebooted after the nano sequence.I should have the latest version as I just purchased the raspberry pi with Noobs and Raspian 2 days ago from Canakit via Amazon.Yes I did have wifi working before. I used an existing install that I did earlier in the day.
The way Pi's manage Wi-Fi was changed in May; it's possible the card you got was old stock. Several folks had issues when transitioning from the old system to the new system. The wi-fi issue is an OS issue caused by updating the OS, and not an MC issue.
I've never had the issue you're describing, but if try googling you'll see lots of folks with your exact error after doing an upgrade. If you're not comfortable troubleshooting, you could try reinstalling with a fresh NOOBS image downloaded from their website. That should be up to date already with the wifi properly configured.
Why did it not accept the install of libg11-mesa-glx? I am sure I typed it in correctly.
I can't tell you the answer as it installs fine here. It might help if you posted the exact error message you got when trying to install it (as suggested above).
Also, did you try installing and running mediacenter without it as I suggested? It may not be necessary anymore. MC continuously evolves and requires fewer dependencies than it did when this guide was written. This is not the most current version of this guide, the new version is here: http://yabb.jriver.com/interact/index.php?topic=99370.0
-
I did go ahead and installed mediacenter using the wired ethernet connection. All seemed to progress nicely, except when I clicked on MC20 all I got was a white window.
I will go ahead and update my Noobs and start from scratch. Thanks for the link to the most current configuration. I will try that.
-
I did go ahead and installed mediacenter using the wired ethernet connection. All seemed to progress nicely, except when I clicked on MC20 all I got was a white window.
If you get the white window it probably means that you skipped (or didn't successfully complete) the step where you add the following lines to your config.txt framebuffer_depth=32
framebuffer_ignore_alpha=1
Without those lines in your config.txt, you'll just get a white screen when MC launches.
-
1) The JRiver screen will only expand to cover 1/8 of my TV screen and it's locked into the upper left corner right below the menu button.
Is there a solution to this problem? I'm not trying to playback video but it'll be easier to interact with JRiver on the RPI if you could expand it to full screen.
Thank you!
-
Is there a solution to this problem? I'm not trying to playback video but it'll be easier to interact with JRiver on the RPI if you could expand it to full screen.
Thank you!
Did you try right-clicking on the MC taskbar entry and selecting "maximize"? That works here. You can also hold down ALT and drag at the corner of the window to resize it.
It's only the maximize and minimize buttons on the MC window itself that don't work.
-
Did you try right-clicking on the MC taskbar entry and selecting "maximize"? That works here. You can also hold down ALT and drag at the corner of the window to resize it.
It's only the maximize and minimize buttons on the MC window itself that don't work.
That's interesting. When did they last work? I'm pretty certain that they did at one time.
-
That's interesting. When did they last work? I'm pretty certain that they did at one time.
They've never actually worked for me on ARM. When I first wrote this quick start guide, I made a list of things that were working and things that weren't in the top post. I've edited the list since to keep up with development, but the maximize and minimize buttons have been on the "not working" list since my first draft in February.
-
Did you try right-clicking on the MC taskbar entry and selecting "maximize"? That works here. You can also hold down ALT and drag at the corner of the window to resize it.
It's only the maximize and minimize buttons on the MC window itself that don't work.
Thanks,
I tried both methods now and it doesn't work for me... right clicking the task bar entry and choosing minimise works - but not Maximise or dragging with the mouse...
Perhaps it s local setting on my system? I'm using VNC to access the Pi - mine is headless and keyboardless...
Thanks!
-
Thanks,
I tried both methods now and it doesn't work for me... right clicking the task bar entry and choosing minimise works - but not Maximise or dragging with the mouse...
Perhaps it s local setting on my system? I'm using VNC to access the Pi - mine is headless and keyboardless...
Thanks!
Those both work fine for me with a headless Pi accessed through VNC, so I'm not sure what the difference could be. Assuming you followed my guide, our configurations should be identical.
What VNC client are you using (I'm not sure that should make a difference, but that's the only thing I can think)?
-
Those both work fine for me with a headless Pi accessed through VNC, so I'm not sure what the difference could be. Assuming you followed my guide, our configurations should be identical.
What VNC client are you using (I'm not sure that should make a difference, but that's the only thing I can think)?
Thanks, I'm using VNC viewer on mac and iPhone...
-
Thanks, I'm using VNC viewer on mac and iPhone...
I don't have any idevices so I can't test/replicate. I just tested using bvnc on android and it worked fine. It also works at home with tigerVNC and tightVNC. I can't imagine the VNC viewer is really the issue though if minimize works for you.
I suspect you've done something different in your configuration than I have, but it would be hard to know what. What MC build are you on?
-
Thanks,
I'm on the latest MC20 RPI version.
I seem to recall that in the set up process there is a file we dill with some tex that looks like resolution? Perhaps something went wrong there?
It's not a huge problem.
-
If you get the white window it probably means that you skipped (or didn't successfully complete) the step where you add the following lines to your config.txt framebuffer_depth=32
framebuffer_ignore_alpha=1
Without those lines in your config.txt, you'll just get a white screen when MC launches.
Hi,
I'm having difficulty getting anything but the white window, and I've checked the config.txt file, which contains the two lines above. I am using the latest build on a Pi 2 Model B, with the pre-loaded Noob OS. The "status bar" on the desktop indicates MC is running,
Is there anything else I can check? I feel like I'm really close.
-
Can you please post your entire config.txt in code tags?
-
Can you please post your entire config.txt in code tags?
Here it is:
# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
# NOOBS Auto-generated Settings:
hdmi_force_hotplug=1
config_hdmi_boost=4
overscan_left=24
overscan_right=24
overscan_top=16
overscan_bottom=16
disable_overscan=0
framebuffer_depth=32
framebuffer_ignore_alpha=1
-
That's odd, that should work. How do you have your Pi hooked up to a display? What kind of display is it?
-
That's odd, that should work. How do you have your Pi hooked up to a display? What kind of display is it?
It's hooked up via HDMI to a Samsung TV which I've been using as a monitor. I'm currently using a windows box on this TV for MC and other streaming stuff. All other graphics appear to work fine on the pi, including the viewing of this forum and some youtube videos I tried out.
Long ago in a faraway land, I worked with UNIX. I'm starting all over again.
Anyway, is there anything else that may be causing this? I do appreciate your time.
-
The only thing I've ever seen cause that all white window on a pi is a lack of 32-bit colordepth, which those two settings should cure. I'm not sure if trying with a different display might help (it shouldn't matter)
The only difference between our config.txt files is that I have overscan disabled, and I specify the size of my framebuffer, but neither of those should meaningfully affect how the MC window is rendered.
If you run mediacenter from the terminal does it throw any errors? I can tell you that if you VNC into the Pi (i.e. operate it headlessly) the window will almost certainly render properly, but that's not much help if you wanted to control it directly.
I'm sorry I'm not more help, but I can't reproduce this here (without removing those lines from my config.txt) so I'm not sure how to proceed. I assume you rebooted after changing your config.txt, right?
Bob is the member of the JRiver staff with the most expertise in this area, but he's on vacation for the time being.
If you're impatient, you might try reinstalling using a freshly downloaded NOOBS image. If you do so, make sure to follow the updated guide on the MC 21 forum. I can confirm that I went back and followed the exact steps listed a few weeks ago and everything worked as expected.
-
Thanks for looking. There are probably too many variables at play at the moment....new Pi, HDMI, versions, etc. I've rebooted several times. I'll futz around with it and re-post if/when I figure this out.
-
Thanks guys works awesome ;D
Pierre
-
Still no luck, so I'm back...
In all other respects, the Pi is acting as it should. All graphics work fine, I can access videos from YouTube etc. Browser acts like a browser should. I've tried all the usual stuff, including running through all the installation and configuration commands on this thread. I've copied and pasted them, to ensure I've made no typos. I've tried both MC20 and MC21. And yet I continue to get the same results. When I fire up MC, a window pops up that says "Media Center 2X". The window size is something like a quarter of the screen size. After a few seconds of the "busy" spinning wheel, it just sits there with a white screen. I've resized the screen and nothing happens. I move the cursor (the curser, that's me) around and it doesn't act as if there's a link anywhere. I'm completely mystified.
Is there anything obvious I'm missing?
Thanks
-
The only thing I can think of is that Raspbian just ported over to Jessie a few weeks ago and maybe you're running Jessie instead of Wheezy? I haven't moved my Pi's over yet so there may be as yet undiagnosed complciations with the new debian stable? Do you know if you're on Jessie or Wheezy? If not type
cat /etc/apt/sources.list and post the results.
-
The only thing I can think of is that Raspbian just ported over to Jessie a few weeks ago and maybe you're running Jessie instead of Wheezy? I haven't moved my Pi's over yet so there may be as yet undiagnosed complciations with the new debian stable? Do you know if you're on Jessie or Wheezy? If not type cat /etc/apt/sources.list and post the results.
here's what I get:
pi@raspberrypi ~ $ cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://mirror.ox.ac.uk/sites/archive.raspbian.org/archive/raspbian/ wheezy main contrib non-free rpi
pi@raspberrypi ~ $
By the way, I recently changed monitors, and no difference. I still get the white box with the Media Center label but no contents. Weird
-
Ok you're on wheezy, so everything should be working. I'm honestly stumped. Could you post over in the build thread for ARM so Bob can see? He's the JRiver "Linux Guy," and he may have some thoughts. Point him to the back and forth here so he can see what we've already ruled out.
-
Progress!
I figured something somewhere in the install might have gotten hosed, so I started from scratch. I bought a new SD card, downloaded NOOBs, configured everything all over again, and it worked. The graphics look like crap, but I have a window in which I can see MC. So thanks....Now I have to figure out the resolution or font, get the network server working etc., but it's running.
-
Progress!
I figured something somewhere in the install might have gotten hosed, so I started from scratch. I bought a new SD card, downloaded NOOBs, configured everything all over again, and it worked. The graphics look like crap, but I have a window in which I can see MC. So thanks....Now I have to figure out the resolution or font, get the network server working etc., but it's running.
Aces! Glad to hear it.
-
One final question. For some reason when MC opens in the window, I can't resize the window. I can't drag it, maximize it, or in any way change the size. No other application behaves this way. What am I missing?
Thanks a ton for your help so far. Almost there....
-
One final question. For some reason when MC opens in the window, I can't resize the window. I can't drag it, maximize it, or in any way change the size. No other application behaves this way. What am I missing?
Thanks a ton for your help so far. Almost there....
Do you have the latest buidl for ARM? Bob recently fixed the maximize buttons which didn't previously work. Resizing by dragging has always been a little flaky on Linux, but right-clicking on the menu bar entry, has always allowed me to maximize it.
-
Latest 20 or latest 21? Thanks.
-
Latest 21. The maximize and minimize buttons never worked in MC 20, but as I said, right clicking on the menu bar entry should allow you to maximize or minimize.
-
Working like a million bucks. Thanks.
-
I can’t install because when I enter »sudo get-apt update« (after the reboot) I get after some time this:
W: Duplicate sources.list entry http://dist.jriver.com/latest/mediacenter/ wheezy/main armhf Packages (/var/lib/apt/lists/dist.jriver.com_latest_mediacenter_dists_wheezy_main_binary-armhf_Packages)
W: Probieren Sie »apt-get update«, um diese Probleme zu korrigieren.
What does it mean? (I’m quote new to raspberry and don’t understand such messages...)
-
I can’t install because when I enter »sudo get-apt update« (after the reboot) I get after some time this:
W: Duplicate sources.list entry http://dist.jriver.com/latest/mediacenter/ wheezy/main armhf Packages (/var/lib/apt/lists/dist.jriver.com_latest_mediacenter_dists_wheezy_main_binary-armhf_Packages)
W: Probieren Sie »apt-get update«, um diese Probleme zu korrigieren.
What does it mean? (I’m quote new to raspberry and don’t understand such messages...)
I can't read German (I'm assuming that's German?), so I'm not sure what the second line means, but my guess would be that you might have run a command twice (or run one imprefectly) which added the repo to the sources list twice causing the error. Can you post the contents of the following file: /etc/apt/sources.list.d/mediacenter20.list
-
A quick translate through Google...
W: Duplicate sources.list entry http://dist.jriver.com/latest/mediacenter/ wheezy / main armhf Packages (/var/lib/apt/lists/dist.jriver.com_latest_mediacenter_dists_wheezy_main_binary-armhf_Packages)
W: Try 'apt-get update "to correct these problems.
But yeah, you're on the right track about the duplicate source.
-
I try to follow these instruction, but without success. This command fails: sudo bash isx11.sh. I get the error message "401 Not Authorized. / Authentifizierung mit Benutzername/Passwort fehlgeschlagen." (Authentification with user name and password failed.) And that’s the end. Is there an alternative way to install this?
-
I try to follow these instruction, but without success. This command fails: sudo bash isx11.sh. I get the error message "401 Not Authorized. / Authentifizierung mit Benutzername/Passwort fehlgeschlagen." (Authentification with user name and password failed.) And that’s the end. Is there an alternative way to install this?
I'm a little perplexed as that command isn't in the instructions at all. Why are you running the command "sudo bash isx11.sh"? Is that from Hilton's alternate headless access instructions? Work on getting the regular install done before meddling with that. This is also the old thread for MC20; there are more up to date instructions in the MC21 version of this thread.
https://yabb.jriver.com/interact/index.php?topic=99370.0
If it's an rdp issue, you'll need to wait for Hilton to chime in as I don't use rdp. If you're having trouble, VNC is much easier to setup (use the directions in the linked thread).
-
Hello all.
My laptop died and I'm looking at a replacement for my JRiver server. I have a spare pi2 I could try and when I saw this thread I was immediately interested.
Just wondering for those that have done the pi2 build how it compares speed wise to running on a dedicated laptop/desktop build?
-
Hello all.
My laptop died and I'm looking at a replacement for my JRiver server. I have a spare pi2 I could try and when I saw this thread I was immediately interested.
Just wondering for those that have done the pi2 build how it compares speed wise to running on a dedicated laptop/desktop build?
It's much slower, but depending on your application it may be fine. A good rule of thumb is that if you're planning on interacting with the GUI directly instead of with a remote it will be a bit frustrating. For a server I would expect very poor performance as the CPU would choke on transcoding, and the Pi has no fast I/O options. I don't think the arm builds support video yet either. It might work for an audio only server with a modest-sized library, but the pi works best as a headless endpoint to turn speakers into "smart" speakers.
-
It's much slower, but depending on your application it may be fine. A good rule of thumb is that if you're planning on interacting with the GUI directly instead of with a remote it will be a bit frustrating. For a server I would expect very poor performance as the CPU would choke on transcoding, and the Pi has no fast I/O options. I don't think the arm builds support video yet either. It might work for an audio only server with a modest-sized library, but the pi works best as a headless endpoint to turn speakers into "smart" speakers.
Thanks for the honest feedback. I have about 2tb of music on this server. I would only be using it as a server/playback client (one machine) and I use tablets for GUI.
-
Give it a try and see; if you plan on mostly using remotes and don't have any/many clients it may be satisfactory. I haven't really tried using mine as servers except for testing the functionality in a basic way so I'd be curious how well that works.