More > JRiver Media Center 21 for Linux

New RaspberryPi 3 - what do you think?

<< < (3/6) > >>

mwillems:

--- Quote from: skifastbadly on April 23, 2016, 06:36:44 pm ---Newbluesman:  I am impressed by your results, I've had nothing but headaches.

Using the Pi as a music server or renderer has great appeal to me but I have not succeeded.  About six months ago, I successfully loaded Media Center 21 onto the Pi 2 and thought I was home free.  But it wouldn't play without dropouts, which kind of ruins the whole "if perfect audio is your goal" aspect of MC.

Here's a bit about my environment:  my wireless router is  Netgear Nighthawk X6, with PLENTY of speed.  On the network I have two PCs running MC, and a Yamaha RX-A2020 with DLNA capability.  I can play from either PC to the other with no dropouts.  I can play from either  PC to the Yamaha with no dropouts.  I can play from either PC to my HTC One phone with Gizmo with no dropouts.   I can play from either PC to my frigging Kindle Fire with no dropouts.  But as soon as the Pi is entered into the equation, I get drop outs.  In each case, by the way, I'm using FLAC files.

I tried overclocking, no help.   So after awhile, I figured it just wasn't going to work.  It seems the horsepower just isn't there for whatever reasons.
Well a few days back I noticed that the Pi 3 was out, and it looked like a real upgrade in terms of horsepower over the 2 so I figured it was worth another forty bucks to give that a shot.

The first thing I learned, which other people have learned, is that it's not as simple as taking the SD out of the 2 and putting it into the 3.  It won't boot.  So I downloaded the latest raspbian image (2016-03-18-raspian-jessie), put it on a new SD, and attempted to go through the installation process based on the excellent directions on how to load MC onto the Pi.  There appear to be a number of changes that are problematic.

The first thing I tried to do was to follow the same sequence as laid out on this site for the Pi 2.  Once I made the changes to the config text: 
framebuffer_depth=32
framebuffer_ignore_alpha=1
When I rebooted, the video never came back.  I mean the boot screen appeared, the status scrolled, but then it would disappear.  Ok, there's maybe something in the graphics that's different. 

Then I figured I'd at least try to load MC to see what would happen. It didn't finish.  I got the following:

Input/Output Eror
dbkg: error processing package shared mime-info (--unpack)
subprocess installed post-installation script
returned error exit status 1

dbks: error:  unable to synch new file
'/var/lib/dpkg/status-new: input/output error E: subprocess /usr/bin/dpkg returned and error code 2

when I rebooted, I got the same as before, the status scrolled by then blank screen.

I have put hours into this with no luck.  What's the trick?

--- End quote ---

Did you download the raspbian image from the raspberry pi foundation?  The NOOBS installation?  Just last week, I tested the directions in the sticky thread with a NOOBS image and a raspberry pi 3 and it all worked perfectly.  It's odd you're seeing errors.

skifastbadly:
You must get sick of idiots like me.  For some reason I got it into my head that I could start with the raspbian image download instead of the NOOB.  I started over with the NOOB download, everything went swimmingly, and I'm now listening to the Pi 3 through the Hifiberry SPDIF.  But I just experienced a dropout. 

Half way there, I guess.

Thanks.

mwillems:

--- Quote from: skifastbadly on April 24, 2016, 03:27:16 pm ---You must get sick of idiots like me.  For some reason I got it into my head that I could start with the raspbian image download instead of the NOOB.  I started over with the NOOB download, everything went swimmingly, and I'm now listening to the Pi 3 through the Hifiberry SPDIF.  But I just experienced a dropout. 

Half way there, I guess.

Thanks.

--- End quote ---

Half is better than nothing!  Glad you made forward progress  ;D

skifastbadly:
Thanks.  I hit one more snag if you don't mind.

Since the Pi 3 is new I was running the trial license.   Once I got everything working, I tried loading the license.  I have a Master license.  I learned earlier that the way to do this on the Pi is to use the instructions on your sticky thread, providing the .mjr file name.  So that's what I did.  The system then stated that the license was renewed.  However, when I started MC up again, I got a window stating that my trial had expired.  Any ideas what I've screwed up this time?

JimH:
The .mjr file is an Install Key and it is only good for 14 days.  Use your Registration Code to do a Restore.  You'll get a new Install Key by e-mail.

http://wiki.jriver.com/index.php/Restoring_a_License

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version