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 June 14, 2016, 07:26:13 am ---Thanks for your follow-up. The dongle works on the Pi, and in fact , has worked on any system that i have, for various reasons, tried it on. As for remote admin, I use Jump Desktop connecting to TightVNC. Jump Desktop connects to my Mini, 2 PCs, 3 Pis, a Ubuntu server, and a virtualized Win10 and a virtualized FreeNAS, both running under Ubuntu. Top shelf program; couldn't function without it.
Since I have your ear - it seems that Linux MC has no server? Is this true?
--- End quote ---
I'm not sure I understand what you mean? In terms of actually functioning as a server, Linux MC works as a media server and has almost similar server functionality to the windows version (that's an area where it's close to feature parity, except for live TV). It doesn't have a tray widget if that's what you mean, but that's just cosmetic. If you start the linux instance with the "mediaserver" flag, it will start minimized, use less memory, and not throw any modal dialogs that would hang the UI. It just won't give you a pretty tray icon, but works perfectly as a server.
--- Quote ---Consequently, I run the MC server in the Win10 vm.
--- End quote ---
Unless you need live TV, you don't need to do this, see above.
--- Quote ---MC runs and connects to my NAS without any problems. However, I can't connect to the MC server, running in the vm machine, from another MC. I use the access code that the MC server supplies and the MC client uses it to try to connect, but it can't find the MC server, although it seems to know its address. I can't positively confirm this since the message addressing this is truncated in the MC messagebox. Guest connecting to outside world - OK; outside world connecting to guest - not so much. I know it has to due with the fact that while my network ip is 192.168.0.xxx, the vm guests run on 192.168.122.xxx. This is recognized by the MC client, but it can't connect because it seems to be a different network. This can be addressed, but requires some research on my part.
--- End quote ---
I don't know what kind of virtualization solution you're using or how you've configured it, so I can't give very detailed advice, but it sounds like the problem is that you're using "NAT" style VM networking. With NAT networking, the host for the VM acts like a router/firewall for the VM, so the inability of programs outside the VM to reach the VM is by design. It's not just that it's on a different subnet, the host is actively blocking traffic to the VM unless you enable port-forwarding or address translation deliberately. Most VM solutions offer other networking modes than the "NAT" mode; for example, virtual box offers a "bridged" mode which effectively just makes the VM another "box" on your home LAN. It can then see and be seen by everything else on the LAN, etc. That kind of configuration is better if you're uncomfortable doing port forwarding.
But you really may not even need the VM; the linux version works fine as a server. Just leave the program minimized, or start it with the mediaserver flag.
Slim_Fishguttz:
--- Quote from: mwillems on June 14, 2016, 05:23:15 pm ---If you start the linux instance with the "mediaserver" flag, it will start minimized, use less memory, and not throw any modal dialogs that would hang the UI.
--- End quote ---
Aha - There's a mediaserver flag? Where is this documented? Is it in the Wiki, I can't find it there. I thought there was no linux server because it wasn't in the startup options, which I guess work differently under linux. From my forum reads, it seems MC under linux is unstable. I think I will keep my underlying server relatively clean and run things virtualized, but I'll try the server mediaserver flag (out of curiosity).
--- Quote from: mwillems on June 14, 2016, 05:23:15 pm ---..... it sounds like the problem is that you're using "NAT" style VM networking.
--- End quote ---
Aha - NAT vs. port forwarding vs. bridging. That's what I need to research. Thanks for the finger pointing.
My regards.
JimH:
I think that the command you need is in this section of the DevZone:
http://wiki.jriver.com/index.php/The_Command_Line
mwillems:
--- Quote from: Slim_Fishguttz on June 15, 2016, 06:34:44 am ---Aha - There's a mediaserver flag? Where is this documented? Is it in the Wiki, I can't find it there. I thought there was no linux server because it wasn't in the startup options, which I guess work differently under linux. From my forum reads, it seems MC under linux is unstable. I think I will keep my underlying server relatively clean and run things virtualized, but I'll try the server mediaserver flag (out of curiosity).
--- End quote ---
It's
--- Code: ---/mediaserver
--- End code ---
If you look at the posts at the top of the thread some o the code examples use the flag.
Spresti:
So I have successfully installed MC21 on my raspberry pi 3. I activated the license via the terminal and everything was work working great! But after a few boots about the fourth time I opened MC21 I got a message indicating that my trail has expired, even though I already activated it. So I clicked apply license and entered my code. It thinks for a second and then pops up saying that it could not connect to the license server. I am connected to the internet and my code is valid. I have tried reinstalling MC21 but at first start it said my trail was expired and still would not let me apply my license saying it could not connect to the license server. PLEASE HELP ME!!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version