Forum Replies Created
-
-
18. Juli 2019 at 10:45 #46360
Hi Hurwitz,
Thank you for the detailed update. We will have a look into this.
18. Juli 2019 at 10:45 #46359Hi Hurwitz,
Thank you for the detailed update. We will have a look into this.
18. Juli 2019 at 10:45 #46358Hi Hurwitz,
Thank you for the detailed update. We will have a look into this.
18. Juli 2019 at 10:44 #46357It’s because of the expansion, the space is expanded to have the room for your data. If you create a copy of it before the expansion, you have ca 2 gb of space, after the expansion you have all of the card’s storage taken advantage of.
18. Juli 2019 at 10:36 #46356Hi danilu,
Sorry, I wasn’t clear on the command line options.
Shairport doesn’t have the command line option -C 5, so you need to remove it again. Here’s an overview of shairport’s command line options.
When you start Kodi, the audioplayers are stopped. Check to see if Kodi has the right audio output device selected in its settings.
18. Juli 2019 at 10:26 #46355Hi Frank,
We’ve never had any problems with the image burner plugin. Could you paste your error message here?
17. Juli 2019 at 15:33 #46349Hi chopinhauer,
We do not have an installer for Plex, as we do with the LMS. So you would have to install it manually. Also, it might be a performance bottle neck for the Pi to run both servers at the same time.
Once the HDD is mounted, you can use it with any software on Max2Play, so you don’t need to do this twice. However, installing the plex server itself would require several commands and tweaks from the SSH. There are various guides for this online, our current image is based on Stretch (or buster with the new beta). But again, it probably makes most sense to have a second Pi running just Plex server with a dedicated image.
17. Juli 2019 at 13:17 #46348Hi teeitup,
Which image download did you use for the setup? I will try to recreate the issue here.
17. Juli 2019 at 13:16 #46347Hi lektoren,
Please use the shutdown button in the Settings menu before removing the power supply to make sure you don’t damage the SD card.
17. Juli 2019 at 11:56 #46344Hi Kops,
I spoke with our head developer and this setup is not really feasible on the Squeezebox side as you would have to work around all software commands regarding volume control.
The most convenient solution would probably be a home automation app’s custom player volume control using your hardware’s API. We have a one-click installer of OpenHAB2 which probably fits the bill for this kind of setup.
17. Juli 2019 at 10:25 #46342Hi Erwin,
Thank you so much for the detailed troubleshooting report. The issue is that the GPIO 18 is used by the HiFiBerry card, so the LIRc solution needs to be changed to GPIO 25. Please try this and check if the issue persists.
17. Juli 2019 at 10:11 #46341Hi Frank,
There should be a read option as well. However, you can also use our image burner plugin to read out an SD card if you have a second one.
16. Juli 2019 at 15:00 #46332Hi Kops,
Okay, so you can get all the detailed documentation on the commands for Squeezebox control from our API-Examples. You can use the CLI for more detailed commands. Then, you would have to find a solution to connect these outputs to your specific hardware with commands as you mention. Then, you would need a solution to disable any actual volume change on the end of the software you actually use. Correct?
I’m not sure this is feasible but I will discuss it with our head developer in our next session.
16. Juli 2019 at 11:53 #46329Hi guys,
The max2play image expands the filesystem automatically during the first boot. To stop max2play from doing this, you can access the SD card with image manually, access the config.txt in the filesystem with an advanced editor like Notepad++ and change the value AUTORESIZE=1 to AUTORESIZE=0. Afterwards, the system will stay unexpanded unless you manually expand it in Settings/Reboot.
16. Juli 2019 at 11:03 #46328You’re right, very odd. If you have a second SD, can you try recreating the issue with a fresh image to find out if the problem might be connected to your hardware or network?
15. Juli 2019 at 15:55 #46316Hi ErwinB,
I was just able to successfully load the hifiberry driver for the Digi+ Pro on Pi2B with our buster image. I’ll check playback tomorrow, but it doesn’t look like I can recreate your particular error here.
15. Juli 2019 at 15:28 #46313You forgot the /./ part of the link, I tested it again with the link above and it worked again. Here it is: http://downloads.slimdevices.com/nightly/./7.9/sc/6a6440dc801e31915ec04df28e4c1494ec121931/logitechmediaserver_7.9.2~1562310110_arm.deb
15. Juli 2019 at 15:26 #46312Hi danilu,
Make sure the shairport and squeezelite output devices are different (sysdefault hifiberry and default hifiberry), you can also add -C 5 to automatically close the port for the player after 5 secs of inactivity to make sure your players don’t overlap.
15. Juli 2019 at 15:26 #46309Hi Hurwitz,
I checked your license and it activated our tester.
None of the things you mentioned should have any bearing on our license server and its authentication process.
The only thing you can check is that the automatic access point in WiFi/LAN does not block the internet access.Please try the following:
Make sure your Max2Play device is connected to the internet.
Delete the license in the Max2Play interface and click „save“ with a blank field.
Click on „Settings/Reboot“ again, reenter your license and click „save“.
Check if the green „Activated“ field appears. If not, contact us again for further help.12. Juli 2019 at 10:01 #46299Hello Norbert,
Thanks for chiming in again. Do you have any news regarding the Pi4 and network booting?
12. Juli 2019 at 9:55 #46298Hello Marc,
Thank you for the feedback, I will add this request to our agenda and discuss it with our head developer.
You can also create a topic for the request and if other max2play users chime in and also request it, we will prioritize this development.
12. Juli 2019 at 9:51 #46297Hi Erwin,
Thank you for the feedback, we will test this exact configuration here to make sure it is not a universal problem. Can you tell us which version of the Digi+ it was? (HW X.X on the top of the board)
12. Juli 2019 at 9:36 #46296Hi Kops,
The command line option hw:1/hw:0, depending on the position of your sound card, enables hardware volume control.
You can find the commands for the volume control of Squeezebox in our API Examples plugin.
9. Juli 2019 at 10:20 #46215Hi Erwin,
Glad to hear it. Your best bet is to use our new Buster release and migrate if you prefer to run Buster. So far, the image seems to work with most plugins and we appreciate any feedback to get it out of beta asap.
9. Juli 2019 at 10:18 #46214Hi Mimi,
The -C 5 should be in the command line options in the advanced settings of Squeezelite in the Audioplayer menu.
The server does not impede on your playback, Squeezelite is the player unit for the server to play to.
As I’ve mentioned, the Spotify Connect player is only really useful for standalone Spotify systems. The Spotty plugin for the Squeezebox Server with Squeezelite as player is a more comfortable and feature-rich option. You can quickly and easily set it up with the HowTo I linked above.
9. Juli 2019 at 10:11 #46213Ich denke das sollte gereicht haben. Der Punkt ist in den Server Einstellungen unter Basic Settings der letzte Punkt „Rescan Media Library“, dort die zweite Option „rescan library and clear everything“.
9. Juli 2019 at 10:08 #46212Hi danilu,
If the snd_hifiberry output is selected in Kodi, you should hear sound. Try deactivating Shairport to make sure that this is not the cause.
9. Juli 2019 at 10:04 #46210Hello Marc,
The Squeezebox Server has a radio plugin, you can stream from your phone with DLNA or AirPlay, there are also some radio stations preconfigured in MPD.
8. Juli 2019 at 16:30 #46198Yes, it seems the card is not actually recognized by the system, which might mean that it is defective otherwise not connected.
Please try physically remounting the sound card, to make sure there is not connector problem.
-
