Forum Replies Created
-
-
1. März 2018 at 13:39 #34159
Hi Dave,
SambaShare is rather simple with Max2Play, you can find it in the Filesystem/Mount menu and it says exactly what to do there to (both to create one and to access it on a windows device). However, depending on the size of library this might (not necessarily) strain the Pi’s computing powers.
1. März 2018 at 13:35 #34158Hi bigsur,
Firstly, try running a reboot and clicking the button again. If you still cannot access the interface, something went wrong in the installation.
Then, please reinstall LMS and select the other version to make sure the issue is not connected to the nightly.
1. März 2018 at 12:49 #34157Hi 7ZollDAU,
Das vor und nach sollte eigentlich bei der Installation des LMS nicht relevant sein. Das Expandieren des Systems läuft seit ein paar Versionen bereits automatisch beim ersten Hochfahren.
Die Log-Ausgabe ist die normale, wenn der LMS nicht gestartet ist.
Wird beim gelben Text der Installationssequenz vom LMS irgendwelche Fehler ausgegeben?
1. März 2018 at 12:28 #34156Hi antonio,
Thank you for your request.
There is actually already a solution for this. A user of Max2Play put it together a year ago. You can find the discussion on a slimdevices topic, here.
28. Februar 2018 at 17:21 #34148Hi contax,
Sorry about the inconvenience. Could you share the debug info log of your WiFi/LAN menu? Also, could you try WPS?
28. Februar 2018 at 17:08 #34146Hi bigsur78,
The last log should not be a problem at all.
Did your install show the button to open the web interface after installation in this last instance?
28. Februar 2018 at 17:04 #34145Leider nein, die beste Option, die wir kennen ist Jivelite.
28. Februar 2018 at 16:59 #34144Hi timb,
There are several 🙂
Wiki on Mounting
Wiki on SambaShare
Wiki on Fritz-Mount (German)
Youtube Video I didHowever, fundamentally, I am not sure about your setup. Do you still have the LMS running on the NAS? If so, you just need the players on the Pi’s and now mounting or server it whatsoever. They are all controlled on one LMS and Squeezer just accesses it and lets you control all players connected to this server.
28. Februar 2018 at 16:54 #34143Hi Myself,
Vielen Dank für die Rückmeldung und die netten Worte!
Über eine positive Bewertung in unserem Shop würden wir uns immer sehr freuen, falls die Lust und Zeit dazu findest 😉
edit: Und wenn du noch Hilfe bei der Suche nach der nächsten Soundkarte brauchst, ruf einfach durch, ich bin Wochentags von 9 bis 17 Uhr im Büro.
28. Februar 2018 at 11:54 #34141Hi bigsur78,
I just set up a tester with a new install of 7.9.0 and unfortunately could not reproduce the error. The install went through. Could you share the error messages in detail here? It should be logged in the debug info window below.
28. Februar 2018 at 11:50 #34140Hi jmkeuning,
You can use the Jivelite GUI in autostart to control those basic features. You can also use the GPIO-pins and rotary encoder or button to bind commands like play or pause directly.
28. Februar 2018 at 11:37 #34138Hi Marc,
Entschuldige die späte Rückmeldung. Ich war die letzte Woche im Urlaub und arbeite jetzt noch chronologisch die Anfragen ab. Durch deinen zweiten Post ist diese leider etwas nach oben gerutscht.
Bitte versuchen einmal, Kodi neu zu installieren. Außerdem kannst du noch den Haken bei „Reinitialize Display (if screen is black or HDMI was not connected on startup)“ setzen, um sicherzugehen, dass das Problem nicht mit einer fehlerhaften Initialisierung des Bildschirms zusammenhängt.
Weiter gibt es in den Raspberry Einstellungen noch die Funktion „HDMI Hotplug“, welche du auch noch ausprobieren kannst.
28. Februar 2018 at 11:33 #34137Hi geert,
With the interface you use to control Squeezebox, please make sure that you have the name of your device (try renaming, to be sure) selected for playback before starting Spotify playback. Otherwise, the server might still not have auto-selected the player at first.
27. Februar 2018 at 17:40 #34118Hallo Jürgen,
das root pw ist „max2play“, also mit sudo solltest du Zugriff haben. Jedoch kennen wir dieses Projekt leider nicht und können anhand der begrenzten Doku auf github auch nicht sagen ob dies auf Max2Play’s LMS funktionieren wird.
27. Februar 2018 at 17:36 #34117Hi albert,
Thanks for the follow-up, let me know if any other issues arise.
27. Februar 2018 at 17:33 #34116Hi okenny,
Sorry about the inconvenience. For the future, this should easily be fixable by connecting via WiFi (network called „max2play“ and then accessing „max2play“ in the browser to remove the aforementioned tick for automatic AP mode and reboot. If the ethernet cable is plugged in during that reboot, the device will automatically switch connections.
27. Februar 2018 at 17:29 #34115Hi guys,
Sorry about the late response. I am just now back from a holiday break for the last week.
@thanat: The playback should work right away through headphones. No change necessary@drewt: Thanks for pointing us in this direction, will check it out soon and see if it makes sense to integrate in Max2Play 🙂
27. Februar 2018 at 17:25 #34114Hi macpac,
Thank you for the follow-up. I am glad your setup is working now 🙂
27. Februar 2018 at 17:22 #34113Hi willy,
Please create a new topic and link to this one for context, otherwise I won’t see posts in threads marked „SOLVED“ as quickly 😉
This is the topic you are referring to.:
The current version of Jivelite has, in fact, the function to switch off the backlight included in the Display Off option under Screensavers. We could validate this by disabling the autofunction and just turning off the display leaving the backlight on. When going back to the default option on Jivelite, the backlight is turned off again.
You can check if this function is active in your version of Max2Play by typing the following command in the console:cat /opt/jivelite/jivelite/share/jive/applets/BlankScreenSaver/BlankScreenSaverApplet.lua
Please check the command line if possible. Please also reinstall Jivelite from Max2Play sources if it still does not work.
27. Februar 2018 at 17:10 #34112Hi jmkeuning,
Sorry about the late response, I way on holiday last week and am still catching up 😉
This is the procedure of how Max2Play tries to connect:
1. Check for ethernet -> connected, done
2. No ethernet -> start WPS scan -> running for 30 seconds -> connected, done
3. No WPS connection established -> start automatic Access Point
4. automatic Access Point started -> access the web interface with any device by selecting „Max2Play“ WiFi in your phone/tablet/etc.
5. Now you can use Max2Play „offline“ until you manually enter your real WiFi credentials in the WiFi/LAN menu of our we interface and reboothope this helps
27. Februar 2018 at 17:04 #34111Hi mnvelocitypilot,
Sorry about the late reply. I was on holiday for the last week and am still going through all the outstanding requests.
Let me first make sure I get the situation correctly:
– You have a share with the files of a USB HDD attached to an Apple NAS
– You used our filesystem mount menu to add the share with HDD’s files on the Apple NAS to your Pi
– You selected the path with the files in the LMS but the files are not found
– The files are found in a different setup with a different NAS (?)
Please clarify if there is anything I got wrong.Ideas:
– Make sure the format of HDD which is correct for the Apple product is also working with RPi
– Try connecting the HDD directly to the Pi and create a SambaShare on the path to share it with the rest of the network
– Make sure your files and folders of music do not have any special rights or formats to rule this out as a source of error27. Februar 2018 at 16:51 #34110Hi fahzz,
This is the folder in the Pi that is used for the SambaShare. You can just use the example, or something like „media/usb2“ which is then created instead 😉
27. Februar 2018 at 16:46 #34109Hi Wolfgang,
Sorry about the inconvenience, and the late response, I am still working through the posts from my holiday break over the last week. Kodi only allows a few slots for sound output. So you need to deactivate built-in audio in the Raspberry Settings and reboot. Afterwards, the DigiOne output should slot in the Kodi selection. Pulse should only be there for bluetooth.
27. Februar 2018 at 16:45 #34108Hi linlar,
Is this in some way different from the integration that’s already included in our Jivelite plugin in the dropdown?
27. Februar 2018 at 16:35 #34107Hi Myself,
Entschuldige die späte Rückmeldung. Ich war letzte Woche im Urlaub.
Dein beschriebenes Setup sollte soweit funktionieren. Wir können leider keine Garantie für jeden BT-Lautsprecher geben, aber grundsätzlich ist das genau das Einsatzgebiet unseres Bluetooth-Plugins.
27. Februar 2018 at 16:32 #34105Hi geitje,
Thanks for sharing your process and the solution you found for your issue 🙂
27. Februar 2018 at 16:31 #34104User Nymphen96 reported issues with the RPi Camera Plugin. We will look into it.
27. Februar 2018 at 16:30 #34103Hi Nymphen,
Danke für die Info, ich nehm es mal in unser Stretch-Thema mit auf 🙂
27. Februar 2018 at 16:29 #34102Hi guys,
Just in case there’s anybody else wondering how this could currently work, the plugin „Spotty“ is the new ideal solution for Spotify with Squeezebox systems 😉
27. Februar 2018 at 16:28 #34101Hi Rolders,
Raspberry Settings and its sound card selection field are premium features. so you need an active license to save it.
The default driver for HiFiBerry-based cards is HiFiBerry DAC without the „+“.
-
