Heiner

Forum Replies Created

Viewing 30 posts - 2,461 through 2,490 (of 4,111 total)
1 2 3 … 82 83 84 … 136 137 138
  • Back to forum
    Posted in:
  • Heiner premium
    21. November 2017 at 10:29 #32554

    Hi eightdigitworld,

    Sorry about the late reply, I was off work for a few days.

    You can try playing the files via HDMI or the native headphone jack to rule out the USB DAC as a source of error.

    edit: also, check the settings of the LMS on FLAC and DSD playback.

    Heiner premium
    14. November 2017 at 17:22 #32487

    Hi TJH,

    What image did you start with? If you did not configure a lot, you could burn a fresh 2.44 image which should have Kernel 4.4.41-v7+ from the start.

    Heiner premium
    14. November 2017 at 17:18 #32486

    Hi Markus,

    Ja, das ist möglich. Hier findest du mike brady, den Entwickler von shairport sync zum Thema: https://github.com/mikebrady/shairport-sync/issues/267

    Das Ziel wäre es, „Avahi“ auf wlan0 Interface zu beschränken.

    Das sollte so klappen (in SSH mit putty o.Ä.):
    sudo nano /etc/avahi/avahi-daemon.conf
     Einfügen: allow-interfaces=wlan0
     Einfügen: deny-interfaces=eth0
     Neustarten

    Heiner premium
    14. November 2017 at 17:16 #32485

    Hi Martin,

    You might have used an older version of Squeezelite on Max2Play.

    Please try using our own compiled one which should be Squeezelite Max2Play v1.0.3 based on v1.8.7-999

    Heiner premium
    14. November 2017 at 17:14 #32484

    Hi Yasmail,

    We now also added an output in the current beta of the WiFi/LAN plugin that shows the status of the power management.

    Heiner premium
    14. November 2017 at 15:58 #32482

    Depends on the IR stick.

    Here’s a general discussion on IR with Squeezelite: https://www.max2play.com/en/forums/topic/infrared-remote-for-max2play-rpi-squeezebox/

    And here’s the solution for FLIRC: https://www.max2play.com/en/forums/topic/problem-mit-flirc-usb-ir-stick/

    Heiner premium
    14. November 2017 at 13:33 #32478

    Hi Matthew,

    Please select none in your HiFiBerry Plugin, reboot the system, select your DAC again, reboot again.

    The complete command line options for hardware volume control are -o hw:0 -V Digital when you have build-in audio deactivated in the Raspberry Settings.

    Optimizing Squeezelite’s Volume Control

    Heiner premium
    14. November 2017 at 13:28 #32477

    Hi Christophe,

    If this issue occurs with all the distributions, your hardware might be defective.

    You can try checking other speakers and/or cables to rule these out as sources of error.

    Heiner premium
    14. November 2017 at 13:23 #32476

    Hi wifi75,

    You should also have a proper Spotify Premium Login with your subscription to Spotify Premium. Currently, only this login can authenticate your account with our Spotify solutions.

    Heiner premium
    14. November 2017 at 13:20 #32475

    Hi SkyFulcrum,

    Please try putting the value „-Q“ in front of the other command line options.

    Heiner premium
    14. November 2017 at 12:07 #32474

    Hi kriddy,

    Did you create the SambaShare with Create Mode 777?

    Heiner premium
    14. November 2017 at 11:10 #32472

    Hi TJH,

    Please try updating the Max2Play system first. Then, try updating the Kernel again.

    Heiner premium
    14. November 2017 at 10:04 #32471

    Hallo Beginner,

    Du kannst noch versuchen, den Parameter für Bufferrate manuell anzupassen:

    -b <stream>:<output>Specify internal Stream and Output buffer sizes in Kbytes in den Kommandozeilenoptionen von Squeezelite.

    Hier findest du zudem noch die anderen Parameter um manuelle Konfigurationen in Squeezelite vorzunehmen: https://www.max2play.com/en/wiki/command-line-options-for-squeezelite/

    Heiner premium
    13. November 2017 at 17:18 #32463

    Hi specher,

    You can use Jivelite and Kodi and switch between the two. You can create a button or bookmark for the http command to start Kodi and have Jivelite running otherwise. This way, you can start your video use with one command from any device (use the voice control plugin to get the right http command or check the URL bar after starting Kodi) to use Kodi and just shut it down once you are done with it to get Jivelite started again.

    I have not tested this specific setup yet, but the only issue that might arise is that Jivelite might not start up automatically again after turning off Kodi. For that, you can also add a http command.

    Heiner premium
    13. November 2017 at 16:56 #32462

    Hi dumtratt,

    Which image did you use? Please reboot your system and try again.
    Please also check whether you have Shairport on Pulse and make sure that your device shows up green when heading to the Bluetooth plugin.

    Also, make sure you have the current version of the Bluetooth plugin, you can update it by just installing the plugin from our website again.

    • This reply was modified 8 years, 4 months ago by Heiner.
    Heiner premium
    13. November 2017 at 16:34 #32461

    Hi Yasmail,

    You could try this (not tested yet, but M2P is based on Jessie so it should work):

    Disabling WiFi Power Management Permanently for Raspberry PI 3 with Raspbian Jessie

    login is pi pw is raspberry, root pw is max2play

    Heiner premium
    13. November 2017 at 16:29 #32459

    Hi Tetsuo,

    Unfortunately, our plugin is an implementation of the librespot protocol which we do not alter. But you can add this issue as a to-do: https://github.com/plietar/librespot/issues

    Heiner premium
    13. November 2017 at 16:26 #32458

    Hallo Florian,

    Was passiert denn beim Synchronisieren? Bleibt die Wiedergabe lediglich auf dem originalen Gerät oder wechselt sie zum zweiten?

    Ist außerdem bei deinen Squeezelite Playern die Hardware Volume Control aktiviert?

    Optimizing Squeezelite’s Volume Control

    Heiner premium
    13. November 2017 at 16:23 #32457

    Hi Bill,

    The easiest way to go there is to reimage the SD card, as our current build of the RPi-Display plugin is for specific screens and their use, we have not added a fully functional deinstallation yet.

    Heiner premium
    13. November 2017 at 16:20 #32456

    Hi NoizeBoy,

    You can use MultiSqueeze to name the player on the device a different name (so device name in Settings/Reboot „Music Server“, 1 player in MultiSqueeze „LivingRoom“, deactivate autostart for Squeezelite in Audioplayer menu). The name of the server is always the same as the device name as it’s tethered to the device IP. 😉

    Heiner premium
    13. November 2017 at 13:47 #32453

    Hi nb,

    Please try burning a fresh image, if you have not yet.

    Afterwards, please try connecting with another method than you already used, e.g. WPS or Access Point Autostart Mode:

    How-to – WiFi Configuration with WPS and Max2Play

    Access Point Autostart Mode

    Heiner premium
    13. November 2017 at 13:45 #32452

    Hi Matthew,

    You can make sure your hw volume control is set up properly. The advanced options‘ command line options should include „hw:0“ or „hw:1“, depending on whether you deactivated the build-in audio or not. If its inactive, please make sure it says „hw:0“ and vice versa.

    Heiner premium
    13. November 2017 at 13:41 #32451

    If you do have another device you could check for that ethernet connection, you could try to recreate the issue to rule out the Pi’s ethernet port as the source of error. This is amongst the most likely of sources.

    You could also try running a completely fresh image for a day to rule out any software changes.

    Otherwise, you can also try running the system as is via WiFi to see if this is truly a hardware issue with the ethernet port.

    Heiner premium
    13. November 2017 at 13:35 #32449

    Hi tof,

    The Amp2 now uses the digital driver by HiFiBerry (same as the new DAC’s), as opposed to the Amp+’s master driver. That’s why the output device option does not say „amp“ anymore.

    Please try removing the parameters for hardware volume control from your Squeezelite in order to rule it our as a source of error. You can also deactivate the build-in audio and make sure your „hw:“ says 0.

    Furthermore, please try testing another power supply, if possible. 3.33A is on the lower end of what the Amp2 + Pi need. Also, remove all periphery from the Pi that might also require power (USB).

    Heiner premium
    13. November 2017 at 13:32 #32448

    Hallo Mini,

    Ist der Parameter für Hardware Volume Control in deinen Erweiterten Einstellungen gesetzt?

    Optimizing Squeezelite’s Volume Control

    Falls du die eingebaute Soundkarte in den Raspberry Einstellungen deaktiviert hast, muss bei hw: eine 0 stehen. Falls nicht, eine 1.

    Heiner premium
    13. November 2017 at 12:37 #32444

    Hi Peter,

    What connection method did you use? I am not sure which bug you are referring to as we have not yet been able to recreate the specific issues. This topic contains various solutions to different problems, including a shairtunes2 bug fix that you might be referring to.

    For now, please try using WPS, Access Point Autostart or following the normal Wifi procedure.

    How-to – WiFi Configuration with WPS and Max2Play

    Access Point Autostart Mode

    If you are having issues with the latter, please share your steps and error messages so we can understand what might be the problem.

    Firstly, do make sure your ethernet cable is reomved after you configure your WiFi and reboot, if you are going with the normal WiFi configuration.

    Heiner premium
    10. November 2017 at 14:24 #32408

    Hi SkyFulcrum,

    Hast du das 7″ touchdisplay image gebrannt? Dieses sollte den 7″ Raspberry Pi Touchscreen automatisch kalibrieren.

    Heiner premium
    10. November 2017 at 14:19 #32407

    Hi Polouch,

    Please try removing the autostart from Squeezelite and also make sure that the outputs of players don’t overlap.

    Heiner premium
    10. November 2017 at 14:19 #32406

    Great, let me know if this fixes problem so I can close the topic 🙂

    Heiner premium
    10. November 2017 at 11:38 #32401

    Hi Nojelc,

    In this case, the Squeezelite player hogs the output. Usually, Squeezelite should shut down automatically when you start Kodi, allowing the output to be freed up. Please try removing the autostart from Squeezelite, rebooting and starting Kodi.

Viewing 30 posts - 2,461 through 2,490 (of 4,111 total)
1 2 3 … 82 83 84 … 136 137 138