INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Linux => Topic started by: elvanor on December 04, 2018, 06:51:32 am
-
Hello,
I bought a JRiver Media Center license (version 22, I believe) to use on my QNAP NAS. It worked well, as there was a package for QNAP (don't remember if it was official or not).
However, it turned out that QNAP NAS are total crap. I had tons of problems with them, tried to solve them but never really succeeded. In the end, I just decided to buy an Asustor NAS. It works *much* better, and while I am not yet 100% happy about it, it's already day and night compared to the QNAP.
But, in the progress I lost JRiver Media Center. My question is thus simple: is there a way to install this software into an Asustor NAS? There is no official package, for what I understand there is also no unofficial package. Is it possible to make one? or how can I install it then, should I follow another tutorial? Has anyone already managed to do so?
Jean-Noel
PS: A google search turned out a comment in a forum saying that MC works on Asustor, but it was dated from 2015 and did not contain any instructions or details.
-
It's not recommended (or supported as far as I know) to run JRiver Media Center on a NAS. There was a version of MC22 for QNAP but it was discontinued.
It'd be easier to use a Raspberry Pi, an IdPi, an Id or a NUC to run JRiver Media Center with the NAS connected (connected via wireless, wired or USB).
-
I would be curious to know why it's not recommended... although many things did not work correctly on my QNAP, MC did work perfectly without any problems.
-
This page of this recent topic might give you more insight: https://yabb.jriver.com/interact/index.php/topic,87159.50.html
-
This page of this recent topic might give you more insight: https://yabb.jriver.com/interact/index.php/topic,87159.50.html
Thanks. I read the topic, and I can understand JRiver position on this (although I am not so sure the NAS market is so small). Anyway I managed to run it via Docker on my NAS (Docker really is a nice technology). But it's still not OK for me, as I need local audio rendering and (apparently) the Docker image does not support this. Now if JRiver would make an official Docker image, I am sure *this* would not be wasted time. As Docker is already a de facto standard.