More > JRiver Media Center 23 for Linux
Quick Start Guide for Installing JRiver Mediacenter 23 ARM on a Raspberry Pi
mwillems:
--- Quote from: Zhillsguy on February 02, 2018, 02:30:19 pm ---Thanks for the detailed explanation. I've always been curious about thumbnail generation. You are spot on about the Pi getting overwhelmed easily, it doesn't take much of a bump in the road to make it skip or buffer, but if set up correctly it's quite usable.
I've been looking at other SBC's, and ended up ordering an Odroid C2. More powerful but not as much community support. There are enough available OS images to make it palatable to use with MC.
--- End quote ---
Do you have it working well with the C2? I tried running MC on an older ODROID C1 and an ODROID U3, and there were basic roadblocks because their video outputs didn't support adequate color space so MC just appeared as a solid black or white square; attempts to set the video output to a higher color space either didn't work or broke X11 (because the firmware didn't support it). There were also dozens of other issues with the two SoC's (certain USB DACs that worked in mainline didn't work with odroid, no video hardware acceleration for most programs, etc.) that were never resolved before ODROID EOLed those boards, which led me to shelve ODROID indefinitely. But if everything works great on the C2 that would be good news and I might give them another chance.
Zhillsguy:
The C2 won't be here until next week, I will advise after tinkering.
mp48:
thank you mwillems for the detailed explanations. It makes it clearer for me. Actually I have several crashes of MC per day always with the message "java.net connect exception: connection refused". I will now get an adapter to get the monitor connected to the raspi in order to change the thumbnail issue. I hope that will solve the problem.
JohnWalker:
My previously registered and working copy of mediacenter23 on Raspbian no longer saves my registration details - it accepts the registration code at program start-up, but then forgets the registration details when it is re-started. I have a Master licence which I purchased in Nov 2017 as an upgrade from MC22. The drive that all software is installed on is accepting writes OK (it's not the fault where Raspberry Pi drives go permanently read-only). Mediacenter23 is installed in /usr/bin, which I assume is correct. I've used up 6 of my 20 annual restores so far trying different ways to fix this problem.
Awesome Donkey:
Make sure you're using the latest 23.0.100 build.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version