More > JRiver Media Center 22 for Linux
JRiver Media Center 22.0.111-5 for Debian ARM
bob:
--- Quote from: PAPETOURNE on January 15, 2017, 08:41:20 am ---What file extention is to be taken to update MC22 in my NAS QNAP 251hs. taking the doawload as is does not work.
--- End quote ---
MediaCenter Arm is not packaged for non-intel QNAP boxes.
You might want to check the docker thread if you want to try getting MC to run on ARM based QNAP boxes.
bob:
--- Quote from: mk9pa on January 15, 2017, 11:45:58 am ---Brand new user, evaluating MediaCenter22. Hope I'm posting in the right place for a bug report.
I am running MC 22.0.63 on Raspberry Pi 3/Raspbian Jessie. My requirement is that RPi be headless, and so far so good -- it has never had a monitor, keyboard, or mouse plugged into it, just power and network.
MC22 is running using Xvfb for a virtual display, and x11vnc to act as VNC Server. This works well so far (at least, overnight), and I can connect to the VNC server from a Mac using Screen Sharing. It's the only configuration I've found so far that works on both ends (RPi and Mac).
I also purchased JRemote 3.23 on iOS and tested it out. On at least 6 occasions it has crashed MC22. Here are some error messages I captured from the RPi terminal window where MC22 was invoked from:
*** Error in `mediacenter22': double free or corruption (fasttop): 0x6e5995c0 ***
*** Error in `mediacenter22': double free or corruption (fasttop): 0x667ca8c8 ***
*** Error in `mediacenter22': double free or corruption (fasttop): 0x679bcd78 ***
Another crash occurred without an error message, just a segmentation fault.
The one thing that seems to be in common in all the crashes is that JRemote was downloading artwork (or metadata?) when all the crashes occur. I can make it crash about once a minute by populating album art in the grid view on JRemote.
--- End quote ---
You might be running into that same xrandr issue above.
Otherwise if you can give us enough detail to try to duplicate that here we'll look at it.
We have not observed that behavior with a real display or the dummy X server and X forwarding.
mk9pa:
--- Quote from: bob on January 15, 2017, 01:38:04 pm ---You might be running into that same xrandr issue above.
Otherwise if you can give us enough detail to try to duplicate that here we'll look at it.
We have not observed that behavior with a real display or the dummy X server and X forwarding.
--- End quote ---
The intent is that getting MC running can be done entirely by the headless RPi during boot, running with a virtual frame buffer. Then, if access to the screen by a client is needed for configuration, etc., that can occur without any action on the RPi, just on the client.
The RANDR problem causes immediate MC22 crash on startup when running with tightvncserver with the RANDR extension missing message as others have reported. Running with vnc4server causes an immediate crash but without the RANDR message. Running with the current default Raspbian RealVNC server seems to work on the RPi side, but is not compatible with MacOS' screen sharing client. Thus the attempt to use Xvfb and x11vnc. With this combination, MC22 starts and runs fine, at least overnight, without JRemote communicating with it, and on the shared screen's desktop I can resize the MC22 window without any issue. Desktop performance is not great, but not terrible either.
Here's more detail on my setup. Let me know if you would like something more.
RPi 3 running Raspbian Jessie fully updated as of 1/14/17. MC22 Linux/Debian ARM build 22.0.63, installed following instruction at https://yabb.jriver.com/interact/index.php?topic=106027.0 up to (and including) the section "Installing MC", i.e. modifications to /boot/config.txt.
My notes on how to set it up once installed are:
On the RPi, one time:
* Set x11vnc password (required by Mac’s Screen Sharing) using x11vnc -storepasswd
On the RPi, each time it boots:
* Check that no leftover x11vnc or Xvfb are running
* Start xvfb: Xvfb :1 -screen 0 1280x768x24 &
* Start an X window manager: DISPLAY=:1 lxsession &
* Start MediaCenter: DISPLAY=:1 mediacenter22 /MediaServer &
On the MacOS client, if want to attach to the MediaCenter display:
* ssh -l pi -L 59000:localhost:5900 <rpi3-hostname> 'x11vnc -localhost -display :1 -forever -usepw -ultrafilexfer’
* Confirm that x11vnc is using port 5900
* Use Finder’s Connect To Server… (cmd-K) and type in vnc://localhost:59000. Password is the one given to x11vnc -storepasswd.
* In this case, the local (MacOS) port 59000 is tunneled to the RPi’s port 5900. All the RPi port numbers and screen numbers have to match (with offset of 5900).
Now, start JRemote (3.23, iOS 10.2) and browse artists or albums. When album art is missing on JRemote, it appears to produce a crash of MC22 pretty much every time, or at least a large fraction of the time. The x11vnc options are verbatim from one of the references I found along the way, and I can't find it at the moment. I'll keep looking in case it's significant.
bob:
I've not used xvfb before so I'm not sure how or if that supports xrandr.
I'll try your test with the dummy xserver and missing coverart when I can.
Update: the dummy X display works fine with remote desktop and xtightvncviewer.
mk9pa:
--- Quote from: bob on January 17, 2017, 01:37:39 pm ---I've not used xvfb before so I'm not sure how or if that supports xrandr.
I'll try your test with the dummy xserver and missing coverart when I can.
--- End quote ---
Thanks, Bob. I'll try the dummy X server and xpra, which sounds like it should do what I want also.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version