Forum Replies Created
-
-
13. September 2017 at 9:59 #31298
Hi Nils,
Multiroom Spotify works different from our Spotify Connect Plugin. The Spotify Connect Plugin only works individually, whereas the Spotty plugin for the Squeezebox Server lets you synchronize streams and play to different players. Here’s how you set it up: https://www.max2play.com/en/how-tos/howto-spotify/
13. September 2017 at 9:56 #31297Hi Volker,
Just install the 2,8″ Skin in the Jivelite web interface and reboot the system. Afterwards the selection for screensaver should be blank screen and once active, will also shut off the backlight.
12. September 2017 at 15:20 #31292Hi Alexandre,
We will try to recreate your issue with Pi2 and Amp+. In the meantime, please try using an ethernet connection if you have not yet, to rule out bad WiFi as a source of error.
12. September 2017 at 10:36 #31289Hi Alexandre,
Can you reach the device’s web interface with its IP (listed in your router’s interface)?
Also, which model of the Raspberry Pi are you using?
12. September 2017 at 10:34 #31288Hi guys,
The kernel is also listed in our debug info on Settings/Reboot.
12. September 2017 at 9:46 #31285Hi Nils,
I tried to recreate your issue with a new install of the plugin but did encounter it.
Based on your debug, you might have entered something in the wrong field. Make sure to leave command line options blank and only enter your password and login of Spotify Premium.
Please click the reinstall button on Spotify Connect and reenter your login credentials afterwards.
Also make sure your premium account with Spotify is active at the time of login.
12. September 2017 at 9:07 #31284Hi Cyn,
Sorry about the late reply.
Does a random radio stream or your music play okay? If not, please check your output device selection in the advanced options of Squeezelite.
11. September 2017 at 17:16 #31272Hi Alexandre,
Thanks for your request.
What does your Health Checker say in Settings/Reboot? Also, which version of the Raspberry Pi are you using?
Furthermore, could you share the debug info on your Settings/Reboot page?
11. September 2017 at 17:02 #31270Hi Eric,
That should not be the case at all, then. I am sorry about the problems you are encountering.
Then this might be connected to another plugin on your device. Please share the debug info on the Settings/Reboot menu. The first lines show you how much space is used, it should not be more than 40 percent.
Please also check the final lines of the installation sequence of the LMS to make sure there is no apparent errors.
The quickest solution would be to burn a fresh image. If you already implemented some configurations, you can make a back-up of your current image with our plugin image burner with a few clicks.
In order to find out exactly where the image went wrong, I would ideally need all the steps you have taken thus far. Since this would be a lot of work for you, a fresh image might the easier option. But I will assist you either way, just let me know how you will proceed.
11. September 2017 at 16:16 #31267Hi mark,
Unfortunately, Spotify Connect is only available for Raspberry Pi.
The Odroid images are based on a different system, Ubuntu and thus cannot utilize the same packages and scripts.
11. September 2017 at 16:14 #31266Hi Raymond,
Sorry about that, I will update the thread accordingly.
11. September 2017 at 16:13 #31265Hi Slartibartfast,
Here is Raspberry’s official statements on it:
https://www.raspberrypi.org/documentation/raspbian/updating.md
https://www.raspberrypi.org/documentation/linux/kernel/updating.mdWe concur in recommending to not update new, untested kernels. However, you can of course still update whatever you want over SSH.
Max2Play does not have any benefits in manually updating the kernel. we recommend only updating from the Raspberry Settings.
11. September 2017 at 16:09 #31264Hi Eric,
Sorry about the inconvenience.
What version of Max2Play do you have, what version of the LMS did you install and what Raspberry Pi are you using?
In any case, a re-install of the LMS 7.9 should do the trick. Just click show available versions, select 7.9 and click install. It will overwrite the faulty installation. Also, please be patient as the installation can take a few more minutes than most other software on Max2Play.
11. September 2017 at 16:04 #31263Hi Nils,
That’s just the device name for recognition, it should change the player’s behaviour whatsoever.
You can leave the default inputs as they are and just select the correct output device to get started.After the normal installation and input of your premium login, what does the plugin do and does the player show up in your Spotify app? It should show up with the given name of your device (default „max2play“) which is what the error message is about.
11. September 2017 at 16:01 #31262Hi sigfrido,
If you do not have active speakers, you absolutely need an amplifier before directly connecting the DAC.
The amplifier needs to provide the correct wattage for your speakers. You can find out what the speakers need on the manufacturer’s page or on the speakers themselves.
You need to connect the RCA outputs of the DAC to to the RCA inputs of either your Amplifier or your active speakers for the DAC to correctly send the analogue HiFi audio signal that is then amplified, either by a dedicated amplifier or by active speakers‘ built-in amplifier.
11. September 2017 at 14:16 #31260Hi Roger,
Thanks for the detailed follow-up.
Your issue of stalling/hanging music playback has come up a lot of times in this forum. The recommendations I mentioned have all been the root of the problem for some users that have posted here. However, the issue is very vague and can thus stem from all kinds of issues.
The fix that you have found for yours is peculiar as the shairport instance we have running has been stable and reliable for a few years.
Nonetheless, we appreciate the feedback and will look into a possible replacement. We will let you know, when a new beta is available for testing.Thanks 🙂
11. September 2017 at 11:25 #31256Hi lemuba,
Wir haben leider noch keine Erfahrungen mit IO Broker machen können. Falls dieses Program jedoch Port 9000 verwendet, ist es schon möglich, dass der LMS sich deswegen auf 9002 umstellt. Wird Port 9000 denn zwingend benötigt für deine LMS-Installation und Nutzung?
11. September 2017 at 10:41 #31254Hi powerbiker,
It looks like the installation sequence is not responsive.
Please try burning a fresh image if it’s not too big of a hassle. You can back up your current image with our image burner plugin, just in case.
8. September 2017 at 13:04 #31211Hi Antti,
First of all, thanks for making the switch to us 🙂
1) This is probably related to your Spotify client. Please try out whether the same issue occurs with anothr app.
2) This is an issue that is being worked on in the librespot solution we are incorporating. You can click the reinstall button to get the latest update of librespot, however the fix is still a work in progress and some unexpected shutdowns might still occur.
8. September 2017 at 11:57 #31208Hi Roger,
Thanks for the kind words.
Please first try disabling build-in audio in the Raspberry Settings. However, in your case there can be a lot of factors. Including the cable to the passive speakers, the speakers themselves, the AirPlay device, the WiFi or LAN connection. Please try isolating and switching some of these factors around if you are able to, to rule them out as sources of error. Also, if you are not using it, perhaps deactivate Bluetooth as well.
8. September 2017 at 11:23 #31207Hi powerbiker,
Please try upgrading Kodi again, and make sure that „kodiupgradepi“ shows up in the line next to it for a second.
When you start Kodi afterwards, please make a tick by „reinitialize display“ beforehand.
8. September 2017 at 10:17 #31190Hallo denaja,
Wir haben dieses Setup nicht mit HiFiBerry’s DAC+ testen können, aber wir haben hier eine detailierte Aufbauanleitung für das Case erstellt:
Bis auf die Implementierung für den Power-Button, welcher wahrscheinliche andere GPIO-Pins benötigt, sollte alles relativ ähnlich installiert werden können. Die Stromzufuhr sollte auch ausreichend sein.
Grundsätzlich empfehlen wir die Nutzung dieses System jedoch nur mit Audiophonics Soundkarten, da wir keinerlei Garantien für andere Hardware ausstellen können.
7. September 2017 at 9:36 #31160Hi tom,
The error you posted might be related to your version. Please try updating all packages in the Raspberry Settings at the end of the page.
7. September 2017 at 9:26 #31159Hi Iwan,
You can disable the access point by removing the tick from the WiFi/LAN menu on that feature. It’s just a security precaution.
Bundle images come preconfigured and with an already expanded filesystem. We do recommend updating your system as those include bug fixes and other improvements, but they are not absolutely necessary.
7. September 2017 at 9:23 #31158Hi Cyn,
The updating process via the LMS web interface should pose no problem. My tester currently runs Version 7.9.0 – 1488878280.
6. September 2017 at 16:28 #31152Hi Daniel,
Jep hab ich getestet, klappt mit dem Sabre V3-Treiber. Letztere Features sollten auch alle klappen, können wir jedoch nicht garantieren.
6. September 2017 at 16:26 #31151Hallo Michael,
Versuche bitte den Treiber des HiFiBerry DAC+ und füge zudem „hw:1″ oder hw:0“ je nach dem ob deine Soundkarte auf dem einen oder dem anderen Slot ist (debug info am ende der seite).
Zudem kannst du Suptronics kontaktieren und fragen, welchen Treiber Sie genau verwenden.
-
