Forum Replies Created
6. Januar 2024 at 19:23 #53028
I see that this message is in a string that I initiated. And I think I understand that it is me who titled this ‚No Available Versions, „LMS-Version Does Not Exist“‚ But I will reply from my notes, which somewhat disagree.
In my notes, my problem was an error message saying „cannot locate server.“
And my solution was to set my Raspberry Pi address to 192.168.0.103 (the port was set to 9000 without interaction on my part) and then enter that address into my remote control program, Orange Squeeze.
For Max2Play, in the m2p interface, WiFi/LAN tab, find “Fixed LAN-IP Setup” to set this address.
The rest of this message may or may not be of value….
On the Raspberry Pi, if a reboot is required, disconnecting and reconnecting power does not reset the state as desired, because much of the state information is on the SD card, which is nonvolatile. I had max2play require a reboot after its first two years of operation and again three years later. This is pretty good performance, except that rebooting is so terribly hard. (By contrast, when I used piCorePlayer instead of Max2Play, rebooting was required 4 times in a 7 month period.) My solution is to make a clone of the SD card containing Max2Play after I have the system running. The next time a reboot is required, I clone the clone for backup and install the cloned SD card.27. Januar 2022 at 17:13 #51998
Yes. That worked. Thank you. I can work with that until the Buster image is fixed, of course. I would like to avoid the complexity of incompatibility with the default FAT32 file system, and the extra step of mounting an external drive. But you know that and it is in your plans. So thanks again, I look forward to a new image.25. Januar 2022 at 19:35 #51987
Thanks for the effort, Mario.
I tried 2.55 and got the same behavior as I did with 2.53. Sorry!
On the other topic, as I said, my externally powered hard drive was formatted as FAT32. I have checked and my thumb drives always are FAT32. I do not know how to make them VFAT. If that experiment is still of value, I will try to figure out how to format the external drive as VFAT. If you have any hints on how to do it, they would be appreciated.23. Januar 2022 at 19:26 #51961
I missed your „edit“ because I was not informed that it was there, and I had already read your message. I would recommend that you put in a new reply instead of an edit when communicating next time.
I have some things to say. First: On my PC, under Properties, my external disk shows „File System: FAT32.“ I thought that was the recommended way to set it. Should I create a disk that is formatted as „vfat“ and test again?
Second: I have not yet tried the piCorePlayer experiment, though I started to try. As I said, it is a lot of work. And I do not know whether I should try the 32- or the 64-bit version, or both. I understand from your previous message that whatever I learn from that experiment is very unlikely to be helpful for you. So I will not put high priority on this unless you encourage me to do that, and if you do, please recommend 32, 64, or both.
Third: In studying about piCorePlayer, I came to learn that the 64-b version of piCorePlayer when running on the Rpi 4 does not support the USB fiq drivers. I have no idea what that means, but just in case it might be a hint for your debugging, I will pass that along.
Thanks again.19. Januar 2022 at 2:46 #51942
1. I had set the checkbox to „Max USB Current“ before my recent posting. It is still set that way. It does not change the symptoms.
2. I have tried an externally powered USB hard disk. I have also tried another brand of USB thumb drive. Neither changes the symptoms.
3. When I access the Webadministration, and click on the Basic Settings tab, and click on one of the Browse buttons, under /dev, there is no /sdal.
Thank you for continuing to try with me. Thus far, the problem still looks to be with the buster image. Would it be of value for me to try a piCorePlayer image? If I get the problem with both piCorePlayer and m2p, and not with moOde nor volumio, that would imply a problem with LMS. If I get the problem with m2p but not piCorePlayer, that would imply a m2p problem.16. Januar 2022 at 17:47 #51933
Sad to say, the problem was not resolved with a new power supply. The new power supply is designed for use with the Rpi. It is a CanaKit Raspberry Pi 4 Power Supply (USB-C). It is rated at 5.1V, 3.5A, with an integrated cable.
I have tried rebooting and restarting Squeezelite and Squeezebox server. I have tried _v7.9.3 and _v8.2.0.
If it helps understanding the problem, I can try piCorePlayer. As I said before, my experience with piCorePlayer on the Rpi 3 B was that it needed complete software rebuild about every two months, which is unacceptable for my long-term needs.
In summary, I cannot get a Raspberry Pi 4 B to work with max2play with the only available image, Buster. The failure to work is due to the inability to find any music on a USB thumb drive. The same player and drive works with MoOde and Volumio.10. Januar 2022 at 18:31 #51914
Thank you, Mario. I am grateful for your experiments and observations.
The interesting thing from the m2p perspective is that the apparent hardware problems are experienced by m2p software but not volumio nor moOde. And that the problems with power have such a narrowly observed misbehavior. I would bet that it is possible to code the m2p operating system so that this does not happen. I am not saying that would be necessary nor straightforward, though.
The interesting thing from a Rpi perspective is that the cable makes a difference in your experience. In my configuration, I have a USB-C charger rated at 3 A, which is what the Rpi 4 B is said to require when allowing for extra current required by USB connections. My USB thumb drive does not have specifications on how much current it consumes. The HifiBerry Digi+ Pro that I am using is no longer produced, but the new Digi Pro is said to use a negligible amount of current, so I doubt that is part of the problem. I am suspicious that Rpi 4 B is not configured optimally for independence from cable parameters, where it could be. But this is only speculation.
From my perspective: I have ordered a Raspberry Pi 4 B power supply, 3.5 A, for further experimentation. The experiments are pretty time-consuming, and even if I show that using a different cable fixes the problem, I doubt it has a comfortable margin. So I want to use a more complete fix of a new power supply with integrated cable and more power than is needed.
I will let you know of the results. Thank you so much for replicating the problem.6. Januar 2022 at 3:59 #51891
I tried piCorePlayer about three years ago, as a substitute for max2play. I love their business model, and I like the way they distribute their use of memory. But I found it to fail and require a reboot four times in the 7 months I used it, while I got the first two years on max2play before the first instance of such a problem. So I am anxious to use max2play in both of my players. I am optimistic that you will fix the problem.
(As you probably recognize, a reboot for a Raspberry Pi with non-volatile SD card is a lot of work! I now keep a „clone“ SD card, and have a documented process for how to start from scratch with a complete new download.)3. Januar 2022 at 21:23 #51870
Let me reiterate with minor new information.
I have a Raspberry Pi 3 B with the stretch m2p image and it works. I have a Rpi 4 B with the buster 253 m2p image, and it cannot find my thumb drive, as explained above. This Rpi works correctly with Volumio and now also moOde.21. Dezember 2021 at 21:15 #51860
When you say, „when you have connected the drive,“ I interpret that you mean when the thumb drive is plugged in, which it is. The USB drive is not listed on the „Filesystem Mount“ page. There is nothing displayed under „External Drives on Max2Play.“
The „DEBUG Info“ at the bottom of the „Filesystem Mount“ page is:
#### blkid ####
/dev/mmcblk0p1: LABEL_FATBOOT=“boot“ LABEL=“boot“ UUID=“B6BB-0F0E“ TYPE=“vfat“ PARTUUID=“0634f60c-01″
/dev/mmcblk0p2: LABEL=“rootfs“ UUID=“638417fb-7220-47b1-883c-e6fee02f51ac“ TYPE=“ext4″ PARTUUID=“0634f60c-02″
/dev/sda1: UUID=“982A-618C“ TYPE=“vfat“
/dev/mmcblk0: PTUUID=“0634f60c“ PTTYPE=“dos“
#### mounted ####17. Dezember 2021 at 1:34 #51850
My „Filesystem Mount“ tab does not show my USB drive. And I am not confident I know how to „save the path there.“ I typed:
„USB thumb drive“ /media/usb <blank> no 666
…into the „add“ boxes and clicked „Save.“ The response was:
Sambashare successfully added
Samba Service restarted
But when I try to scan for music using the path /media/usb, I still get no files found.
Please also note: I have shown that I get this same misbehavior with my Rpi 3 B using the „buster“ image. It works fine with the „stretch“ image. I have also shown that I can run Volumio successfully on the Rpi 4 B, with the same thumb drive. I am not sure, but I think I recall trying the stretch image on the 4 B without success; this is not recommended anyhow.
I would think that this means that the buster image v253 is not meeting customer needs; it certainly does not work for me.16. November 2021 at 18:10 #51792
Thanks for your interest! My question, Am I missing something, still applies. Let me try to be more exact in what I am looking for.
To answer your question, my current workaround is to use one squeezebox server and one Volumio system. I do not think Volumio is based on squeezebox, but it has the functionality I am looking for, which is a (headless) player with shuffle capability controlled by a Wi-Fi app (which in Volumio runs in a browser). I am pretty sure I can make a system with two squeezebox players work well, though right now, server discovery is slow and inconsistent, but I think that problem can be solved.
What I am looking for is the capability to have a player which shuffles discs within a library using the „Don’t stop the music“ plug-in, and that library can be browsed via album art, while ignoring the discs in another library. I need to be able to switch libraries extremely easily. It is acceptable if I must change players in order to change libraries; in fact, that is slightly preferred.
It is my observation #1 that, even with Multisqueeze, I cannot have one library for one player and a separate library for the other. It is my observation #2 that, even with Multilibrary and Custom Browse, I cannot browse via album art only the selected library, and I cannot shuffle albums of only the selected library.
Perhaps my observations #1 or #2 are due to an oversight on my part. Are these observations incorrect/am I missing something? Thanks!12. November 2021 at 23:28 #51784
Thank 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.