Heiner

Forum Replies Created

Viewing 30 posts - 2,761 through 2,790 (of 4,111 total)
1 2 3 … 92 93 94 … 136 137 138
  • Back to forum
    Posted in:
  • Heiner premium
    18. September 2017 at 16:02 #31382

    Hi Muchacho,

    Ich nehme an, du meinst mit alle Einstellungen die Einrichtung über das HiFiBerry-Plugin. Dort hast du „HiFiBerry Digi/Digi+“ gewählt, gespeichert und neu gestartet. Danach sollte in deinem Squeezelite bei „Audio Player“ im Max2Play Web Interface in den erweiterten Einstellungen das Ausgabegerät „sysdefault…hifiberry…“ gewählt sein.
    Falls dies nicht der Fall ist, wähle bitte dieses aus. Falls es nicht gelistet ist, check bitte deine Auswahl im HiFiBerry und Raspberry Einstellungen Menü. Bei beiden kannst du deine Soundkarte auswählen.

    Heiner premium
    18. September 2017 at 15:57 #31381

    Hi shoddy,

    Danke für den detailierten Report, wir werden versuchen das Problem hier nochmal mit einem frischen Image zu rekreieren. Wie weit entfernt ist der Pi von deinem Router entfernt?

    Heiner premium
    18. September 2017 at 15:49 #31380

    Hi Roger,

    Thanks for the update and the detailed log you shared. We will keep testing the newest version and see whether we can recreate them.

    For now you can still make a beta update to get to our newest version.

    Heiner premium
    18. September 2017 at 15:44 #31379

    Hi bollinim,

    You should be able to do so with our MultiSqueeze plugin. Have one Squeezelite running with „sysdefault_hifiberry…“ as output and one Squeezelite (you can create multiple Squeezelite instances with the plugin, as the name suggests) with the USB-DAC output.

    Heiner premium
    18. September 2017 at 15:42 #31378

    Hi motamas,

    Super Entscheidung 😀

    Das Display ist bereits raus an dich.

    Heiner premium
    18. September 2017 at 13:53 #31370

    Hi simi,

    Unfortunately, we have not had any experience with this board, yet. However, you can contact the manufacturer and ask whether it is compatible with the RPi Zero W and if so, what drivers have to be installed. In the meantime, you can check out the WiFi options for the Zero W.

    We offer both WPS: https://www.max2play.com/en/how-tos/how-to-wifi-configuration-with-wps-and-max2play/

    And an Access Point Autostart Mode: https://www.max2play.com/en/2017/08/access-point-autostart-mode/

    Heiner premium
    18. September 2017 at 13:44 #31369

    Hi tom,

    2b) MAke sure your player and server are properly connected in the LMS web interface. You can further go into the LMS settings to check out whether the DLNA plugin runs correctly. For shairport, you can also check out the creators documentation for more info: https://github.com/mikebrady/shairport-sync

    Heiner premium
    18. September 2017 at 13:33 #31367

    Hi Cyn,

    Great! Please keep us updated on your home assistant implementation.

    Heiner premium
    18. September 2017 at 13:32 #31366

    Hi Udo,

    With a fresh installation of Max2Play, you should immediately get the option to select HiFiBerry, HB DAC+ and your player setup in our web interface. The dropdown menu for output device selection should definitely give you options that include „hifiberry“ in the name, these output devices all work with the sound card. Our default and recommended one is „sysdefault…“.
    This is literally what is selected, when you saved your DAC+ as the sound card in use and rebooted.

    We will consider adding a test button for a quick audio check, thanks for the input.

    Heiner premium
    15. September 2017 at 11:52 #31340

    Hi Tom,

    The easiest way to avoid issues with third party software like tuneblade is to use the built-in DLNA protocol that works natively on Windows.

    But we will look into this issue and try to see what might go wrong in this setup. In the meantime, you can try using shairtunes2 plugin for Squeezebox playback to see whether it produces the same issue.

    Heiner premium
    15. September 2017 at 9:37 #31337

    Hi Anthony,

    Both Spotify instances should work on the same Pi. However, make sure that the playback outputs do not overlap as Spotify Connect and Squeezelite are individual players that need individual outputs (e.g. Squeezelite -> sound card output, Spotify Connect -> HDMI output). We are currently working on a Soft-Off feature to allow both players to interact and use the same output, but this is still not ready. Of course, you can also manually start and stop the one you want to use for the output device of your choice.

    With Spotty for Squeezebox, the Login happens with your account for the first and keeps using this login. With Spotify Connect, you also need your own Login to get it started. But then you should be able to use any Spotify app with any account to play to it.

    Heiner premium
    15. September 2017 at 9:32 #31336

    Hi Andreas,

    Sorry, das hae ich wohl überlesen. Aktuell ist das springen im Song leider nicht möglich mit Spotty. MHerger vom SlimDevices-Forum arbeitet jedoch akribisch daran, das Plugin weiterhin zu verbessern.
    Und bei unserem Spotify Connect-Plugin wird jetzt immer die neueste Version von librespot automatisch bezogen bei einer neuen Installation. Du kannst also, falls eine neuere Version raus ist, auf „Reinstall“ klicken und gucken wie die Ausgabe ist.
    Du kannst außerdem versuchen, bei den Command Line Options „–device hw:0“ oder „–device hw:1“ einzutragen. Je nachdem, welchen Slot deine Soundkarte hat (wenn Build-In Audio deaktivier ist, ist es 0, wenn nicht, ist es 1).

    Edit: Du kannst jetzt mit einem Beta-Update die neue Version unseres Spotify Connect Plugins starten. Damit kannst du den Mixer einstellen (Master bei den meisten Amp’s, Digital bei den meisten DAC’s) und hw volume control möglich machen.

    • This reply was modified 8 years, 6 months ago by Heiner.
    Heiner premium
    15. September 2017 at 9:22 #31335

    Hallo Stefan,

    Wenn das WLAN geht, sollte die Verbindung auch Internet liefern können. Gehe dann bitte sicher, dass du den Access Point deaktivierst.

    Heiner premium
    14. September 2017 at 14:00 #31327

    Es scheint noch die LAN-Verbindung forciert zu werden. Bitte versuche, nach der Verbindung und Einrichtung des Netzes einen Neustart durchzuführen. Danach sollte WLAN seine eigene IP erhalten.

    Heiner premium
    14. September 2017 at 13:11 #31325

    Hallo Stefan,

    Die Verbindung sollte in der Tat bei dem ersten erfolgreichen Scan und einhergehender Eingabe des Logins bereits bestehen.

    Kannst du uns genau sagen, bei welchem Schritt du welche Fehlermeldung erhältst, wenn du diesen folgst:

    NEU: Accesspoint Autostart-Mode

    Gibt der Scan dein Heimnetzwerk als Verbindungsoption aus?
    Könntest du außerdem die Debug Info des WLAN/LAN-Menü’s hier teilen?

    Heiner premium
    14. September 2017 at 11:58 #31323

    Hallo Stefan,

    Bitte entschuldige die Verwirrung.

    Die feste IP-Vergabe ist nur für LAN-Verbindung möglich: Setze feste LAN IP-Adresse (eth0): Bei dieser Einstellung muss definitiv der Access Point deaktiviert sein.
    Entferne deshalb bitte auch diese Einstellung, wenn du vor hast das Gerät über WLAN zu nutzen.

    Unser neuer Autostart Access Point Mode erlaubt dir die direkte Verbindung mit dem Gerät ohne im Netzwerk zu sein. Nutzt du diese zum Verbinden? Falls nein, deaktiviere sie bitte direkt unter der festen IP.

    Heiner premium
    14. September 2017 at 11:52 #31322

    Hi macpac,

    Danke für das Feedback, wir schauen uns demnächst an, was für möglich Integrationen sinnvoll wären für Max2Play.

    Heiner premium
    14. September 2017 at 11:50 #31321

    Hi The1ne,

    We are currently not planning to integrate this as a plugin.
    However, there is a rather comfortable option for you to create a plugin with a just a few clicks over our web interface:

    Plugin Pluginbuilder

    Our head developer made a video on how it’s done:

    You can create your install script and just copy the instructions for Raspberry integration in there.

    Max2Play is currently based on Raspbian Jessie lite, so you would need that is compatible with this system.

    Heiner premium
    14. September 2017 at 11:45 #31320

    Yes, we will also try to indicate the version and name more clearly in a future update.

    Heiner premium
    14. September 2017 at 11:27 #31318

    Hi waterdrinkingman,

    Das ist leider ein bekanntes Problem im aktuellen librespot, der Software auf welcher dieses Plugin basiert. Wir arbeiten bereits an einer möglichen Lösung, aber aktuell lässt sich dies leider nicht einfach fixen.

    In der Zwischenzeit kannst du jedoch das Spotty-Plugin für Squeezebox Server nutzen, falls die Lautstärkeanpassung zu unpraktisch für deine Anwendung ist: https://www.max2play.com/howtos/howto-spotify-einrichten/

    Heiner premium
    14. September 2017 at 11:24 #31317

    Hi Udo,

    Our images are very easy to set up and the default playback is your Pi’s native audio jack. The moment you select your sound card, settings are automatically made to select the right output device for it in your audio player of choice.

    You can find the output device selection in each audio player’s advanced options. Just click the „Edit Advanced Options“ button in our web interface.

    You can select what setup you might want on our start menu of the web interface. After rebooting the system, your audio player, e.g. Squeezelite if you select the advanced setup, will already the right output device, e.g. with HiFiBerry DAC+ it’s „sysdefault – snd_rpi_hifiberry….“.

    That way, you just test by setting up the system you like and playing the music you like. For a quick playback check you can either select a radio station in the Squeezebox Server or do the same with any other audio player, e.g. play a file from your iPhone when using AirPlay.

    Heiner premium
    13. September 2017 at 14:59 #31309

    Hi gmorel,

    First of all, unfortunately it is not possible to set a fixed IP for our Access Point Setup plugin.

    However, the AP does have both the IP of the network it receives its internet from, presumably your 178 network, and also offers new IP through its own network to all devices connected via this AP. Thus, it would be fatal to have the same IP range on your AP as in your local network as they would most probably overlap.

    Your mentioned wireless services would most probably require an alteration of the DHCP settings, which we do not offer or support.

    Heiner premium
    13. September 2017 at 14:44 #31308

    Hi Alexandre,

    While could not recreate the issue, we did come up with another diagnostic:
    Please try removing the Amp HAT and booting the Pi to see whether the web interface is still not reachable.

    Furthermore, please check your router’s web interface for what exactly the Max2Play device is recognized as, whether it changes IP’s and what else it gives out.

    Also, did you configure the sound card through our HiFiBerry plugin or did you do it manually?

    Heiner premium
    13. September 2017 at 14:40 #31307

    Hi Tom,

    Sorry that it is taking so long. This issue should have already been cleared up.

    Please try another radio stream to also rule this out as a source of error.

    Furthermore, you can add -a 80:4:24 to your command line options and select the output device „front card“ in your advanced settings.

    Heiner premium
    13. September 2017 at 14:35 #31306

    Hi Roger,

    Quick update: I confirmed with our head developer that indeed the version of Shairport installed on our current Max2Play is already Shairport-Sync. However, we will further update to the newest version 3.1.2 and add some info in the debug log to include this.

    Heiner premium
    13. September 2017 at 14:31 #31305

    Hi Cyn,

    First of all, sorry about the inconvenience and the late response.

    Squeezelite’s version in Max2Play is a special, customized one based on the same as PiCore, but with added functionality from our side as well. Thus, the most current version of Squeezelite available for Max2Play is 1.84.726 at the moment.

    However, we are working on an updated repository right now and will let you know as soon as the new version will be available for update.

    Heiner premium
    13. September 2017 at 14:11 #31303

    Hi rob,

    First of all, sorry about the late response and thanks for the kind words.

    We do not recommend changing the CLI port as it is an important parameter for a lot of apps and software that works with the Squeezebox system.

    However, we will alter our information in Kodi to include this possible issue and the path where you can change the port in Kodi, as it is secondary in our hierarchy to the Squeezebox Server. Consequently you will also have to alter the port in Yatse or other apps.

    Again, thanks for pointing this out, we will forward the information to our users.

    Heiner premium
    13. September 2017 at 12:48 #31302

    Hi aschiller and Oli,

    No, unfortunately running SBS as „pi“ is not a possibility.

    For now please note that the pulse framework is only activated when you use our Bluetooth plugin. Otherwise, you should get all ALSA features including „arecord“ and should also be able to use it as your input for waveinput.

    But, we will try to test this with the Digi I/O and let you know. 😉

    Heiner premium
    13. September 2017 at 12:36 #31301

    Hi Ravenik,

    We checked the situation with a fresh setup again and a simple update in Jivelite (pre-compiled by Max2Play) solves the issue. You also have to make sure that the Screensaver settings are set to „blank screen“ when off and when paused. This should get the trick done.

    Nonetheless, we appreciate the DIY solution and will continue to link to it if other users experience similar issues. Thanks for your detailed contributions and for pointing out this problem.

    Cheers
    Heiner

    Heiner premium
    13. September 2017 at 10:06 #31299

    Hi Cyn,

    Our default setting is sydefault which is also what we would recommend for stereo performance.

Viewing 30 posts - 2,761 through 2,790 (of 4,111 total)
1 2 3 … 92 93 94 … 136 137 138