More > JRiver Media Center 22 for Linux
JRiver Media Center 22.0.111-5 for Debian ARM
bob:
--- Quote from: mwillems on January 13, 2017, 07:59:34 pm ---Good pointer, but not the answer sadly. Xrandr is installed, but tightvncserver doesn't support randr on its virtual displays. I get the same error when I try to run xrandr on the pis. Looks like I'm not alone:
https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=16598
So it looks like I'll need to find a new VNC server that supports xrandr. In the interest of completeness, I'll note that my JRiver server instance (where I was having the drawing issues) was also being accessed via VNC (but not via a virtual display, I was using x11vnc for it).
--- End quote ---
How about running with the dummy XServer and using a XWindows server to access the Pi?
I do this on linux all the time and OSX with XQuartz. Windows can use putty and XWin as a the server.
mwillems:
--- Quote from: bob on January 13, 2017, 09:18:07 pm ---How about running with the dummy XServer and using a XWindows server to access the Pi?
I do this on linux all the time and OSX with XQuartz. Windows can use putty and XWin as a the server.
--- End quote ---
You mean plain old X forwarding? I'll give it a shot when I have some time, but performance is usually pretty poor when I've tried it, and the windows xserver's I've used have been kind of flaky.
Apparently some VNC implementations do correctly support randr, and tightvnc has some other problems as well (i.e. can't display modern desktops at all), so my first stop is trying a few other vnc servers. I guess newer pi builds actually ship with RealVNC built in, so I may do a quick reinstall on a pilot system and see if that works.
bob:
--- Quote from: mwillems on January 13, 2017, 09:23:59 pm ---You mean plain old X forwarding? I'll give it a shot when I have some time, but performance is usually pretty poor when I've tried it, and the windows xserver's I've used have been kind of flaky.
Apparently some VNC implementations do correctly support randr, and tightvnc has some other problems as well (i.e. can't display modern desktops at all), so my first stop is trying a few other vnc servers. I guess newer pi builds actually ship with RealVNC built in, so I may do a quick reinstall on a pilot system and see if that works.
--- End quote ---
Yup, just regular old X forwarding.
It's pretty slow through ssh but decent enough for me when I do it directly and on a Lan.
PAPETOURNE:
What file extention is to be taken to update MC22 in my NAS QNAP 251hs. taking the doawload as is does not work.
mk9pa:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version