|
Post by MartinT on Sept 14, 2014 19:58:17 GMT
Ooh, you got the DAC+. Very nice, I will be interested in how you find it. The Digi+ continues to impress me with its sound quality.
|
|
|
Post by Pinch on Sept 14, 2014 20:49:44 GMT
Yup! I think I'll probably pick up a Digi+ also, but for now I'm interested to see how well the Pi can work as standalone player + JRiver renderer, that I can deploy either in the kitchen or bedroom (a much more convenient alternative to streaming to iPad, which I've been doing in these rooms up to now). It works pretty nicely so far! I've not yet given it a proper work-out on the main system, but that's on the to-do list.
|
|
|
Post by Pinch on Dec 13, 2014 13:18:57 GMT
Pi²
|
|
|
Post by MartinT on Dec 13, 2014 14:50:07 GMT
So how does the standalone RPi with DAC+ compare with the Digi+ version running into your DAC?
|
|
|
Post by Pinch on Dec 13, 2014 14:57:13 GMT
Don't know yet - I've only assembled it, not installed the OS, so no listening yet. I'm working today, but the bits arrived this morning and I couldn't resist taking 10 mins out just to put it together I plan to get the OS installed this evening, and also to update the first Pi to 1.5, and then to do some listening.
|
|
|
Post by pinkie on Dec 13, 2014 17:06:03 GMT
2 Pi's!! Yeah, I'm already thinking that way too.
|
|
|
Post by pinkie on Dec 13, 2014 17:12:18 GMT
Ooh, you got the DAC+. Very nice, I will be interested in how you find it. The Digi+ continues to impress me with its sound quality. I remember now, the "thing" that made me go looking for the Pi thread on TAS was somebody using the sabre dac with it. Has anyone compared these dacs? Are there any others for the Pi?
|
|
|
Post by MartinT on Dec 13, 2014 19:10:13 GMT
With the Digi+, it can be used with virtually any DAC.
|
|
|
Post by Pinch on Dec 13, 2014 19:45:51 GMT
Well that took a little longer than expected. Just installed Volumio 1.5 on the new Pi, applied the little tweaks and whatnot that I documented above - overclocking and disabling cpu throttling - installed the wifi and Digi+, and updated the DLNA renderer and got it talking to JRiver; a couple of hours all in all.
But now there's music playing and initial impressions are good - currently cranking this:
|
|
|
Post by pinkie on Dec 26, 2014 9:13:08 GMT
Tom. You are da man! Like you I much prefer the user interface of JRiver (still have issues about it controlling the audio on the PC, although as a DNLA device (it can be configured as server, controller and renderer or perm any 1,2,or 3 from 3), maybe its not such an issue I failed to get it to work first time because my trial JRiver is on the laptop, and I was controlling volumio from the desktop. Volumio needs to be in a browser on the JRiver device (ie my laptop) for it to find it. Thereafter it is superb. My android phone can browse the whole library and JRiver sorts out where it is. It will play the files without the need to configure a NAS on volumio, and selects its own direct library in preference for any duplicates. I'll go back to my own blog to repeat this, and ask a few questions Brilliant! Thanks for blazing the trail
|
|
|
Post by Pinch on Jan 10, 2015 19:55:41 GMT
Just saw this^ post - good stuff! Pleased the info here helped My next plan for the Pi is to have it playing video as well as music, so it can serve as all-in-one media player in the lounge, feeding both the big screen and the second system via the Digi+. At the moment I use an old laptop for this, but it's a noisy bastard, and has a tendency to overheat, so it would be great to replace it with the Pi. I want to experiment with both raspbmc and with raspbian running the new JRiver for Linux. This will probably be beyond the initial scope of this blog, but in any case I'll update once I make a start.
|
|
|
Post by Pinch on Feb 18, 2015 12:08:33 GMT
Volumio needs to be in a browser on the JRiver device (ie my laptop) for it to find it. Thereafter it is superb. This comment from Pinky intrigued me, and I subsequently noticed that the Pis had a tendency to vanish from JRiver's zone list, but would re-emerge if I opened the device page in web browser. I'm not sure what's responsible for this behaviour, but either way it's a little annoying, since it means control through JRemote is not as seamless as it should be, since the Pis will often need to be woken up and re-registered by JRiver before I can stream anything to them. But anyway, it's fixed now. Last week I was reconifguring the router's device settings - the settings it applies to devices on the network - since the port-forward that I'd set up on my main machine, and which allows me to stream from the library when I'm outside the network, would need to be updated whenever the machine was periodically assigned a new network IP. Since this was a little tiresome, I set the router to always use the same IP for this device, and - on a whim - did the same for the Pi's also, and since then (about a week now) they haven't vanished from JRiver once
|
|
|
Post by MartinT on Feb 18, 2015 12:38:18 GMT
You can use a service like DynDNS to retain a consistent external address when your router uses NAT to assign internal dynamic IPs.
|
|
|
Post by Pinch on Feb 18, 2015 12:52:12 GMT
Ah, you'll have to forgive my ignorance here Martin - would this be preferable to simply telling the router to keep the same IP for the relevant devices?
|
|
|
Post by MartinT on Feb 18, 2015 13:20:13 GMT
It's a way of accessing devices from outside of your network without having to reconfigure every time the device IP changes.
DynDNS
NoIP (I use this one, it's free)
|
|