INTERACT FORUM
More => Old Versions => JRiver Media Center 22 for Linux => Topic started by: pepar on June 14, 2017, 06:51:08 am
-
With an always on MC Library Server, do clients read the content from the NAS (unRAID in my case) and only get library details about the content from the Server?
Jeff
-
It must come from the mc server, as it works without connection to the drive where the actual files reside.
-
If the client has access to the content at exactly the same path, it is possible to configure it to read the content directly from that location. Note this currently implies that client runs the same OS as the server (or at least the same family, windows vs nix).
-
Client could mount the Samba share (unRAID) but is currently only sharing the library via the Library Server. If client isn't reading the file directly from the Samba with that scheme, I'd prefer to have it do that.
-
Check media network / client options / play local file....
That should enable the option as described by Matt above.
-
By "same path" I should mount the Samba share on thenclients as I have on the MC Media Server?
-
By "same path" I should mount the Samba share on thenclients as I have on the MC Media Server?
yes
i.e. if you take the path from the library and then do an ls on that path on the client, it must be able to read the file at that path
-
Linux newb here - "do an ls" .... ?
-
Is there any good reason to go through these procedures to make an MC client read directly from a NAS device, as opposed to reading from the MC server? Is there any benefit to the end user?
Brian.
-
My media storage is separate from my MC server. I'd prefer clients reading directly from the file server and not via the Library Server device.
-
ls is a Linux command. Use it at a Linux prompt.
-
I feel there is possibly a slight communication issue here, maybe I'm missing something.
If you want your Linux clients to access the network share at boot: for my Debian, Pi3, and Mint boxes I added a line similar to below to the /etc/fstab file in all 3 (identical line added to all 3):
//(server.ip.add or name)/sharename /home/username/Music cifs auto,user,credentials=/home/username/netlogin 0 0
Netlogin is a text file with sharing credentials if needed. Get one machine working and go from there.
For the Debian machine I had to add the smb and cifs-util packages; for the Pi3, I had to go into pi settings from main screen and select "Wait For Network At Boot"(?), for Mint it worked out of the box with the added line.
Of course, these will not be MC "clients" now, and will need to do their respective importing, etc. like any other stand-alone pc, and suggest using one (win or Linux) machine as "master" for tagging, etc. All others access pre-tagged and processed files.
Hope this helps.
-
My media storage is separate from my MC server. I'd prefer clients reading directly from the file server and not via the Library Server device.
What benefit does that have?
Brian.
-
Personally, I have worked out the automounting of shares at login. That how my DebianXFCE/i3 NUC MC Library Server is configured. (My media is stored on an unRAID server.) When I set up my first client, also Debian/XFCE/i3 NUC, I installed MC and poked around the settings and selected the Library served by the first box. It will play content.
My question was if the played content was being read directly from the unRAID or via the NUC running MC Library Server. And that's where I am at this point.
Jeff
I feel there is possibly a slight communication issue here, maybe I'm missing something.
If you want your Linux clients to access the network share at boot: for my Debian, Pi3, and Mint boxes I added a line similar to below to the /etc/fstab file in all 3 (identical line added to all 3):
//(server.ip.add or name)/sharename /home/username/Music cifs auto,user,credentials=/home/username/netlogin 0 0
Netlogin is a text file with sharing credentials if needed. Get one machine working and go from there.
For the Debian machine I had to add the smb and cifs-util packages; for the Pi3, I had to go into pi settings from main screen and select "Wait For Network At Boot"(?), for Mint it worked out of the box with the added line.
Of course, these will not be MC "clients" now, and will need to do their respective importing, etc. like any other stand-alone pc, and suggest using one (win or Linux) machine as "master" for tagging, etc. All others access pre-tagged and processed files.
Hope this helps.
-
What benefit does that have?
Brian.
I try to outfit my "devices" CPU-wise based on the work that they are handling. There are many low power options, which is something I gravitate to. Some of my devices are fabless. So, At least, I am curious as to what is happening on each device.
Jeff
-
<shrug> I have no idea what you mean. But that's fine. Good luck with your project.
Brian.
-
One more try with this example ... :)
For my gaming rig I use a 6-core i7 and a fancy Radeon video card. For a file server I use a low power Pentium and onboard video.
Ahh, also, autocorrect turned "fanless" into fabless.
Jeff
BTW, I still have an open question as to how to have clients that are using the Library Server actually read the files from the file server ... ?
-
Your open question has been answered so perhaps you can clarify what isn't clear to you then someone can explain
re the "read direct from the NAS", if no transcoding is involved then it's really a question of bandwidth IMV. If you push all content down the NAS - server - client path then NAS - server is a potential bottleneck (and could also theoretically have an impact on the server). I would have thought this isn't going to be an issue in any decent home network though, unless perhaps you have *alot* of clients and/or a really weak server. Personally I just go with a fat pipe between the NAS the server but then that's mostly because my secondary clients are predominantly linux so I have no choice in the matter.
-
Thanks, all. I got back from a trip, set up automount of the share identically on the client as it is on the Library Server and made the MC setting change recommended. I have edited the thread subject and added [SOLVED].