Forum Replies Created
-
-
15. März 2018 at 12:34 #34445
Hi gls,
Thanks for sharing.
For what purpose are you using SSH? Max2Play is intended to run headless over web interface, so any SSH commands or edits make it difficult for me to recreate your issue and find a universal fix if there could indeed be a general problem.
You can do a package upgrade in our Raspberry Settings at any time.
If it’s not a hassle for you, you can try running a fresh image and try to recreate the issue when setting up WiFi via our WiFi/LAN web interface.
You can check the Debug Info window below to see which adapters are connected and get IP addresses.
15. März 2018 at 12:23 #34444Hi macaltec,
If you are using the Squeezebox Server, I’d recommend using the great Spotty Plugin for it to make your Squeezelites Spotify-compatible. There is even a new Spotify Connect feature included.
15. März 2018 at 11:04 #34440Hi Paul,
What status does the player put out when you start it and what output device did you select?
15. März 2018 at 11:01 #34439Hi j0f,
You can find the beta update in our Settings/Reboot menu below the normal update button.
15. März 2018 at 10:49 #34438Hi Marc,
Sorry about the late response. This is a difficult question as there are multiple routes to go and if you are a programming noob, all have their challenges.
Max2Play is based on Raspbian and since this request is not connected to any Max2Play Plugins or features, you should have quicker success checking out stack exchanges on what you want to achieve.
This should steer you in the right direction
You can use our Remote Control Plugin for SSH access
14. März 2018 at 18:29 #34426Hi medapyne,
Indeed, you need an Amp HAT for passive speakers and DAC HAT for active speakers. If you have a digital input on your stereo, you can also use a Digi HAT for that. Those are three main groups 😉
14. März 2018 at 18:27 #34425Hi arctoeric,
Sorry about this, the LMS 7.9 nightly changed a little during our exchange. Please make a beta update in Settings/Reboot and then install the 7.9 nightly again. Afterwards (give the server a few seconds to set up) you should be able to access the web interface it right away.
14. März 2018 at 17:33 #34424Hi joeri,
The Joggler Skin for Jivelite is our official skin for 7 inch RPi touchscreen. It allows for a direct switch to Kodi.
14. März 2018 at 15:29 #34422Hi gls,
What does the debug info say? Is the second IP listed under any entry?
Did you look at the Health Checker during the crash? Depending on your setup, if you have too many peripherals connected, the Pi might reach its limit in terms of power management. To rule this out as a source of error, please try recreating the issue without any periphery connected.
14. März 2018 at 15:24 #34421Hi medapayne,
If you have our default image, this plugin should come preinstalled. You can find in the LMS settings under plugins under the name of shairtunes2 (fork).
14. März 2018 at 13:38 #34418Hallo Haiko,
Kannst du bitte versuchen, das Beta Update in Settings/Reboot durchzuführen, den LMS Nightly erneut zu installieren, die Pakete zu updaten und Napster neu einzurichten?
13. März 2018 at 18:03 #34403advanced settings of the player you use. There is a setting called „command line options“.
13. März 2018 at 16:06 #34399Hi medpayne,
Not sure about your dac, but you can try adding „hw:1“ or „hw:0“ depending on the slot your sound card has.
13. März 2018 at 15:45 #34397Hi Stefan,
Firstly, please try running the Spotify Connect without any other players running. (You have to add the IP address of the device with LMS installed in order to run both Squeezelite and Spotify Connect at the same time)
If this does not change your situation, please try reinstalling Spotify Connect to rule out an issue with the install. We have not encountered this error message yet and according to my search, it also has not been reported on the librespot github as well.
13. März 2018 at 15:39 #34396Hi Mario,
Yes, for nightly you first need to make a beta update under „Settings/Reboot“
13. März 2018 at 14:22 #34393Hi actoeric,
Did you execute a reboot after the installation and try again? Please share the debug info when trying to start LMS (bottom of the menu) if still does not start properly.
13. März 2018 at 14:21 #34392Hi Randy,
Hast du einen DigiOne Version 1.1 oder 1.2? Du kannst dies an den drei kleinen Elementen oben rechts sehen. Wenn diese drei alle gleich sind handelt es sich um 1.2, wenn nicht ist es 1.1.
13. März 2018 at 13:51 #34391Hi gls,
– Using either dongle should improve the quality of connection
– Only the IP address of wlan0 should be visible, are you still having three IP’s?
– You need to use or install the Joggler Skin in Jivelite, its custom for 7″ RPi Touchscreen
– You can set up a screensaver in Jivelite’s Settings, there you can also see how it until it should show up13. März 2018 at 12:28 #34390Hi justwords,
Thanks for the quick follow-up! Glad to hear that it works now.
13. März 2018 at 12:25 #34389Hallo damianar,
Entschuldige die späte Rückmeldung. Dieses Topic ist eigentlich nur zu Info gedacht. Bite poste in Zukunft ein eigenes Topic für technische Anfragen.
Es gibt ein Topic wo bereits ein User mehrere Kanäle auf einer LogiLink 7.1 genutzt hat für unterschiedliche Player. Dieses findest du hier.
13. März 2018 at 12:20 #34388Hi TJH,
Holiday was great, thanks for asking 🙂
– Fixed IP unfortunately only works with ethernet connection.
– We had an issue with the LMS 7.9 nightly. After running a beta update in Settings/Reboot, the install should work again.
Is your share still not recognized or indexed incorrectly in LMS?
13. März 2018 at 12:08 #34387Hi Paul,
That’s the error message when you username was not recognized. Please check again in the field „Username“ of the Plugin if your premium account’s username is correctly entered.
13. März 2018 at 12:06 #34386Hi Leute,
Wir konnten einen Fehler bei der Nightly lösen in unserem aktuellsten Beta Update. Einfach Beta Update in Settings/Reboot klicken und danach den LMS erneut installieren.
13. März 2018 at 12:05 #34385Hi j0f,
We recently fixed an issue in our most current beta update (under Settings/Reboot) for the Nightly 7.9 of LMS.
So please try installing again after makingt that update.
13. März 2018 at 12:05 #34384Did it work? We recently fixed an issue in our most current beta update (under Settings/Reboot) for the Nightly 7.9 of LMS.
13. März 2018 at 11:12 #34382Hi MustangsGM,
We currently only offer 2,8″ and 7″ skins by Max2Play. There are also some other skins preinstalled on Jivelite that you can test and some by users you can install in the jivelite web interface menu.
You can also check out this correspondence (German, use Google Translate. If you have trouble understanding, let me know.) where another user got his WaveShare 5″ Display to work. This is the WaveShare 7″ solution in our web interface, so try installing that.
13. März 2018 at 10:51 #34376Hi ALW,
Have you tried running the card with our newest version of Max2Play 2.45? It already has
#### KERNEL #### 4.9.39-v7+12. März 2018 at 18:07 #34350Hi medpayne,
As mentioned before, we do not have this device here for testing.
You can try selecting „none“ in the HiFiBerry plugin, rebooting, reselecting HiFiBerry DAC (no „+“) and rebooting again.
12. März 2018 at 18:04 #34349Hi gls,
1. Please share your debug info log so we can see exactly what the third IP is assigned to.
2. Manually closing ports or removing parts of Max2Play is not recommended or necessary. As you can see in the Health Checker under Settings/Reboot, the system already runs well. Kodi is just installed and never has to run if you do not need it.
Another tip: The Pi3 shares an antenna for both WiFi and Bluetooth. So if you want to use both simultaneously, utilizing a WiFi dongle would be recommended.
12. März 2018 at 17:59 #34348Hallo Robert,
Vielen Dank für deine Anfrage.
Wenn du dich damit auf dieses Topic beziehst, sollte doch auch hervorgegangen sein, dass lediglich die simultane Nutzung von hw volume control und Equalizer nicht funktioniert.
Grundsätzlich ist es so, dass ich mich mit jeglichen Anfragen beschäftige, jedoch die mit mehr individuellen Stimmen priorisiere. So wird auch diese Anfrage mehr Aufmerksamkeit erhalten, wenn mehr Leute sich diese Umsetzung wünschen. Ebenso hat sie bereits mehr Aufmerksamkeit als andere Anfragen erhalten, weil mehr als eine Person dieses Feature bereits erfragte.
Die Nutzung des AMP2 unter Max2Play ist übrigens ein kostenfreies Feature, ebenso wie der Equalizer und das gesamte Audioplayer Plugin.
-
