Forum Replies Created
-
-
27. Juli 2017 at 12:48 #30201
Hi Duschcaptain,
Hast du IPv6 deaktiviert in den Raspberry Settings?
Hast du Squeezelite gleichzeitig laufen? Falls ja, wähle bitte ein anderes Ausgangsgerät für Squeezelite und nehme es vom Autostart um es grundsätzlich als Fehlerquelle auszuschließen.
Gehe bitte außerdem sicher, dass du Version 2.44 von Max2Play nutzt. Wir haben im letzten Update einen Bug in der librespot Implementierung gefixt.27. Juli 2017 at 12:45 #30200Hi TroLoo,
If not selected already, please select the Output device „sysdefault:CARD=sndrpihifiberry – snd_rpi_hifiberry_amp, – Default Audio Device“ in Squeezelite.
Please also check out our Wiki on optimizing Squeezelite to find out the command line options which should fix this issue: https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/
With your HiFiBerry Amp+ it should be:
-o hw:0 -V Master27. Juli 2017 at 12:37 #30199Hallo Steini,
Ich weiß nicht weshalb dir diese Version vorgeschlagen wird. Wenn du den Menüpunkt „7.9“ im Squeezebox Server Menü auswählst, sollte in der Quell-Zeile diese Version und URL stehen: http://downloads.slimdevices.com/LogitechMediaServer_v7.9.0/logitechmediaserver_7.9.0_arm.deb
Und nach der Installation im Debug Info und im Webinterface des SBS diese Version: v7.9.0, 1488878280
26. Juli 2017 at 15:04 #30172Hi Ronnie,
Unfortunately, we do not have this DAC to recreate your issue. Have you checked it on another end device to make sure its not a hardware problem?
26. Juli 2017 at 13:55 #30166Hi Dave,
What audio output do you have selected in Audioplayer menu?
Also, common issues you can avoid:
– Deactivate Bluetooth if running and built-in audio. According to HiFiBerry, it might interfere with their cards.
– Check out our tips for sound optimization: https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/
– Try using LAN instead of WiFi, it sometimes decreases the sound quality: https://www.max2play.com/forums/topic/higher-bitrate-songs-freezing-lms/#post-2611326. Juli 2017 at 12:47 #30165Hi Carsten,
Have you tried using our LIRC implementation in the Raspberry Settings?
Just enter the GPIO’s of your IR sensor and tick the box. Afterwards click save and reboot.
25. Juli 2017 at 12:47 #30131Hi Carsten,
What setup are you using and what steps have you taken so far?
25. Juli 2017 at 12:45 #30129Thanks for the follow-up, Rolf. Glad you got it working 🙂
25. Juli 2017 at 12:42 #30127Hi fabien,
This is our official stance on the use of the Kali Reclocker:
The Kali Reclocker can only be combined with DACs running in Slave Mode. The cards of our partners HiFiBerry, IQaudIO and JustBoom all run in Master Mode. Consequently, the Kali can not be connected with these cards without major manual changes. Thus, we recommend the Kali Reclocker in combination with the Piano DAC 2.1 in our Shop. This combination works, as usual with Max2Play, directly out-of-the-box.We love the device in combination with the Piano DAC and recommend anyone interested to get it.
The Sparky Board is not an officially supported device of Max2Play’s. Please contact allow on the software possibilities of the Sparky SBC.
25. Juli 2017 at 11:41 #30122Hi OJ,
What sound output do you have selected in the Audioplayer menu of Squeezelite (advanced options)?Also, did you try selecting „force HDMI“ for audio output in the Raspberry Settings‘ dropdown menu, yet?
24. Juli 2017 at 17:32 #30102Hi fisherman,
We updated the Kodi 17.3 install to include the PVR addons in our newest beta. Just click the beta update on „Settings/Reboot“, head to Kodi’s M2P menu and click „Upgrade to latest version“. Then, you can find the addons in Kodi’s own menus and configure them there.
24. Juli 2017 at 17:29 #30101Hi dongilles,
I just used a fresh install to test it again, successfully.
Please try deactivating all other players momentarily to rule them out as sources of error.
24. Juli 2017 at 17:26 #30100Okay, thanks for clearing this up. The problem with this purported bug, is that amongst the whole community of Max2Play it is only experienced by a few. In addition, the LMS depends on the Pi’s workload in combination with the size and variation of your music libary. These factors first and foremost command the smoothness with which the LMS runs. Also, we recently added support for the new LMS 7.9 and trying to phase out the nightly uses as they can also cause issues.
For most users, there is no problem whatsoever with LMS under Max2Play. For some, a little tweaking of the settings might be necessary. For others, an entirely different issue might be the root problem and can be determined here based on a few questions of mine. Usually, I pride myself on our community’s quick responses and open interaction which results in 99 percent of all issues being solved rather quickly. However, here the issue is more vague. You can check the vitals of Pi when first indexing the LMS with your library in the Settings/Reboot menu. Yet, I assume you are interested in further trouble shooting as seem to have found your solution.
Nonetheless, I would appreciate it if other users could still get the chance to find out their actual issue instead of jumping to another platform. This is always a possible solution, but not one they need to navigate to the Max2Play forums for.24. Juli 2017 at 17:13 #30094Hi Steini,
Mit Quelle bezog ich mich auf die LMS-Installation, da wir aktuell die neue 7.9 Version ohne nightly implementiert und erfolgreich getestet haben. Wir empfehlen, diese zu nutzen anstatt der Version 7.9.1 nightly.24. Juli 2017 at 16:21 #30090Hi guys,
@Matthias: I am not sure what exactly the point of your argument for the PiCore Player is here. The same features are available on Max2Play. It is definitely possible to have two, or several more shairports on one Max2Play device. In fact, we have a premium plugin for just that purpose: https://www.max2play.com/en/portfolio/pluginmultishairport/
@rwanou: The issues with these files are probably related to their specific rights and properties. Please make sure these are standard and do not have special file safety restrictions as this is the cause of 99 percent of all file issues with the Squeezebox system.24. Juli 2017 at 15:57 #30088Hi Richard,
No there is not. Currently, you can shut down the device and safely remove any USB periphery from it and you can remove mass storage devices from the input in Filesystem/Mount with the button „unmount“.
24. Juli 2017 at 15:26 #30086Wir haben jetzt mit unserer aktuellen Beta die PVR Addons ins automatische Skript von Kodi 17.3 implementiert.
Einfach ein Beta-Update durchführen und dann in Kodi auf neueste Version updaten. Danach findest du die PVR-Addons direkt in den Optionen von Kodi 😉
24. Juli 2017 at 15:01 #30085Hi dongilles,
In „Settings/Reboot“ there is an option „Network Lookup“:
Search local Network for other Max2Play-Devices running Squeezelite and display them in the header of this interfaceAfter a little wait, the refresh button should show you an overview of all devices in the top right corner of the web interface.
24. Juli 2017 at 14:33 #30084Hi yokoyoko,
Wir haben das gleichzeitige Nutzen beider Spotify Lösungen noch nicht testen können. Bitte deaktiviere vorerst Spotty um sicher zu gehen, dass dieses nicht die Grundlage des Problems ist.
24. Juli 2017 at 14:09 #30080Hi TroLoo,
Thank you for the kind words, first of all.
Please share the command line options and output device that is selected in your Audio Player menu. Those can tell us what might be wrong with the setup. You might have to add an „hw“ to the options or select a different output.
24. Juli 2017 at 14:08 #30079Hi fisherman10,
Hier findest du verschiedene .deb Installationsdateien, unter anderem Version 16.1: http://pipplware.pplware.pt/pipplware/dists/jessie/main/binary/
Außerdem haben hier noch die originale Version von Kodi 15.1 hinterlegt: https://www.max2play.com/download/15362/
24. Juli 2017 at 13:32 #30078Hi Piero,
You could try this solve from another user: https://www.max2play.com/forums/topic/infrared-remote-for-max2play-rpi-squeezebox/#post-1706024. Juli 2017 at 13:28 #30077Thanks for sharing your solution. We will look into this alternative as well 🙂
24. Juli 2017 at 13:13 #30076Hi jono,
Das Joggler Skin ist ein spezielles Format für die Ausgabe der grafischen Oberfläche des Squeezebox Systems „Jivelite“. Es ist konzipiert für die 7 Zoll Touchscreens von Raspberry funktioniert aber auch mit anderen 7″ Ausgabegeräten. Darin befindet sich unserer Version unter anderem ein Menüpunkt um das System herunterzufahren, eins um direkt zu Kodi zu wechseln, ufm.
20. Juli 2017 at 14:39 #30015Hallo Horst,
Danke für die Info.
Jedoch sollte die Spotify-Steuerung und die AirPlay-Steuerung eigentlich doch immer auf verschiedenen Programmen erfolgen, oder gibt es da eine Überschneidung?
20. Juli 2017 at 14:35 #30014Hallo Steini,
Welche Quelle hast du zur Installation des Servers gewählt? Hast du außerdem bisher den Pi mit LMS über LAN oder WLAN am Laufen gehabt? Falls du ersteres noch nicht probiert hast, tu dies bitte um das WLAN-Netz als Fehlerquelle auszuschließen.
20. Juli 2017 at 14:21 #30013Hi Rolf,
Thanks for pointing this issue out to us. It is connected to your version of the Raspberry Pi not being recognized by the original script.
We were able to recreate the issue and fix it in our current beta. Just click on the beta-update button in Settings/Reboot and try installing the server again.
-
