Heiner

Forum Replies Created

Viewing 30 posts - 2,551 through 2,580 (of 4,111 total)
  • Posted in:
  • 1. November 2017 at 10:32 #32227

    Hi Dicker,

    Hier ist die Repo für das Family Plugin: https://richiezed.com/squeezefamily/repo.xml

    Du kannst dieses im LMS-Menü unter Einstellungen -> Plugins ganz unten einfügen.

    1. November 2017 at 10:26 #32226

    Hi romain,

    Thanks for alerting us on this issue. We will check the plugin with our current image.

    30. Oktober 2017 at 18:03 #32214

    Hi Polouch,

    Please try installing the Squeezebox Server to make sure you are connected to the internet.

    30. Oktober 2017 at 18:02 #32213

    Hi Man48,

    You can have a look at the buffer time and try adjusting the buffer rate with the Squeezelite command line options: http://manpages.ubuntu.com/manpages/trusty/man1/squeezelite.1.html

    If you have not yet, please also add hardware volume control: https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/

    Also, these tips might help you: https://www.max2play.com/en/wiki/getting-high-sound-quality/

    30. Oktober 2017 at 17:39 #32212

    Hi Blockstermann,

    Ich habe vor kurzem einen Wiki-Artikel zum Mounten von Fritz-Box-Shares gemacht für deutsche User: https://www.max2play.com/en/wiki/pfad-von-fritzbox-mounten/
    Außerdem gibt es noch das englische Wiki zum allgemeinen Mounten: https://www.max2play.com/en/wiki/mounting-an-external-drive/

    Falls diese keine Abhilfe bringen, melde dich hier bitte erneut und teile die Debug Info vom Filesystem/Mount Menü mit.

    30. Oktober 2017 at 17:32 #32211

    Thanks for the feedback. We have now added a notice to the configuration for this issue. Automatically, it now sets up hw:1 for new setups in our most current beta.

    30. Oktober 2017 at 13:22 #32188

    Hi guys,

    Please do make sure that none of your „available plugins“ still have autostarts set as these will run in the background if they are fully configured. If there are any you had running before that might still have a process in autostart, please reactivate them to make sure they are all removed.

    I started with a fresh install of Max2Play and set up Spotify Connect and RPi-Display. Unfortunately, I could not recreate any issue after enabling the SD protection.


    @okenny
    : Could please detail what you mean by nothing else? Did you have all other plugins removed from the menu? Do you have any autostarts left? Are you able to start Spotify Connect? If so, when and how do the problems occur?

    30. Oktober 2017 at 13:11 #32185

    Hi Nojelc,

    Thanks for the follow-up! Happy it works for you, now 🙂

    30. Oktober 2017 at 13:10 #32184

    Hi guys,

    Sorry about the confusion. There is no direct error resulting in this. You can still use the fixed IP and it will remain accessible. However, you do get a second IP which we are currently trying to fix.

    Thank you for your understanding.

    30. Oktober 2017 at 13:04 #32183

    Hi RHD,

    This plugin is still maintained by Logitech, according to the official forums, free accounts only work on official Squeezeboxes:
    http://forums.slimdevices.com/showthread.php?105368-LMS-doesn-t-log-me-in-to-Pandora

    However, you can also post there to find out more on what other users did to achieve Pandora services in LMS.

    30. Oktober 2017 at 12:59 #32182

    Hi cramcram,

    6-7 seconds is indeed a little too long waiting for a menu. You might be able to shave off a few seconds with the regular 7.9 version of LMS.

    However, the wait might also just be related to the connection to Spotify with librespot.

    You could try out the Connect feature to see whether the latency remains.

    30. Oktober 2017 at 12:53 #32181

    Hallo Thomas,

    Handelt es sich bei deinem Odroid auch um einen XU4?

    Hast du eine feste IP für den Odroid zugewiesen in WLAN/LAN?

    Welche Werte hast du beim Mounten deiner Festplatte und Freigeben über SambaShare angegeben?

    30. Oktober 2017 at 12:45 #32180

    Hi Scott,

    No there should not be any issue. However, since you cannot access the Max2Play web interface right after the first boot, something has to be wrong. However, apache is most likely not related to it.

    If yo have not yet, please try burning a fresh image and immediately check whether you can access the Max2Play web interface.

    30. Oktober 2017 at 12:42 #32179

    Hi phamd4,

    Please check in the LMS web interface under Settings -> plugins which shairtunes2 plugin is active. Please select shairtunes2 (fork) and remove the other instance if possible.

    27. Oktober 2017 at 13:30 #32158

    Thanks for the feedback, we will try our best to find the ideal solution in the next version 🙂

    27. Oktober 2017 at 13:29 #32157

    Hi sfraser,

    Please check your router’s web interface for the IP of your device, enter it into any browser, change the name of your device in Settings/Reboot, reboot and try accessing that name.

    Your issue is most likely not related to apache.

    27. Oktober 2017 at 13:18 #32156

    Hi ad,

    The upgrade is indeed for 17.4 of Kodi. However, there might be dependency issues if you have a an older image that you updated (system update, not Kodi update).

    So if in Settings/Reboot in the Debug Info, it says wheezy instead of jessie, you have to either burn the fresh image based on Raspbian jessie or use a wheezy-based Kodi installation of version 17.

    27. Oktober 2017 at 12:18 #32153

    We do not have a specific date for new releases. But we will put out a blog article once it’s out.

    For now, you can update to beta for this feature.

    27. Oktober 2017 at 11:46 #32151

    Do you have the beta Spotify Connect feature activated? If so, please try deactivating it to rule it out as a source of error.

    Also, please check your Health Checker when the playback is slow to see whether the CPU and SD card are affected.

    27. Oktober 2017 at 11:37 #32148

    Hi guys,

    Sorry about the confusion.

    The driver is not yet added to the Raspberry Settings overview. Selecting it in the HiFiBerry Plugin is the recommend way to go.

    After reboot you should get the right drivers. In Audioplayer menu, make sure that Squeezelite is running successfully with a process and that “sysdefault – snd_rpi_hifiberry_dacplus, – Default Audio Device, CARD=sndrpihifiberry” is selected.

    The one issue I experienced while setting it up, is that we now automatically set the hardware volume control in the command line options (in Squeezelite’s advanced options) to „hw:0“ which only works with the built-in audio is deactivated. You can do this in the Raspberry Settings. If you do not have a premium license or do not do deactivate the built-in audio, you either:

    Option 1:
    Remove the command line options from Squeezelite’s Advanced Options and click „save“
    -> NO Hardware Volume Control anymore!

    Option 2:
    Change the hw:0 to hw:1 OR deactivate build in audio in the Raspberry Settings
    -> Hardware Volume Control remains

    Thanks for pointing us towards this issue, we will find the best fix for this as soon as possible and I will make sure everybody encountering this gets the solution they need.

    For now, these options are your best bet. Please let me know whether you would prefer Hardware Volume Control to be set right after selection, or whether you would rather want it to be optionally available as a later addition?

    • This reply was modified 8 years, 5 months ago by Heiner.
    27. Oktober 2017 at 10:00 #32147

    Hi phamd4,

    Please follow these steps:

    Delete the license in the Max2Play interface and click „save“ with a blank field.
    Click on „Settings/Reboot“ again, reenter your license and click „save“.
    Check if the green „Activated“ field appears.

    27. Oktober 2017 at 9:51 #32146

    Hi ulip,

    Hast du schon versucht, den Namen des Geräts zu ändern und damit drauf zuzugreifen?

    Bitte versuche den gmedia renderer zu deaktivieren um diesen als Fehlerquelle auszuschließen.

    Versuche außerdem, die genannten Server kurzzeitig auszuschalten, um diese als Fehlerquelle auszuschließen.

    Du kannst zudem noch die Maßnahmen durchführen, die hier genannt werden:

    https://www.nginx.com/blog/welcome-to-nginx-on-my-favourite-website/

    27. Oktober 2017 at 9:18 #32144

    Hi ad6922,

    I just installed a fresh 2.44 image to check and Kodi should start out with version 15.2-2~jessie from the first boot.

    If you still have an old Raspbian Wheezy image, you can either burn a fresh jessie image or find a wheezy version of Kodi 17.

    27. Oktober 2017 at 9:13 #32143

    Hi necrotk,

    Bei einem AV-Receiver hast du die Wahl zwischen DAC oder Digi. Beides kann problemlos angeschlossen und genutzt werden. Ich habe das von dir genannte Modell gecheckt und da gibt es sowohl TOSLink, als auch RCA’s für DAC’s. Die meisten Nutzer nennen jedoch Digi-Karten als optimalen Output für AV-Receiver.
    Dahingehend kannst du noch unseren Digi-Soundkartenvergleich checken.

    27. Oktober 2017 at 9:01 #32142

    Hi lemuba,

    For that you could try pairing your device to play youtube on with the bluetooth plugin for the audio Pi and stream the same procedure as mentioned above for the second Pi with video.

    26. Oktober 2017 at 15:49 #32132

    Hi ctweedle,
    Unfortunately, we do not have an HC1 here to test this, but if it can handle the same Ubuntu distros as the XU4 it should work. You can just download our XU4 image and try it out.

    We’d appreciate a follow-up post if you get the chance to test it 😉

    26. Oktober 2017 at 15:47 #32131

    Hi sveenma,

    What SD card are you using? How do you shut down the system? What did Spotify Connect solution do you use? Our plugin or Spotty?

    26. Oktober 2017 at 15:46 #32130

    Hi veryaner,

    Sure I can 🙂

    Max2Play’s multiroom system is based on a headless server+player structure, meaning you only need one „master“ Pi with the server installed. This one can also be used as a player at the same time. Meanwhile, all other zones in your multiroom system just need to be players and can all be controlled by the one server, which itself is decentralized and can be configured and controlled by any other devicein the network (apps, web interface via browser, etc.).

    So you can use one Pi to have the server and a sound card with player and several other Pi’s in different rooms with just players (including your bluetooth speaker, if you like, but we recommend direct connection via sound card to active speakers, passive speakers, existing sound systems, etc.)

    We offer complete bundles for individual zones and you can check out our multiroom configurator to find the fitting ones for each zone:

    Multiroom Audio Configurator

    Build your own multiroom audio system

    26. Oktober 2017 at 14:01 #32125

    Hi cramcram,

    While I do not have a reference point for the speed you are experiencing, the LMS should indeed not have any timeouts while using Spotty. At least I never experienced any.

    Which version of LMS and which version of Spotty are you using?

    26. Oktober 2017 at 12:31 #32121

    Hi sven,

    Thanks for choosing Max2Play and thank you for the quick follow-up. 🙂

Viewing 30 posts - 2,551 through 2,580 (of 4,111 total)