Max2Play Home › Forums › Max2Play on Raspberry PI › Shuffle stops spontaneously, perhaps due to multi squeeze, since removed
Tagged: Shuffle nonvolatile multisqueeze
- This topic has 2 replies, 2 voices, and was last updated 3 years, 1 month ago by Joe Gorin premium.
-
Posted in: Max2Play on Raspberry PI
-
8. November 2021 at 7:40 #51778
I like to let my Raspberry pi music player run on “shuffle albums” much of the time. But now it fails to keep shuffling, stopping 15 hours, 1 hour, 3 hours, etc. after starting in recent experiences. But wait, there is more….
It frequently will not show the second half of my library. It frequently will not show the artwork for some of my disks in the Albums view.
This all sounds like it needs a reboot. And I have rebooted by using a recreated SD card from a saved image from times when it did not have these problems. But the problems continue. I have cleared cache and done clear and rescan many times.
Also, it seems to remember what disc was playing recently, even though I have just changed the SD card.
All this misbehavior started soon after I tried, and abandoned, multisqueeze.
My obvious question is, How do I get it to start working reliably again? And the related question is, How do I fully clear nonvolatile memory?
9. November 2021 at 15:00 #51779Hi Joe,
Which Max2Play version, LMS version do you use? Which image do you have installed (Stretch or Buster)? You can find the latter information in the debug info in Settings/Reboot. Do you find any errors in the server log that can be traced back to the problem? You can find the server log in the settings of the Squeezebox server under „Information“.
12. November 2021 at 23:28 #51784Thank you for the reply.
I now have two Raspberry Pi computers playing music. I have found that the one that is running Max2Play and misbehaving also misbehaves when running Volumio, and the one that was running Volumio works correctly with Max2Play. So my first RPi is having hardware problems.
These days, I am always most suspicious of software and settings problems, but this looks like hardware.
To answer the original question about volatile memory in case any future users searching come upon this, I now understand that this is how it works: All the nonvolatile memory is on the SD card. When I replace my SD card with a cloned copy, it still has a lot of state and library information on it. The best way to eliminate unfortunate state information is to recreate the SD card starting with a Max2Play download.
Again, thanks for your thoughts.
-
You must be logged in to reply to this topic.