Please try running the „advanced“ option in our web interface. This is our best player software and we can use it to rule out the MPD as a source of error. Do the following:
Select „none“ in the web interface, reboot, select „advanced“ option, reboot, select „Digi/Digi+“ in HiFiBerry Plugin, reboot, install Squeezebox Server version 7.9 and head to its web interface to play radio from a known station to your local player (upper right corner of the LMS web interface with the name of your Max2Play device). For further guidance on our Squeezebox System, check out our youtube channel „Max2Play“ and our Wiki in the Help section of this website.
We have not tested Napster in a while. We will take this on in our next session and look at possible fixes to make sure Napster users don’t have to manually alter Max2Play in the future. Thank you for pointing this out.
If you are using our upgraded version 17.4 of Kodi, you need to head the following way:
Settings Wheel in the main menu -> Interface Settings -> Regional -> Language -> Russian
It will install the language pack and automatically go into Russian menus.
Du kannst unser Remote Control Plugin für SSH nutzen. Der root login sollte funktionieren indem du su mit Enter bestätigst und dann „max2play“ als Passwort eingibst.
@Stefan: according to your log, you have an irregular command in your command line options. Please check the advanced options and delete anything that might be entered in your command line options.
Which version did you install? Nightly or official? Please try official if you have not.
Also, which Raspberry Pi do you use? I will try to recreate the issue since the problem with the nightly that was reported before should be fixed by now.
Also, thanks for informing us. We might have to investigate this issue to make sure that future Max2Play users with Apple NAS do not run into this issue in the future.
Currently, there is only an option to shut down the Pi from Jivelite. However, you can make a request for a reboot button and if other users chime in and agree that this feature is something they want, we will discuss adding it to a future release 😉
Sorry about the inconvenience, obviously this should be much simpler.
– By proper I meant non-nightly. Both work fine but the nightly recently changed its repo which resulted in the first error message you posted. This is fixed now and both versions should install fine.
– The WiFi should work out of the box but the Pi’s antenna is not the greatest. Perhaps try connecting nearby your router for first setup. You can also try using WPS for connecting.
– There’s a difference between our beta image and our beta update. Beta version is based on Raspbian Stretch while beta update just adds our most recent bug fixes and changes which have not been officially released yet. However, LMS install should not even require a beta update at this point.
Please check your free space to rule it out as an error. You can see it in the Settings/Reboot Debug Info. You can also check the Health Checker there to make sure your Pi is running fine.
Jivelite is exclusive to the Squeezebox system and the Squeezelite player. You need a Squeezebox Server and Squeezelite both running in order to use Jivelite. Both do not need a lot of processing power and you only need to install the server with one click while Squeezelite comes preinstalled.
Unfortunately, there has been no change in this feature as not many people have been requesting it. However, you can open a topic in our development forum and if there are some other users requesting this feature, we will look into it more thoroughly.
You could indeed mount the SambaShare from one Pi on another with Filesystem Mount.
But if the load is indeed too high for your Pi’s, you can also try creating a new login for your share on the Apple NAS to use in Max2Play to rule out an error there.
The issue can occur with insufficient power. If you have a power supply with less than 2.5A, please make sure no other periphery is connected (the other USB devices suck power as well) and try using one with 2.5A if possible.
Also to make sure the RPi3 WiFi setting is not impeding on your B+’s recognition, please make a tick at the disable build-in WiFi option in the Raspberry Settings.
I tested the stick and it was immediately recognized here.
Sorry about the inconvenience. The Spotify Connect Player should be fixed, now.
Please try selecting „none“ in the Allo Plugin, rebooting, selecting the DigiOne again, rebooting and selecting the correct output device in Spotify Connect again.
Also, please make sure the autostart checkbox is deactivated in Squeezelite and Shairport to rule these out as sources of error.
I am not sure what exactly your issue is. Kodi should be accessible and controllable even without any network. If you are connected to a screen via HDMI on boot, you can start Kodi right away and navigate using any USB periphery, like mouse, keyboard, etc.
What is your setup and what are you trying to achieve?
English
German
