More > JRiver Media Center 26 for Linux

Quick Start Guide for Installing JRiver Mediacenter 26 on a Raspberry Pi

<< < (3/8) > >>

gpongrac:
Happy to report that I was successful in getting MC 26.0.29 running on the current raspbian buster distribution (2020-02-13) on a Pi 4.

This is running headless and is replacing MC running on an old Mac-mini that died recently.  Getting headless to work correctly required only that some HDMI parameters in the raspbian boot/config.txt file be configured correctly.  These parameters trick the Pi into thinking that an HDMI display is attached even though I don't have one.  Once this is done the VNC server that comes with the distribution will work correctly along with MC.

The relevant /boot/config.txt parameters I used are:


--- Code: ---# force HDMI output mode (rather than DVI)
hdmi_drive=2

# make it appear that an HDMI display is attached.  Needed for headless
hdmi_force_hotplug=1

# set HDMI output group to be DMT
hdmi_group=2

# set HDMI output format to be 1280x1024 60Hz
#hdmi_mode=35

# set HDMI to 1600x1200 60hz
hdmi_mode=51


--- End code ---

I went with 1600x1200 display size, but mode 35 (1280x1024) also worked.  Note that framebuffer_width and framebuffer_height are not used here.  Mode values for other resolutions can be found here: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

I configured the pi to run VNC and to boot into graphical mode and auto login the "pi" user via raspi-config.  Other than that it was a plain-vanilla install and configuration of the Pi software.

Migration of my music files from the Mac HFS+ filesystem to the Raspbian's ext4 filesystem was done by installing an Oracle openbox VM on one of my other Macs, installing a Raspbian x86 distribution into that VM, setting up openbox file-sharing between the hosted VM and the Mac host, and then copying files over using rsync on the Raspbian machine.

ttirvnet:
Thanks for sharing @gpongrac.

I'm getting my own RPi 4 soon, so I'm happy to see you already got it working with MC and that it is working in headless mode as well.

Where are you sending the audio from MC, to a USB DAC perhaps or out via the HMDI? I'd like to know more about your setup. In my case I'll be sending the audio to a USB DAC.

gpongrac:
I'm using the PI4 as a uPnP server and sending the audio files via ethernet->router->wifi to a Digione signature streamer, which outputs a high quality SPIDF signal to my Metrum DAC.  The sound quality is excellent this way, better than any USB setup I've tried.

Awesome Donkey:
This seems to be a good place to post Pi news.

There's a new 8GB model of the Raspberry Pi 4 Model B: https://www.raspberrypi.org/blog/8gb-raspberry-pi-4-on-sale-now-at-75/

Also there's now a 64-bit build (which is an early beta right now) of Raspbian, which has been renamed to Raspberry Pi OS.

So that begs the question, ARM64 build of MC in the future, perhaps when the 64-bit OS matures a bit more? :P

bob:

--- Quote from: Awesome Donkey on May 28, 2020, 07:57:50 am ---This seems to be a good place to post Pi news.

There's a new 8GB model of the Raspberry Pi 4 Model B: https://www.raspberrypi.org/blog/8gb-raspberry-pi-4-on-sale-now-at-75/

Also there's now a 64-bit build (which is an early beta right now) of Raspbian, which has been renamed to Raspberry Pi OS.

So that begs the question, ARM64 build of MC in the future, perhaps when the 64-bit OS matures a bit more? :P

--- End quote ---
64 bit would be likely, we have an in-house one for a different ARM platform that seems good.
We will need to see release versions of the OS and some adoption of it before it would be worth the extra overhead of producing and maintaining another build.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version