Forum Replies Created
-
22. März 2022 at 13:40 #52146
Hi Hans,
I’m afraid that’s not possible. You probably need two devices. Nevertheless, I would test it again myself when I get back to the office and let you know if it works or not.
16. März 2022 at 13:05 #52140Hallo Markus,
falls sich hier niemand findet, der damit bereits Erfahrung gemacht hat, würde ich dir empfehlen, die Frage noch einmal im slimdevices Forum zu stellen. Dort kannst du direkt mit den Entwicklern des Squeezebox Servers in Verbindung treten. Wenn du darüber eine Lösung findest, würden wir uns freuen, wenn du sie auch hier posten würdest.
Wo genau liegen denn deine Bilder, die du als Cover verwenden möchtest? Was passiert, wenn du hinter icon den Pfad zu den Bildern angibst?
15. März 2022 at 16:53 #52138Hi Hans,
Yes, you should get the phono signal to line level with a preamp beforehand. See the ADC datasheet for more information on what is supported: https://www.hifiberry.com/docs/data-sheets/datasheet-dac-adc-pro/
15. März 2022 at 16:44 #52137Das könnte tatsächlich die Ursache des Problems sein. Bitte probier mal separate Images auf die SD-Karten zu schreiben und richte diese unabhängig voneinander ein.
15. März 2022 at 16:42 #52136Hi Ramses,
Theoretically, Bluetooth should be backwards compatible. Accordingly, the Charge 5 should work at least as well as the Charge 4. Nevertheless, we cannot exclude that there might be a configuration/version problem. I have not found anything on the Github page of Bluealsa – the service we use for Bluetooth. But maybe you can find a hint that will help us: https://github.com/Arkq/bluez-alsa
Can you try how far away you have to move the Charge 4 from the Pi before the connection quality drops? It might be possible to solve the problem with an external Bluetooth stick, as the Pi Zero uses one chip for Bluetooth and Wifi and they can get in each other’s way sometimes.
15. März 2022 at 16:04 #52134Hi Chris,
Unfortunately, I saw your message here too late. I tried to answer your questions in an email. If you want, we can continue the conversation here.
15. März 2022 at 16:00 #52133Hi gbader2,
It is not intended to have WLAN and LAN running in parallel, that makes no sense. If you want to connect your Pi via LAN, it is best to turn off the WLAN interface.
The error messages seem to be incorrect when you say that the mounts are reachable. It may be that a connection cannot be made at boot time, but is made later. So you don’t have to worry about that as long as everything works.
15. März 2022 at 15:54 #52132Hi Daniel,
We currently do not plan to actively support Pirate Audio products. But as Heiner already said, they use the normal HiFiBerry driver. Here you can find information about the configuration: https://github.com/pimoroni/pirate-audio
And here is explained how to install the display: https://github.com/pimoroni/st7789-python
However, we can’t guarantee that this will work with Max2Play, as we can’t test it ourselves.
28. Februar 2022 at 15:06 #52108Hi Jack,
Our drivers do not support the input from the DAC DSP. For this you would have to manually install the appropriate drivers and create a DSP profile. A simpler way with Max2Play would be the HiFiBerry DAC+ ADC. The analog input from the ADC is supported by us and can be used with the Wave Input plugin of the Squeezebox Server.
More information can be found on the HiFiBerry page: https://www.hifiberry.com/docs/data-sheets/datasheet-dac-dsp/
28. Februar 2022 at 14:44 #52107Hi Paul,
It looks like you have multiple Squeezebox servers on your network. Is there a server running on „Owner-PC“?
To transfer a player from one server to another you have to click on the player (which is located on server 2) via the web interface of server 1. You will then be asked whether the player should be transferred to server 1. If you click OK, the assignment of the player changes and you should be able to synchronise all players on server 1.28. Februar 2022 at 14:36 #52106Normalerweise sollten die verschiedenen Squeezelite Instanzen alle im LMS sichtbar und auswählbar sein. Dass Squeezelite im Audioplayer Tab läuft sollte normal sein, das ist einfach ein Anzeigefehler, der durch Multisqueeze verursacht wird. Startet Squeezelite auch automatisch, wenn du Multisqueeze aus dem Autostart nimmst? Falls ja, könnte hier doch ein Problem vorliegen, dass womöglich auf den Schreibschutz zurückzuführen ist.
Laufen in deinem Netzwerk mehrere LMS? Fall ja, könnte vielleicht auch hier die Ursache für das Playerproblem liegen.
28. Februar 2022 at 14:25 #52105Interesting setup! Of course, the control via Kodi/Yatse makes the whole thing a bit difficult, but in principle your plan should work. I can’t really think of any alternative you could try either. Except, of course, to leave Kodi out of the music streaming ;), which I would recommend, as you have a much more stable system that doesn’t depend on an unreliable Bluetooth connection.
24. Februar 2022 at 13:48 #52095This sounds more like a Kodi problem. Have you edited the CEC mapping in the Kodi settings?
24. Februar 2022 at 13:41 #52094Can you describe your setup in more detail? I don’t quite understand why you are setting up a Bluetooth connection between two Pis. Perhaps your project can be solved in another way.
Theoretically, it is possible to transmit the Bluetooth input to several players via the LMS, yes. How reliably the whole thing works (especially regarding latency) depends on the BT connection.24. Februar 2022 at 13:32 #52093Which image is installed on your SD card? Are you already using our new Buster Imager? You can find this information at the bottom of the debug info on the „Settings/Reboot“ page. If you are using an older image such as the Jessie or Wheezy image, please consider burning our latest Buster image to the SD card and rebuilding your system. If playback still does not work then, there is probably a hardware defect.
24. Februar 2022 at 13:09 #52092As long as our Buster image is installed on the SD card, the other images should also work with the faulty system. By the way, have you tried our new Beta Buster image? Maybe that will solve the problem.
23. Februar 2022 at 15:56 #52088Grundsätzlich nicht, es gibt aber für den Bluetooth Dienst den wir nutzen (bluealsa) eine entsprechende Dependency, die aptx-Support ermöglicht. Diese ist standardmäßig bei uns allerdings nicht installiert und müsste manuell hinzugefügt werden. Hier dazu das git-Repository: https://github.com/Arkq/bluez-alsa
Bei der Installation können wir dir leider keinen Support anbieten, werden aber mal intern besprechen, ob wir die Dependencies zukünftig standardmäßig integrieren.23. Februar 2022 at 14:38 #52086Hi ih8gates,
Please try setting the sound card to „none“ in the HiFiBerry plugin and then reboot your system. Then select the Amp2 again and restart the system. Then in the advanced options of Squezeelite the audio output should be set to „sysdefault…hifiberry_dacplus“. Now restart the server and wait until the player is displayed. Does the audio output then work again?
23. Februar 2022 at 14:34 #52085Hi Paul,
Have you ever tried to use one of the other SD cards of your Pis with this system? I could imagine that it is due to the SD card. Is it the same model/size as for the other Pis?
23. Februar 2022 at 14:26 #52084Hallo rolli,
wir werden die neue Kodi Version zeitnah testen und in unser Beta Image integrieren sobald alles läuft.
23. Februar 2022 at 14:21 #52083Hi Quebrantahuesos,
Normally Squeezelite should autostart anyway. This can sometimes take up to two minutes. Does the autostart work if you wait a little longer after Kodi has stopped?
What have you set in Squeezelite’s advanced options for audio output and command line options?23. Februar 2022 at 14:15 #52082Hi Hogo,
The SD card write protection is only intended for very special use cases. Functionality errors could occur in combination with, for example, the Squeezebox Server or Kodi. This is because these services may need to be able to temporarily write to the SD card in order to run correctly. Therefore, we recommend using the SD card write protection only in special cases.
In principle, the Zero W should work with Bluetooth. However, the Wifi and Bluetooth modules get in each other’s way. Even with a Pi 3, we found that either WiFi or Bluetooth did not work optimally when both were used at the same time. Therefore, I would not rule out the possibility of such connection errors occurring with a Zero W.
Adding repositories via the web interface should have the same effect as adding them directly in Kodi. However, we haven’t touched this feature for a long time, so it may be that there are problems with the new versions of Kodi by now. Adding the repos within Kodi should work in any case.
23. Februar 2022 at 14:04 #52081Ich habe das Ganze nochmal getestet (zugegebenermaßen ohne Soundkarte, aber das Prinzip sollte das Gleiche sein). Bei mir hat der direkte Stream problemlos funktioniert. Es wäre zu überlegen, ob du das Ganze vielleicht auch nochmal ohne Soundkarte probierst.
Mein Vorgehen:
1. Bluetooth installieren, Handy koppeln
2. Bei Squeezelite die Audioausgabe überprüfen. Sollte die Standardeinstellung sein, bei der du auch Sound z.B. über Internetradio ausgeben kannst. In dem Fall ohne Soundkarte: sysdefault – bcm2835 Headphones
3. Bluetooth Speaker starten mit Sound Device „Headphones“
4. Spotify Wiedergabe auf dem Handy starten –> Soundausgabe über den Klinkenanschluss des PiKannst du das in deinem Setup bitte nochmal nachvollziehen? Prinzipiell hast du bei der Einrichtung meiner Meinung nach nichts falsch gemacht. Vielleicht gibt es hier aber irgendein Problem mit Soundkarte und Bluetooth, womöglich in Zusammenhang mit dem neuen Kernel.
23. Februar 2022 at 13:23 #52079Super, dass du die Lösung gefunden hast 🙂 Vielen Dank auch für das Teilen der Befehle.
23. Februar 2022 at 13:20 #52078Hast du bevor sich der Server regelmäßig aufgehängt hat ein Update des Servers vorgenommen? Falls ja, ist dieses Update vielleicht nicht korrekt durchgelaufen. Zumindest scheint es da wirklich Probleme mit einem zweiten Server zu geben. Schau bitte mal in die /etc/init.d. Wird dort sowohl ein „squeezeboxserver“ als auch ein „logitechmediaserver“ gestartet? In diesem Fall lösche mal den alten „squeezeboxserver“ aus der Datei und schau ob das schon Abhilf schafft. Ansonsten würde ich dir raten, den Server noch einmal komplett vom System zu löschen und neu zu installieren.
23. Februar 2022 at 13:09 #52076Hallo Daniel,
ja, das sollte kein Problem sein. Nutze dazu einfach unser Bluetooth Plugin und stelle die Soundausgabe bei Squeezelite auf Bluetooth. Eine Anleitung dazu gibt’s hier: https://www.max2play.com/en/wiki/using-the-plugin-bluetooth/
23. Februar 2022 at 13:07 #52075Hi sfraser,
In principle, this is no problem with Max2Play. As you say, Jivelite would be an option. Jivelite is used to visualise and control audio playback. In addition, you could simply open the server’s web interface on the Pi and display the playback there. But Jivelite visualisation is a bit more optimised for touch screens or televisions.
You can see what the output could look like in this blog post below „Jivelite and Kodi“:
Step-by-Step Multiroom Audio Setup with Max2Play – The Living Room
15. Februar 2022 at 15:29 #52056Unfortunately not, no. We are not currently planning to make Max2Play compatible with Alexa, as we do not have the capacity for this effort. Especially since there are workarounds for integrating Max2Play into an Alexa environment.
15. Februar 2022 at 15:04 #52055Yes exactly, this way you can use your Pis as Kodi players and output the audio directly through each sound card.
15. Februar 2022 at 15:01 #52054Please try to operate the system with a „normal“ power supply unit and disconnect the Ethernet connection during operation. Does the reconnect work there? If so, there is some problem with the pijuice. If not, please try to burn a new image onto the SD card and try everything again.
-
