More > JRiver Media Center 21 for Linux
Quick start guide for installing JRiver Mediacenter 21 ARM for Raspberry Pi
PrinterPrinter:
--- Quote from: mwillems on March 04, 2016, 08:03:37 am ---I don't have a Pi running the old version of Raspbian right now, so I can't give you a step by step, but it would probably be harmless to remove the collabora repo entirely. If I recall correctly there is a file named collabora.list in the directory /etc/apt/sources.list.d. You can try removing that file.
Alternatively, you can run the two halves of the update command separately and it should work fine (meaning first run sudo apt-get update and then on the next line run sudo apt-get dist-upgrade). The reason the update doesn't happen is that the && operator stops if there was an error in the first half of the command, even if it's not necessarily a "blocking" error. So try running sudo apt-get dist-upgrade on it's own line, which should work fine as a work around.
--- End quote ---
Thank you!
Deleting that file did the trick ;)
Really digging the new 'no buffering' mode - stops the stuttering I'd get when playing new files - thank you!
jmone:
@mwillems - thanks! Access is not a problem but it will be interesting to see what they have done SW wise. Here is a quote from Axiom:
--- Quote ---Hackable and Up-gradable were design features we wanted to have. We even nicknamed the access door the "tinker door". It is not running Volumio but the AxiomAir platform was written by Michelangelo. He will be showing up a lot here starting next week to answer questions and get ideas for changes we may want to implement.
--- End quote ---
From what I've read over on the Volumio Forum the "AxiomAir" platform is based on Volumio 2 but is customised (like MC does for 3rd parties I guess). I do like that this thing comes with the ability to play to multi rooms in sync and they also plan to just release a speakerless version (eg just the Pi/DAC) to run into your own AV equipment. They have also said the code will be on Git Hub as Open Source so when it appears I post a link. The other option if I can not run MC side by side would be to just have a second SD Card to boot from.
gulp:
thanks to all of you, it was my fault, I had a false letter in my code, now it works!
Slim_Fishguttz:
Hello -
thanks for the clear and comprehensive recipe for MC on the Pi.
most of my music files are ripped from cds, but 20% are hd downloads from hdtracks, nativedsd, etc. the formats go from 192 pcm to quad dsd.
my output train is ifi usb power --> ifi dac2 --> schiit lyr 2 --> oppo pm-3. the dac can process everything from 384 pcm thru quad dsd.
when a win 10 or osx machine pulls this train everything is as it should be. the dac is recognized as "ifi (by amr) hd usb audio asio". i bitstream with the dsd option. everything is good, better than good.
when a pi 3 is the server, the output device is seen as an asio device (actually several asio devices) as you detail in your documentation. although several asio devices are 'detected' only two actually output sound, the same quality of sound in each. the problem is that mc downsamples everything to 1411. in other words, nothing is any better than a cd rip.
bummer.
my plan was to attach pis to the various music systems scattered thru out the house. i am rethinking this.
do you know if i will have the same problem on different linux forks and/or if i use a linux desktop?
reading the messages in this forum, it seems like people are just happy to get mc running on pi and that i am the first to test hd files. that and the fact that the newest messages are months old, makes me think that mc on a pi is the weak sister.
what are your plans for the future?
thanks for response.
DJLegba:
--- Quote from: Slim_Fishguttz on April 05, 2016, 03:41:04 pm ---my plan was to attach pis to the various music systems scattered thru out the house. i am rethinking this.
--- End quote ---
I can't comment on your pi experience but if you have DACs scattered throughout the house you may want to look at Chromecast Audio. It has a mini-toslink output which means you can feed your DACs 96/24. If you don't have DACs all over the place you were probably planning on using the DAC in the pi (if there is one, I have no clue), in which case you'll probably be happy with the DAC built into the CCA - and you still get 96/24. I think the CCA is cheaper than the Raspberry pi (not sure though).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version