Heiner

Forum Replies Created

Viewing 30 posts - 2,581 through 2,610 (of 4,111 total)
  • Posted in:
  • 26. Oktober 2017 at 12:28 #32120

    Sorry, I failed to mention that we only just added this option by request in our newest beta.

    So you currently need a beta updated device to run the chinese language option.

    The addition will be available in the next official update as well.

    26. Oktober 2017 at 12:26 #32119

    Hi tom,

    Sounds perfect, you should not run into any trouble from this point on.

    Enjoy Max2Play 😉

    25. Oktober 2017 at 15:22 #32105

    Hi lemuba,

    Just to clarify, you need to connect one Pi via HDMI to the beamer AND the sound card on the same Pi to your speakers. Then, you can select the audio output for your sound card in Kodi and have the HDMI output be to the beamer. That should allow your setup to work with just one Raspberry Pi.

    25. Oktober 2017 at 15:19 #32103

    Again, sorry about the late confirmation. If you have any issue with the alternative solutions, or need further assistance in realizing your specific project, let me know.

    25. Oktober 2017 at 15:13 #32102

    Hi dixon,

    First of all, check in Settings/Reboot under „language“, whether you have „chinese“ selected. This allows for Chinese characters to be recognized in Max2Play.

    25. Oktober 2017 at 15:00 #32101

    Hi tom,

    Did you try another SD card, yet? You can keep track of the CPU and SD card usage in the health checker in Settings/Reboot.

    Please check that output when the activity LED is blinking continuously.

    Also, please make sure your card is a Class 10 or higher speed class to ensure Max2Play working optimally.

    25. Oktober 2017 at 10:59 #32095

    Hi okenny,

    A few plugins need access to the SD card and make the write protection inoperable. The Squeezebox Server is one such example.

    Which plugins are you using on the raspi in question?

    25. Oktober 2017 at 10:57 #32094

    Hi Muchacho,

    Bitte versuche noch ein anderes Endgerät an den Pi anzuschließen, um einen Hardwaredefekt auszuschließen. Falls dies auch nicht in Erfolg endet, versuche bitte ein frisches Image zu brennen (du kannst dein altes als Backup mit unserem Image Burner Plugin sichern) und die Ersteinrichtung wie folgt vorzunehmen:
    – Wähle aus dem Pop-Up „HiFiBerry“
    – Wähle aus dem Dropdown den Digi+
    – Wähle „Erweitert“ als Option
    – Versuche mit dem LMS (Installation 7.9) einen Radio-Sender abzuspielen

    25. Oktober 2017 at 10:52 #32093

    Hi mini,

    Habe gerade mal ein neues gespeichert und als SambaShare gecheckt. Ein default image von Max2Play (auf einer 8 GB Karte) ist nach lesen, zippen und speichern 1,07 GB groß auf der SD-Karte des Image Burner Pi’s gespeichert.

    25. Oktober 2017 at 10:50 #32092

    Hi sf,

    Unfortunately, this issue is not resolved, yet. We are working on a fix for the next version of Max2Play.
    Bluetooth connectivity is problematic as there are a huge variety of end devices used with varying technologies used. But we are looking into what might cause the issues on a general level and whether there are any measures to reduce the occurrence of dropouts.

    25. Oktober 2017 at 10:38 #32089

    Hi Richard,

    Sorry about that, I dug out our XU4 to check and these features are indeed Raspberry Pi exclusive.

    Thank you for pointing us toward this issue. I will amend our documentation to clearly point these features out as Raspberry Pi content.

    However, you can recreate DLNA players with the Squeezelite player and the LMS. For file sharing through the network, I would recommend setting up a SambaShare.

    25. Oktober 2017 at 9:44 #32088

    Hi wimvans,

    We are not really familiar with Roon, so I have to ask whether you installed the Squeezebox Server and checked whether you can play a random radio station from the Logitech Media Server interface. Please install version 7.9, if you have not done it, yet.

    Also check the advanced options of the Squeezelite player to make sure that the sound card selection for output has „…hifiberry…“ in its name. (Should be „sysdefault[…]hifiberry[…]“)

    25. Oktober 2017 at 9:39 #32086

    Hallo geloe,

    Danke für die schnelle Rückmeldung. Es freut mich zu hören, dass es jetzt funktioniert. 🙂

    25. Oktober 2017 at 9:30 #32084

    Hi okenny,

    For your player Pi’s, you can use our write protection plugin.

    Further, you can add shutdown commands for all devices as http-requests (shown in the voice control beta plugin) to safely shut down any systems you want to remove from their power supply.

    This should add a lot of longevity to your SD cards. We have devices running here for multiple years, nearly without any interruption.

    Another important factor is the speed and quality of the card itself. We recommend using nothing below Class 10.

    24. Oktober 2017 at 14:06 #32071

    So, there is no device in your router’s list named max2play? If so, you need to burn a fresh image as this one does not seem to boot correctly.

    24. Oktober 2017 at 14:05 #32070

    Hi feeder,

    Aktiviere ggf. hotplug in den Raspberry Einstellungen. Wenn das HDMI-Kabel beim Hochfahren des Pi nicht angeschlossen war, wurde kein Desktop erzeugt.

    24. Oktober 2017 at 14:04 #32069

    Hi Axel,

    Thanks for the feedback! We will look into Snapcast’s environment and specs to see whether it would indeed be a worthy successor of the fan favorite Squeezebox.

    In the community, Squeezebox development is still rather active. The Spotty plugin for Spotify (+Connect) is a great example, but there are also great DIY solutions Google Music and Qobuz that are already working with Max2Play.

    24. Oktober 2017 at 13:52 #32068

    Hi anttiautio,

    Thanks for pointing out this issue. we will look into possible options to fix it in the future. If you have any concrete ideas, please also let us know.

    24. Oktober 2017 at 13:12 #32066

    Hi Veryaner,

    There are a few issues with this idea. For several reasons, it is much more practical to just get another Pi for a second Bluetooth speaker pairing. This will also result in a much reliable multiroom system, as the different Bluetooth pairings will not interfere as much with each other.

    Generally, we recommend using as few players on each Pi as possible to reach the best results both in sound quality and in resilience to outside factors (e.g. bad Bluetooth signals, adapters, protocols).

    24. Oktober 2017 at 13:08 #32065

    Hallo gcg67,

    Das von jonathan86 geteilte Bild ist ein Konzept, was er soweit ich weiß nicht realisiert hat.

    Der Ort wo man eigene Jivelite Skins anfügen könnte findest du oben in meinem Post verlinkt.

    Zweite Frage: Das sollte machbar sein, wird aber grundlegende Linux-Kenntnisse erfordern. Max2Play ist aktuell basierend auf Raspbian Jessie lite. In Max2Play’s Raspberry Einstellungen kannst du bereits den Browser Iceweasel (Firefox-basiert) installieren und den Desktop auf No-Sleep Mode setzen.

    24. Oktober 2017 at 13:00 #32064

    Hi the1ne,

    Which software are using the smart remote with? Are you referring to the JustBoom smart remote?

    24. Oktober 2017 at 12:52 #32063

    Hallo Wolfgang,

    Falls du es noch nicht versucht hast, bitte folge diesen Schritten: https://www.max2play.com/howtos/howto-spotify-einrichten/

    Die Authentifizierung von Spotty sollte über eine App laufen und nicht mit Login-Daten in den LMS-Einstellungen.

    24. Oktober 2017 at 12:50 #32062

    Hi Nojelc,

    We currently do not offer new ready packages of Kodi for Odroid. But please try check another HDMI cable to rule it out as a source of error.

    Furthermore, you can try starting Jivelite GUI to see whether the same error is reproducable in another software.

    24. Oktober 2017 at 12:48 #32061

    Hi wim,

    First of all, thanks for the support. It’s much appreciated.

    To your issue, please check whether your selection of the HiFiBerry AMP2 is also set in Squeezelite, in the Audioplayer menu. Furthermore, you should have volume sliders in the HiFiBerry menu. Also, please remove the autostart from Shairport to rule it out as a source of error and remove the tick from the Access Point Autostart Mode in the WiFi/LAN menu.

    24. Oktober 2017 at 12:45 #32060

    Hi Richard,

    Sorry about that, the binary ishould be located at /usr/local/bin/gmediarender

    24. Oktober 2017 at 12:38 #32059

    Hi Hydro,

    Please check the Access Point Autostart Mode and make sure it is deactivated (remove tick in WiFi/LAN menu).

    24. Oktober 2017 at 12:37 #32058

    Hi geloe,

    Blieb dieses Problem bestehen oder hob es sich auf nach dem Neubrennen?

    Normal sollte Spotty sowohl vorinstalliert sein, als auch mit einem Klick aktivierbar.

    24. Oktober 2017 at 12:35 #32057

    Hi lemuba,

    Should work with Kodi -> System -> Service Settings -> enable DLNA or AirPlay -> stream video stuff

    I just tested with RPi3, Kodi 17.4 and UPnP/DLNA via Android using AllConnect, should work the same with AirPlay, your device shows up as „max2play (kodi)“

    24. Oktober 2017 at 12:15 #32056

    Hi okenny,

    What login did you try? user: pi pw: raspberry with default RPi image

    Have you tried accessing the web interface with the device’s IP from your router’s web interface?

    24. Oktober 2017 at 12:12 #32055

    Hi Toxiro,

    Thanks for sharing these issues. We will try to address them in our next release.

Viewing 30 posts - 2,581 through 2,610 (of 4,111 total)