Forum Replies Created
-
-
21. Dezember 2021 at 14:35 #51857
Hallo panapaul,
Ein gleichzeitiger Betrieb der Soundkarte und des Displays, wenn beide die GPIO-Leiste verwenden, dürfte nicht funktionieren. Die Soundkarte wird trotz der angelöteten GPIO-Leiste nicht alles durchschleifen, sondern bestimmte Pins selbst beanspruchen, sodass das Display dann nicht richtig funktioniert. Es wäre aber z.B. möglich, ein Display über den DSI-Anschluss neben der HAT-Soundkarte zu betreiben. Oder du verwendest das GPIO-Display und schließt dann eine USB-Soundkarte an.
Teste am besten mal, ob das Display mit dem RPI-Display Plugin funktioniert, wenn du es direkt an den Pi anschließt (ohne Soundkarte). Das sollte zumindest funktionieren.16. Dezember 2021 at 13:35 #51847Hi Joris,
Maybe the API-Examples plugin is interesting for you. There you will find all kinds of HTTP commands with which you can control your Max2Play devices and also build automations.
Apart from that, Max2Play can be shut down like other Linux systems with the SSH commandsudo shutdown.14. Dezember 2021 at 15:08 #51844Hi Joe,
Please check if your usb drive is displayed in the „Filesystem/Mount“ tab and if you can save the path there. If this works, scan the path to which the stick was mounted to again.
14. Dezember 2021 at 15:05 #51843Hi Julz,
The basic installation of Max2Play is not affected by Log4j. However, if packages are subsequently installed that run using Java (and thus usually also use Log4j), then it would theoretically be possible that there is a security risk, provided that the device and the service can be accessed via the Internet.
However, this is very unlikely – the most common targets will be popular programs among end users.
7. Dezember 2021 at 12:53 #51837No problem 🙂 I’m glad you found a solution. And I didn’t come up with the solution either, so thank you for sharing it with us.
7. Dezember 2021 at 12:46 #51836Hi Michael,
You may need to reinstall Jivelite or reset its settings via the Max2Play webinterface and possibly delete the $HOME/.jivelite directory in order for Jivelite to work with your dongle.
2. Dezember 2021 at 14:16 #51821Hallo funki,
du solltest die Plugin .tar-Datei unter folgendem Link herunterladen können:
https://drive.google.com/file/d/0ByiPGL04pWjpcjB2djVORE95Zms/view?usp=sharing&resourcekey=0-9nviHTpV81FVeBlht7dTZA
Du kannst Sie anschließend über „Install from local file“ auf der Seite Einstellungen/Reboot auf deinem Max2Play Gerät installieren.2. Dezember 2021 at 14:00 #51820Hallo Benjamin,
Bei so unregelmäßigen Absturzzeiten ist es relativ schwierig, eine Ursache auszumachen. Könntest du hier mal die Debug Info des Spotify Connect Plugins posten? Nutzt du noch andere Plugins parallel auf den Pis? Ich könnte mir vorstellen, dass sie teilweise überlastet sind, sofern noch Dienste wie der Squeezebox Server parallel laufen. Hast du auch Squeezelite und Shairport deaktiviert? Schau am besten mal, wenn Spotify Connect wieder abstürzt, ob im Health Checker unter „Einstellungen/Reboot“ ersichtlich ist, ob der Player überlastet ist.
Hast du deine Max2Play Systeme vor der Installation von Spotify Connect geupdatet? Falls nicht, wurden ggf. nötige Updates von Spotiy Connect nicht bezogen. In diesem Fall würde ich dir empfehlen, ein Update durchzuführen und Spotify Connect im Anschluss noch einmal zu installieren. Die aktuellste Version von Max2Play ist 2.54.25. November 2021 at 16:36 #51813I tested the whole thing again with your setup (and an iPhone 7). It worked for me that Airplay interrupts the playback of Squeezelite. And this is exactly what should happen when you enter the server IP in the advanced settings of Shairport. If you stream music via Squeezelite and then connect the player via Airplay and start playback, the Squeezelite stream is interrupted by Airplay. If you then stop Airplay again, Squeezelite playback should resume. However, it is not possible to interrupt Airplay playback with Squeezelite.
When exactly do the dropouts occur? When you change the playback source? Or generally when you stream via Airplay? Are there any error messages in the server log file? You can find the log under Settings/Information.
25. November 2021 at 14:54 #51812Sofern der IQaudIO DAC Pro eine GPIO Leiste hat, sollte das funktionieren. Der Hersteller des Power Management Moduls empfiehlt dann die Nutzung eines 7-9V Netzteil mit mindestens 2,5A.
Am besten du schaust mal in folgende Aufbauanleitung: https://www.max2play.com/7-zoll-touchscreen-display-im-metallgehaeuse-mit-raspberry-pi-und-soundkarte/
Unten auf der Seite findest du ein Schema, wie der Power Button, Power Management Modul und IQaudIO verbunden werden müssen. Ansonsten findest du dort auch weitere Infos zur Verwendung des Power Management Moduls und Installation des Buttons.25. November 2021 at 14:18 #51811Hi Michael,
In this case, you could add the command
sudo modprobe rtl8192cuin /etc/rc.local beforeexit. This way the command will be executed when the Pi starts up.23. November 2021 at 18:06 #51807Hallo funki,
der Link ist tatsächlich tot. Ich werde mal sehen, ob ich das Community-Mitglied erreiche, welches das Plugin erstellt hat. Vielleicht kann er/sie uns einen neuen Host-Link zur Verfügung stellen.
23. November 2021 at 18:04 #51806Hi Dave,
I have tested the automatic switch of Squeezelite and Shairport again and could not reproduce your problem. Instead, however, I came across another one: If I start playback via Squeezelite while a stream via Shairport is running, the Shairport stream does not stop but continues to run and the two streams overlap. The same applies vice versa.
I will discuss the whole thing again with our developer and hopefully be able to offer you a solution afterwards.19. November 2021 at 14:23 #51802Unfortunately, I can’t really tell you if you’re missing something, as I’ve hardly had any contact with the plugins so far. This sounds like a very Squeezebox Server-specific problem.
I think it would be best for you to post your question again in the slimdevices forum. There you can directly contact the developers of the Squeezebox server (and possibly the plugins). Maybe they have another idea and can better assess what is possible and what is not. From the sound of it, however, you seem to have already found the limits of the plugins.I don’t think it is possible to define two separate libraries for two players. One does not affect the other. However, I could imagine that it is possible to create two libraries and then, depending on where you want to listen to which library, select one of the two players and after that the desired library.
If you have a Squeezebox server and two players running on the network, you can enter the IP address of the server in the advanced settings of the players. This should make the recognition of the players very fast.
19. November 2021 at 14:04 #51801Hi fdmanlondon,
Unfortunately, I could not reproduce your problem. Please perform a Max2Play update again. To update the Remote Control Plugin to the latest version, it is necessary to perform the Max2Play update after adding the plugin. Then please try to install ShellInABox again. If that still doesn’t work, I’m afraid you’ll have to burn a fresh image and test it again.
19. November 2021 at 13:51 #51800Nothing more specific is planned yet, but I think the service would be an enrichment for Max2Play. Therefore, I am confident that we will be able to offer a plugin for Tidal Connect at some point in the future. I will approach our developer about this.
19. November 2021 at 13:42 #51799Hi Dave,
You don’t really need Squeezelite to stream Airplay. Shairport should be sufficient for that. The best thing to do is to try removing Squeezelite from the autostart and stop it so that the two don’t get in each other’s way.
Apart from that, you could also try using plugins for the Squeezebox server to get Airplay to work. Here you can find more information about the possibilities: https://www.max2play.com/en/how-tos/howto-airplay-with-max2play/19. November 2021 at 13:35 #51798Ok, apparently there is no installation from MrEngman for this driver.
Maybe this forum post will help you: https://forums.raspberrypi.com/viewtopic.php?t=264202 A similar problem is discussed there. You may need to modify the /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf files to make your dongle work.16. November 2021 at 15:40 #51791Hallo Hausbaer,
leider bieten wir aktuell keine Lösungen, den Power Button und Rotary Encoder zusammen mit dem HiFiBerry Amp2 zu nutzen. Der Power Button wird aktuell von uns nur für den Audiophonics I-Sabre und das Power Management Modul unterstützt. Gleichermaßen kann der Rotary Encoder nur mit IQaudIO oder Justboom Karten verwendet werden. Die Karten von HiFiBerry blockieren leider wichtige GPIOs, die zur Verwendung der Teile benötigt werden. Hier findest du mehr zur Belegung der Pins von HiFiBerry: https://www.hifiberry.com/docs/hardware/gpio-usage-of-hifiberry-boards/
Ich möchte trotzdem nicht ausschließen, dass es Lösungen für dieses Setup gibt. Vielleicht finden sich ja Nutzer, die diese Komponenten bereits erfolgreich zusammen betreiben. Ansonsten würde ich dir empfehlen, dich auch noch in anderen Raspberry Pi Foren umzusehen, ob dort Ideen geteilt wurden.16. November 2021 at 15:22 #51790Hi Joe,
Sounds like a great project!
How does the Multiple Library Plugin not meet your requirements in this case? Shouldn’t it be possible to create several libraries with this? Do I understand correctly that your current workaround is to use two Squeezebox Servers in the network?16. November 2021 at 14:31 #51789Hi Michael,
Please follow these steps:
1. connect dongle and LAN cable to Pi, boot up
2. install the Remote Control Plugin
3. install „ShellInABox“ in the Remote Control Plugin
4. click „Open Console Fullscreen“
5. login: pi; password: max2play
6. execute the following commands in this order:
–sudo wget http://downloads.fars-robotics.net/wifi-drivers/install-wifi -O /usr/bin/install-wifi
–sudo chmod +x /usr/bin/install-wifi
–sudo install-wifiif that doesn’t work, try:sudo /usr/bin/install-wifiyou should see that the driver for your dongle has been recognised and installed
–sudo reboot
7. after reboot disable the integrated Wifi in the Raspberry settings (then reboot again)
8. set up Wifi and activate WLAN interface
9. at the top of the Wifi plugin you should see „active“ twice as well as an IP address
10. shut down the Pi, disconnect the LAN cable and reboot
11. the Pi should connect to the router via WLAN.Does that solve your problem?
11. November 2021 at 14:27 #51783Hi lektoren,
The hash mark probably means that this line has been commented out. Which version of Max2Play are you using? HD-idle should work in the current version.
11. November 2021 at 14:22 #51782Hi Joe,
Please perform a Max2Play update. Afterwards, the available LMS versions should be visible and installable again. You can find the update button in the „Settings/Reboot“ tab.
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“.
4. November 2021 at 14:54 #51776Hi maxhome,
No, this should not be normal. I assume you get the message „la platine est introuvable“? This means that no player was found. However, you write that your Squeezelite player was recognised by the server, which surprises me.
You could try entering the following in the advanced options of Squeezelite under „Command line options“:
-s <IP-Address>where <IP-Address> should be replaced with the IP address of the server (which is probably 127.0.0.1).4. November 2021 at 14:26 #51775I am very sorry. I do not know what I have read there.
Nevertheless, the internal Bluetooth can be disabled via the Raspberry settings. Apart from that the BT dongle should be detected automatically. The error with hci up could be caused by an outdated kernel. Maybe a kernel update (also available via the Raspberry settings) will help.
4. November 2021 at 13:47 #51774There seems to be a third party plugin called „Play WMA“ for ffmpeg, which you can activate in the settings of the Squeezebox server. Please check if the playback of WMA files works with it.
4. November 2021 at 13:37 #51773Bitte aktiviere mal in den Server Einstellungen das Debugging für „network.cometd“. Du findest diese Option unter Einstellungen/Erweitert/Protokoll. Bitte prüfe anschließend – sobald der Fehler wieder auftritt – ob noch mehr Informationen in der Log Datei stehen.
Nutzt du das Webinterface des Squeezebox Servers um deine Musik zu steuern oder nutzt du einen anderen Controller (z.B. eine App)?
Damit du schneller zu einer Lösung kommst würde ich dir empfehlen, die Frage auch nochmal im slimdevices Forum zu stellen. Dort kannst du direkt mit den Entwicklern des Squeezebox Severs in Kontakt treten.
1. November 2021 at 16:37 #51764Hi Clarenze,
You can deactivate the built-in Wifi in the Raspberry settings. Your wifi dongle may still need a suitable driver. You can install it with the following commands, provided your dongle is connected and recognised by the system:
sudo wget http://downloads.fars-robotics.net/wifi-drivers/install-wifi -O /usr/bin/install-wifi
sudo chmod +x /usr/bin/install-wifi
sudo install-wifiRestart your system afterwards.
1. November 2021 at 14:19 #51763Könntest du mal überprüfen, welches Gerät bei dir die MAC-Adresse 00:04:20:26:5f:ea hat? Dieses scheint nicht mehr erreichbar gewesen zu sein, woraufhin der Server einen Reconnect eingeleitet hat.
-
