Forum Replies Created
-
-
8. Mai 2019 at 11:33 #45316
Hi George,
The plugin RPi-Display lets you select the 7″ touchscreen and installs all necessary drivers and configurations to run ideally on Max2Play. You can find it in our extensions overview under Features.
8. Mai 2019 at 11:31 #45315Hallo pokerjung,
Hier noch ein paar weitere Links die dir bei deiner Wunschlösung weiterhelfen könnten:
https://support.hifiberry.com/hc/en-us/community/posts/360001927178-Yet-another-Amp2-Mono-Output-thread
https://support.hifiberry.com/hc/en-us/community/posts/201494532-Use-of-ALSA7. Mai 2019 at 14:28 #45311Vom Raspberry Pi, der HTTP-Befehl ist im API-Exmaples Plugin vermerkt.
7. Mai 2019 at 12:19 #45307Füge bitte bei beiden Playern „-C 5“ in den Kommandozeilenoptionen hinzu.
7. Mai 2019 at 10:30 #45302Update Fix:
There was a conflict with the NEW DigiAmp+’s implementation that we now fixed in the live version of Max2Play. To get this fix on an existing 2.48 Max2Play image, do the following:
– Make a Beta Update
– Make a normal update (optional to get back to default Max2Play 2.48)
– Select „none“ in IQaudIO Plugin
– Reboot
– Select „DigiAmp+“ in IQaudIO Plugin
– RebootThe sound card should now be unmuted again and work as expected.
Anyone updating to 2.48 now, will not be affected by this bug.
7. Mai 2019 at 9:33 #45301Hello Brian,
Have you tried another bluetooth device yet?
Also, how old is your image of Max2Play?
6. Mai 2019 at 15:56 #45290Update: We were now able to reproduce the error, but only with the legacy DigiAmp+ without the protruding terminals. It seems to be an issue with the assigned GPIO22 which does not show up anymore with newer versions of Raspbian. We have contacted IQaudIO and will keep you up to date on the implementation and any potential fixes. For now, stretch images before 2.48 should still work.
6. Mai 2019 at 15:47 #45289Hello ursdiego,
What exactly would hinder an HDMI connection from your Pi to your beamer for picture and the audio output via USBridge to your DAC?
The latency is created between the different interfaces and their exchanging of streams. So, sound to bluetooth (big) latency, through LMS server latency, to end client latency. The amount of latency depends on various other factors as well, connection strength, file types, bit rates, other processes, etc. In general, we recommend running video player solutions directly through the sound card output.
6. Mai 2019 at 15:24 #45288Hallo Günter,
Danke für deine Mühen und für den Tipp bezüglich des 3B+. Wir werden das hier direkt einmal versuchen, nachzuvollziehen.
6. Mai 2019 at 15:03 #45287Thank you for chiming in, Lietho.
I tested with a new image and the NEW IQaudIO DigiAmp+ and could not reproduce your issues. Both playback and the volume sliders (don’t forget to save any changes) worked right after the reboot.
What version of the DigiAmp+ are both you using? I tried with the NEW DigiAmp+ with protruding terminals.
6. Mai 2019 at 14:54 #45286Standen diese Werte nicht im JustBoom Audioplayer? Hast du sie hinzugefügt und dann passierte diese Umkehrung?
Nenn am besten einmal beide Player um in bluetooth und justboom.
6. Mai 2019 at 13:56 #45285Hallo Pi-Friend,
Deine Anmerkung
mein RPi schaltet immer auf die 5 GHz nach dem Neustart, egal was vorher eingestellt warmacht mich stutzig. Max2Play sollte nicht ein Faktor sein, wenn es um solches Verhalten geht. Brenn ggf. ein neues Image falls noch nicht geschehen und guck ob der Pi weterhin 2.4GHz blockiert. Dies dürfte nicht der Fall sein.6. Mai 2019 at 13:45 #45282Hello max,
Do you mean the bug fix does not work? Have you tried it yet and if so what was the error then, same installation problem?
Which version of Max2Play do you have? In Settings/Reboot you can find „stretch“ „jessie“ oder „wheezy“ in the debug info window.
6. Mai 2019 at 13:28 #45281Hello Hans,
Technically, yes. However, we do not have any experience with the Zero’s GPIOs and any hardware periphery on it. You can try connecting the same GPIOs as with the main JustBoom cards but you should probably also consult JustBoom and ask what they recommend.
6. Mai 2019 at 13:26 #45280Hello kingkong,
The latter should not be connected to your AirPlay speakers connection. Can you play via AirPlay to Squeezelite players?
Can you find any further errors aside from this line in the debug?
Also, please try consulting the creator of the plugin, Philippe_44 over slimdevices, I he might have a quicker idea to fix your issue. Here’s the thread
6. Mai 2019 at 13:22 #45279I’ll consult our head developer to see if there’s a feasible way to implement an automatic restart without causing further issues with other player configurations.
6. Mai 2019 at 13:20 #45278It is indeed, as mentioned be recommend using Max2Play’s advanced preset, nonetheless, the starter should obviously work out-of-the-box.
I’ll try to recreate your issue and see if it’s a universal one. Could you detail your steps in Max2Play? When you say you used the default settings, how did you test playback and set up the device initially?
6. Mai 2019 at 13:17 #45277Hello Georg,
Does this faulty behaviour only occur when Jivelite is open or does it also occur in the normal dekstop view?
6. Mai 2019 at 11:47 #45273Hi Brian,
Sorry about that, we indeed fixed this. There was a bug in the connection protocol that we added to the most current beta but should also be included in the new, proper 2.48 update.
For anyone still affected by connection issues (version 2.47 and older), please do the following to fix your bluetooth:
– Head to Settings/Reboot and click the Update Button
– When the update is finished, head to Bluetooth and „Uninstall Bluetooth“
– Refresh the Bluetooth menu if necessary and „Install Bluetooth“
– Reboot after the installation is finishedYour system should now be able to connect to any Bluetooth device again.
6. Mai 2019 at 11:47 #45272For anyone still affected by connection issues (version 2.47 and older), please do the following to fix your bluetooth:
– Head to Settings/Reboot and click the Update Button
– When the update is finished, head to Bluetooth and „Uninstall Bluetooth“
– Refresh the Bluetooth menu if necessary and „Install Bluetooth“
– Reboot after the installation is finishedYour system should now be able to connect to any Bluetooth device again.
6. Mai 2019 at 11:43 #45271Der Link zum Topic ist im Satz verankert.
Eigentlich können keine Restriktionen auf den Ordner in mnt/share sein. Versuche bitte einmal, direkt zu mnt/share zu mounten.
6. Mai 2019 at 11:29 #45270Thanks for following up, could you tell us what skin and resolution you chose for screen now that it works?
6. Mai 2019 at 11:08 #45269Hallo Erik,
Wenn du mit dem Handy auf deine RPi-Soundkarte über Bluetooth wiedergeben möchtest, musst du im Bluetooth Speaker Audioplayer den Output HiFiBerry auswählen. Wenn du als Ausgabegerät Bluetooth wählst, möchte der Audioplayer mit dem Handy auf das Handy wiedergeben.
6. Mai 2019 at 11:04 #45268Thanks for the follow-up, let us know if you get back into it. The „advanced“ setup really is our main expertise and like with the starter, you get set up everything through our web interface. There’s also more tutorials and help documentation than you can read if you want to set up a specific application.
3. Mai 2019 at 14:48 #45243Hi Phanegem,
Sure you can amend the Rotary Control Script accordingly. Just make sure the GPIOs are suited for rotary use and work on your board.
3. Mai 2019 at 14:43 #45242Hallo mini,
In der Regel kommt dieser Prozess nur bei neuen Network-Geräten vor. Teste einmal ob dieser bleibt, wenn du den WiFi-Dongle entfernst.
Außerdem scheint dies vermehrt bei jessie images aufzutreten. Ein neues Stretch-Image wäre also die nächste Option.
3. Mai 2019 at 14:39 #45241Ein Bildschirm sollte immer über HDMI anschließbar sein.
Der Link zum Screenshot ist von einer lokalen NAS (\\nas-01\Web\2019_05_03_Rpi_nach_Neustart.png)
Hat dein Heimnetz irgendwelche Besonderheiten?
Ist das betroffene Gerät ausschließlich über Ethernet verbunden? Wenn ja, was zeigt das Webinterface des Routers bei dem Gerät nach einem Neustart an? Erhält es weiterhin eine IP?3. Mai 2019 at 14:12 #45240Check ob in den Kommandozeilenoptionen des JustBoom Players folgende Werte stehen:
-o hw:CARD=sndrpijustboomd -V Digital3. Mai 2019 at 14:04 #45238Danke für die Rückmeldung und den Log, freut mich zu hören dass es jetzt wieder geht und die App das Problem gewesen zu sein scheint.
-
