INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Experience with MC on PI3  (Read 7780 times)

jschad

  • Recent member
  • *
  • Posts: 5
Experience with MC on PI3
« on: October 27, 2016, 03:52:13 am »

Hi there, I’m new on this board I but use MC since several years and like to give you an overview what I did with MC on a PI3.

I’m using MC since release 17 on Windows and when r22 came out I also implemented the system on a PI3. My intention was to have a system running 24/7 with a fairly good performance and sound quality and not to get a system with a highend sound. Following what FREDDIEKABERMAN posted here I like to sum up my experience with the PI3.
Starting short after MC22 came out I bought a PI3 and installed it out of the box without any further modifications. The installation was done very quickly according to MWILLEMS instructions (thanks). As FREDDIEKABERMAN told us I also experienced lots of drop outs when connecting a USB DAC (MusicalFidelity VDAC II). I first thought it only may occur due to the fact that my music (flac 24/96khz) resides on a network drive (Synology NAS). Then I tried to read the music from a USB disk connected to the PI3 but the dropouts didn’t disappear. I played around with buffer options and playing from disk versus storage without success.
Next action was to install a Hifiberry DAC+ pro with analog outputs and I experienced a major step forward. From now on I had very seldom dropouts and when I switched to playing the music directly from the network storage instead of playing from internal storage they disappeared completely.
The system is far away from being error free or as comfortable like the Windows version but the music plays constantly without dropouts and that’s important! Errors which still remain are that MC stops working regularly when it is started headless through VNC connection. On the other hand when it is connected to a TV via HDMI cable there is a small amount of hum which can be heard in silent moments within the music if using higher volumes on the amp. To prevent this I have to start the system through a TV connection and then I disconnect the TV and do the rest via JREMOTE.  The sound quality is fairly good and very close to what I hear from my Windows/HTPC running a RME HDSP9632 sound card and that’s a real surprise for me. Possibly a difference is more hearable when using a real high end system (see my configuration below).
I’m now waiting that the Theaterview will be implemented for the LINUX version and for sure then I also need to establish a remote control system for the PI3.
To improve the sound quality in the next weeks I will try a Hifiberry DIGI+ and feed the music signal to an external DAC via SPDIF/TOSLINK. If this will bring me closer or exceed to the performance of my HDSP9632 and the problems described above are sorted out then a PI3/MC version can be a real good solution with low power consumption, good music quality and perfect handling.

Configuration: Synology NAS, HTPC/Win7/RME HDSP9632/MC22, RPI3/LXPANEL 0.7.2/MC22, Audionet SAM, Piega P4

Logged
Synology NAS  -  HTPC/Win7/RME HDSP9632/MC22  -  RPI3/LXPANEL/MC22  -  Audionet SAM  -  Piega P4

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874
Re: Experience with MC on PI3
« Reply #1 on: October 27, 2016, 03:32:39 pm »

