More > JRiver Media Center 22 for Linux

QuickStart Guide Raspberry Headless question

<< < (2/2)

akira54:
Thank you very much fir this very full answer. After downgrading MC22 (I too had lots of random crashes) I followed your setup instructions mentioned here https://yabb.jriver.com/interact/index.php/topic,108981.0.html but am still a little uncertain about two points. I am running RPI headless, and you state: "If you are using such a virtual display, substitute the display variable in the Environment section, and change the "After" line to refer to the name of the systemd service you're using to start your vnc server, but note that VNC virtual displays may not work correctly anymore with MC since 22.0.36."
I do not know what you mean by "substitute the display variable in the Environment section" and should I change the "after" line to read: "After=x11vnc.service" in my setup? In both jriver.service and x11vnc.service?

Also, can I now disable the built-in VNC service and still use VNC Viewer on my Mac to access the RPI?

blgentry:
mwillems:  Thanks for the explanation. ...and all of your work developing the guides and the methods used in them.  I'm a Linux guy from way back.  My current day job is mostly working on Linux.  But I still followed your guides; without them I'm not sure I would have bothered with a Pi setup.  But I'm glad I did.  :)

Brian.

mwillems:

--- Quote from: akira54 on July 11, 2017, 02:11:35 pm ---Thank you very much fir this very full answer. After downgrading MC22 (I too had lots of random crashes) I followed your setup instructions mentioned here https://yabb.jriver.com/interact/index.php/topic,108981.0.html but am still a little uncertain about two points. I am running RPI headless, and you state: "If you are using such a virtual display, substitute the display variable in the Environment section, and change the "After" line to refer to the name of the systemd service you're using to start your vnc server, but note that VNC virtual displays may not work correctly anymore with MC since 22.0.36."
I do not know what you mean by "substitute the display variable in the Environment section" and should I change the "after" line to read: "After=x11vnc.service" in my setup? In both jriver.service and x11vnc.service?

Also, can I now disable the built-in VNC service and still use VNC Viewer on my Mac to access the RPI?

--- End quote ---

If you followed my instructions exactly, you shouldn't need to modify the first service at all except to add your user name (probably "pi").  Likewise, if you're using my method, you shouldn't need to modify the second service at all except to add your username twice.

I can't say how it will interact with the built in vnc service as I've never used it.  I'm going to try and update the overall quick start guide for mc23 this weekend (assuming a non-beta arm build gets put up) to incorporate the services if you need more detailed instructions.


--- Quote from: blgentry on July 11, 2017, 04:44:30 pm ---mwillems:  Thanks for the explanation. ...and all of your work developing the guides and the methods used in them.  I'm a Linux guy from way back.  My current day job is mostly working on Linux.  But I still followed your guides; without them I'm not sure I would have bothered with a Pi setup.  But I'm glad I did.  :)

Brian.

--- End quote ---

Thanks Brian!  I'm comparatively new to Linux proper (about 4-5 years), but I've been really excited about raspberry pi's and their potential.  I remember, as a kid, trying to write BASIC on an old Tandy Model 3, and if someone had told me then that in 30 years I could buy a computer that was smaller than an Atari cartridge for less money than an Atari cartridge, that was more powerful than any computer I'd ever used, I'd have called them a liar.  The first time I got to see a Raspberry Pi, it really brought some of the sense of wonder back into the PC hobby for me, so I'm glad that the guides are helpful to others in getting into them.  Stay tuned for an MC 23 update to the guide  ;D

akira54:
I did follow your instructions to the letter, but was just a little confused by the proviso you added. I took your remark that you have never used the built-in server to mean that it can be switched off, but what program do I need on my Mac to set up a VNC connection with the RPI. VNC Viewer which I used before now refuses to connect.

I have noticed two further problems. Would you like me to start separate threads on them?
1. When playing HD material (SACD iso) the PI stutters, i.e. every 20 seconds or so (pretty regular) it stops playing for circa 4 seconds and then continues again. NB. With 44.1 24 bit flacs playback is smooth.

2. Using JRemote makes MC crash before all the artwork for the various folders is even properly loaded. NB. After the automatic restart of MC22 the artwork is replaced by "blanks" and JRemote no longer crashes.

mwillems:

--- Quote from: akira54 on July 12, 2017, 12:28:25 am ---I did follow your instructions to the letter, but was just a little confused by the proviso you added. I took your remark that you have never used the built-in server to mean that it can be switched off, but what program do I need on my Mac to set up a VNC connection with the RPI. VNC Viewer which I used before now refuses to connect.

--- End quote ---

Try tigervnc or tightvnc; if they don't work something is misconfigured.


--- Quote ---I have noticed two further problems. Would you like me to start separate threads on them?
1. When playing HD material (SACD iso) the PI stutters, i.e. every 20 seconds or so (pretty regular) it stops playing for circa 4 seconds and then continues again. NB. With 44.1 24 bit flacs playback is smooth.

--- End quote ---

You should open a thread on this, or have a look at the two other threads currently running about DSD on the pi/linux.


--- Quote ---2. Using JRemote makes MC crash before all the artwork for the various folders is even properly loaded. NB. After the automatic restart of MC22 the artwork is replaced by "blanks" and JRemote no longer crashes.

--- End quote ---

You should set the thumbnailing priority to low, and then pre-build all the thumbnails using the "build thumbnails" option.  If you have a lot of files, it will take a while, but the behavior you're describing is caused by MC exhausting the very limited RAM on the pi due to aggressive thumbnailing (which is why it crashes before all h=the art finishes appearing.  Once the thumbs are generated stability dramatically improves.

Navigation

[0] Message Index

[*] Previous page

Go to full version