More > JRiver Media Center 21 for Linux
Quick start guide for installing JRiver Mediacenter 21 ARM for Raspberry Pi
mwillems:
--- 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.
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.
--- End quote ---
You're definitely not the first to test hd files, the Pi will happily output up to 192KHz PCM with the right DAC. I haven't personally tested higher than 192KHz myself, but other users have reported higher sample rate PCM working for them with the right devices. I don't have an Ifi, so I can't test your hardware specifically, but I'd be willing to bet you may have a configuration problem, not a hardware problem with respect to the PCM sample rate issue.
That said, DSD is potentially a problem on Linux in general (not just with MC). Native DSD support on Linux is relatively new and not all methods of DSD output are supported by the Linux kernel. I don't personally use DSD (have no files or devices to test), so I can't provide a firm statement of how well MC for Linux works with DSD, but I seem to recall reading that DoP is working?
To summarize: hi res files (other than DSD) are well supported on MC for Linux including with the Pi. If you can't get the files to output in their native format, it's likely a configuration issue. DSD files (depending on the device, output format, and recency of the kernel) are not as well supported, but some configurations may (or may not) work.
My advice to you would be to open up a separate thread with a descriptive title so someone is likely to see it; this is primarily a support thread for installation issues so is not high traffic (i.e. you are unlikely to find anyone with Linux DSD experience in this thread). If it's not clear from the above, I'm just a user like you, not a dev, so they may weigh in at some point as well.
Slim_Fishguttz:
--- Quote from: DJLegba on April 05, 2016, 07:12:13 pm ---I can't comment on your pi experience but if you have DACs scattered throughout the house
--- End quote ---
Yeah, I do have DACs scattered thru out the house, iFi, Schiit, Marantz. I like to experiment with gadgets. BTW - HiFiBerry and IQaudio make acceptable, for the money ($35-$50), DAC daughter cards for the Pi. I have Pis with each. I totally mistrust Google/Chrome, so I don't want to get more involved in their eco-system.
Still, thanks for the input.
Slim_Fishguttz:
--- Quote from: mwillems on April 05, 2016, 08:44:47 pm ---To summarize: hi res files (other than DSD) are well supported on MC for Linux including with the Pi. If you can't get the files to output in their native format, it's likely a configuration issue. DSD files (depending on the device, output format, and recency of the kernel) are not as well supported, but some configurations may (or may not) work.
My advice to you would be to open up a separate thread with a descriptive title so someone is likely to see it; this is primarily a support thread for installation issues so is not high traffic (i.e. you are unlikely to find anyone with Linux DSD experience in this thread). If it's not clear from the above, I'm just a user like you, not a dev, so they may weigh in at some point as well.
--- End quote ---
Thanks for reply. It's true, I misunderstood who you were.
Without any problems, I am using the same output hardware and option settings on an ASrock BeeBox (a NUC-like machine), running Windows 10, as I am on the Pi. They both are clients of an MC server running on a Mac Mini. Still, you seem to know whereof you speak, so I'm thinking you're right about configuration issues.
I'll take you advice and post on the Linux forum.
BTW - as far as running headless goes, i have used an HDMI dongle to fake out software into believing a monitor was attached. i haven't used it on a Pi, yet, but if it works i believe it would be preferable to any (no matter how well engineered) software kludge.
mwillems:
--- Quote from: Slim_Fishguttz on April 06, 2016, 07:12:53 am ---Thanks for reply. It's true, I misunderstood who you were.
Without any problems, I am using the same output hardware and option settings on an ASrock BeeBox (a NUC-like machine), running Windows 10, as I am on the Pi. They both are clients of an MC server running on a Mac Mini. Still, you seem to know whereof you speak, so I'm thinking you're right about configuration issues.
I'll take you advice and post on the Linux forum.
--- End quote ---
If the hardware works with windows, but not with the Pi, then it's either configuration problem or a generic Linux driver support problem; MC on Linux doesn't have any special limitations with respect to hi res PCM that I'm aware of. I'll weigh in with some testing advice once you get your thread set up.
--- Quote ---BTW - as far as running headless goes, i have used an HDMI dongle to fake out software into believing a monitor was attached. i haven't used it on a Pi, yet, but if it works i believe it would be preferable to any (no matter how well engineered) software kludge.
--- End quote ---
If you're referring to the headless operation instructions above, you may not appreciate fully what those instructions "do for you." The purpose of those instructions isn't just to "fake out the software," they also give you a method to remotely configure and control MC on the headless pi without plugging a monitor or keyboard into the pi. You can use Gizmo or JRemote to control day to day playback, but neither of those tools allow for configuration, updating, or library maintenance (or even turning the pi off safely if you need to!). You need a way to interact with the actual desktop of the Pi once in a while, and most folks don't want to haul a monitor and keyboard over to the box.
Also, if you're not a regular Linux user, you may not be aware that VNC-server virtual displays aren't a "kludge"; they're a very common way to administer hardware that doesn't have a monitor attached, or, in the case of real servers, hardware that doesn't even have a display adapter of any kind to "fool" to begin with. VNC is a mature, long-in-use set of software tools.
An "HDMI Doctor" style dongle wouldn't provide any remote administration options, and isn't really necessary on Linux in any case: if you don't care about remote administration there are ways to force the XServer to start without a monitor attached, but I didn't outline them above because they're not particularly useful (you wouldn't be able to interact with it at all without plugging in a monitor). There's also no guarantee that such a dongle would work particularly well with Linux at step one, whereas the VNC solution has been extensively tested.
So I would advise against using such a dongle on the Pi, but if you try it, I would be interested to hear how such a dongle works with Linux (just out of curiosity).
jmone:
@mwillems, my Axiom Speakers have shipped (long way from Canada to Oz but should be here in a week or so). Is there anything I should do when I first get them (eg dump the contents of it's SD Card if you want to see what is on it etc)?
Thanks
Nathan
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version