On the pi you might want to disable disk buffering for audio (it can help with dropouts, the downside is that some formats aren't seekable as streams).
Tools->Options->Media Network->Advanced->Disable Audio Buffer To Disk
Logged

jschad

  • Recent member
  • *
  • Posts: 5
Re: Experience with MC on PI3
« Reply #2 on: November 01, 2016, 08:29:19 am »

Thanks Bob,

do you know how to prevent the instability of MC when started headless?
Logged
Synology NAS  -  HTPC/Win7/RME HDSP9632/MC22  -  RPI3/LXPANEL/MC22  -  Audionet SAM  -  Piega P4

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72439
  • Where did I put my teeth?
Re: Experience with MC on PI3
« Reply #3 on: November 01, 2016, 08:36:46 am »

Please describe what is meant by "instability". 
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7805
  • Autumn shade...
Re: Experience with MC on PI3
« Reply #4 on: November 01, 2016, 08:38:07 am »

Well, if you're experiencing crashes/sudden closes disabling auto-import (and just importing manually on-demand) would be the best bet, I'm thinking. A bad file during auto-import is usually the reason why MC will crash/close and seem unstable.

No issues here with stability.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874
Re: Experience with MC on PI3
« Reply #5 on: November 01, 2016, 10:48:22 am »

Also, if you consistently get one of these crashes, a log would be nice so we could request the bad file from you to try to code around the import errors.
Logged

jschad

  • Recent member
  • *
  • Posts: 5
Re: Experience with MC on PI3
« Reply #6 on: November 02, 2016, 07:42:06 am »

Thank you for your replies. Let me describe what I'm doing:

I start the PI with a TV and a keyboard connected but do not start MC. After everything is running I switch off the TV and start VNC on a Android device (headless) to controll the system remotely. Via VNC I start MC and let it run 24/7. I do not start any import of music files nor do I use autoimport. Knowing that the PI version of MC is still under development I try to control everything manually. Sometimes MC stopped working after a sudden close therefore I switched back and start MC via a connected TV. This version is running absolutely stable for many days.

This sudden death occurs not necessarily during playing a file it also occurs when MC is just waiting. I checked the logs on the PI but didn't find anything unusual.

I think it makes sense to try the headless version again because in the meantime (since the last crash) I upgraded MC as well as the PI's Linux.

Thank you so far for your help I will come back after the test.
Logged
Synology NAS  -  HTPC/Win7/RME HDSP9632/MC22  -  RPI3/LXPANEL/MC22  -  Audionet SAM  -  Piega P4

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7805
  • Autumn shade...
Re: Experience with MC on PI3
« Reply #7 on: November 02, 2016, 07:44:59 am »

Yeah, auto-import runs in the background so it very well could be crashing when trying to import a bad file. You should try enabling logging in MC and posting the logs here.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

jschad

  • Recent member
  • *
  • Posts: 5
Re: Experience with MC on PI3
« Reply #8 on: November 08, 2016, 11:16:38 am »

After a week of testing I had 4 crash situations. Two during the night which may be caused by autoimport and bad files but I didn't add any file to my storage. One time it crashes during normal play of music and the last time it crashes during intensive scrolling of the album list on JREMOTE possibly caused by storage problems.

All these crashes occurred when MC was started in a headless configuration. The last two days the system was running non-headless without any problem.

In total I had much less crashes than a few weeks ago, before I updated the system. For the moment I can live with this situation.

Can anybody tell me how to activate logging within MC.

Thanks for your support

 
Logged
Synology NAS  -  HTPC/Win7/RME HDSP9632/MC22  -  RPI3/LXPANEL/MC22  -  Audionet SAM  -  Piega P4

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72439
  • Where did I put my teeth?
Re: Experience with MC on PI3
« Reply #9 on: November 08, 2016, 11:26:57 am »

Logging is under the Help menu.  There is a wiki topic on Logging.
Logged

jschad

  • Recent member
  • *
  • Posts: 5
Re: Experience with MC on PI3
« Reply #10 on: November 08, 2016, 11:54:51 am »

Thanks will do.
Logged
Synology NAS  -  HTPC/Win7/RME HDSP9632/MC22  -  RPI3/LXPANEL/MC22  -  Audionet SAM  -  Piega P4

balky

  • Junior Woodchuck
  • **
  • Posts: 87
Re: Experience with MC on PI3
« Reply #11 on: February 19, 2017, 08:28:38 am »

After a week of testing I had 4 crash situations. Two during the night which may be caused by autoimport and bad files but I didn't add any file to my storage. One time it crashes during normal play of music and the last time it crashes during intensive scrolling of the album list on JREMOTE possibly caused by storage problems.

All these crashes occurred when MC was started in a headless configuration. The last two days the system was running non-headless without any problem.

In total I had much less crashes than a few weeks ago, before I updated the system. For the moment I can live with this situation.

Can anybody tell me how to activate logging within MC.

Thanks for your support

 


What did you do to resolve this issue?

I have a library of + / - 35K files, and mediacenter keeps crashing whenever there is any intensive activity from JRemote...
I had this once in while when I was using Pi 2B, but since about two weeks after changing to Pi 3B it has become near impossible to search for anything...

At first I thought it has to do with the fact that I was running MC20 and after several re-installs, I bought the upgrade license to MC22 today, and believe me, the problem is identical...

Thanks
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874
Re: Experience with MC on PI3
« Reply #12 on: February 20, 2017, 11:38:22 am »


What did you do to resolve this issue?

I have a library of + / - 35K files, and mediacenter keeps crashing whenever there is any intensive activity from JRemote...
I had this once in while when I was using Pi 2B, but since about two weeks after changing to Pi 3B it has become near impossible to search for anything...

At first I thought it has to do with the fact that I was running MC20 and after several re-installs, I bought the upgrade license to MC22 today, and believe me, the problem is identical...

Thanks
It's possible the JRemote actions are causing MC on the Pi to run out of memory.
You might try running top from the command line while MC is running and try to reproduce the issue watching the memory usage.
Logged

balky

  • Junior Woodchuck
  • **
  • Posts: 87
Re: Experience with MC on PI3
« Reply #13 on: February 20, 2017, 11:57:25 am »

It's possible the JRemote actions are causing MC on the Pi to run out of memory.
You might try running top from the command line while MC is running and try to reproduce the issue watching the memory usage.

Thanks Bob...
Just tried this now and each time I reproduce the issue... i.e. open genre-reggae for example, while the album art loads, the CPU goes right up to 99% and memory usage goes between 20% - 25%, and MC crashes.
Been doing this for the last 10 minutes...
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874
Re: Experience with MC on PI3
« Reply #14 on: February 20, 2017, 05:08:46 pm »

Thanks Bob...
Just tried this now and each time I reproduce the issue... i.e. open genre-reggae for example, while the album art loads, the CPU goes right up to 99% and memory usage goes between 20% - 25%, and MC crashes.
Been doing this for the last 10 minutes...
Did you drop the thumbnailing threading priority down to low in MC's options?
This combined with pregenerating the thumbnails has been a solution for what you are seeing.


Logged

balky

  • Junior Woodchuck
  • **
  • Posts: 87
Re: Experience with MC on PI3
« Reply #15 on: February 21, 2017, 03:48:52 am »

Did you drop the thumbnailing threading priority down to low in MC's options?
This combined with pregenerating the thumbnails has been a solution for what you are seeing.

I'm not sure I did... I'm currently at work now... (CET timezone...  ;)) will check as soon as I am back home and let you know.

Thanks.
Logged

balky

  • Junior Woodchuck
  • **
  • Posts: 87
Re: Experience with MC on PI3
« Reply #16 on: February 21, 2017, 12:37:44 pm »

Did you drop the thumbnailing threading priority down to low in MC's options?
This combined with pregenerating the thumbnails has been a solution for what you are seeing.

I have changed the thumbnailing threading priority down to low and this doesn't help...

What do you suggest I do next?

Thanks
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13874
Re: Experience with MC on PI3
« Reply #17 on: February 21, 2017, 02:44:05 pm »

I have changed the thumbnailing threading priority down to low and this doesn't help...

What do you suggest I do next?

Thanks
Did you pre-generate the thumbnails before trying JRemote again?
Logged

balky

  • Junior Woodchuck
  • **
  • Posts: 87
Re: Experience with MC on PI3
« Reply #18 on: February 22, 2017, 03:43:20 am »

Did you pre-generate the thumbnails before trying JRemote again?

Thanks Bob,

The pre-generate thumbnails does seem to solve the issue...

Thanks once more.
Logged
Pages: [1]   Go Up