Forum Replies Created
-
-
17. September 2018 at 9:41 #37861
Hi dcsooner,
Thanks for the update. However, it should work with Stretch, too.
17. September 2018 at 9:39 #37860@dennis:
Do you have a sound card active? If so, it is not active. The hw:1 would point to the sound card’s built-in hardware control.
The -C 5 tells the player to stop occupying the card if it’s inactive, allowing other players to access it.
If you do not have a sound card, the audiojack output itself might be reason for inadequacies in the playback. Although it should not stop, so please also paste the debug info from your Squeezebox Server.@hilary: your outputs seem to indicate that the radio station’s url was not reachable. Please try a big mainstream station to make sure this issue is not universal.
17. September 2018 at 9:21 #37858Hi Phanegem,
When you installed the Jivelite IR support, did you get the following lines as the last of your install sequence:
Preparing to unpack .../lirc-x_0.9.4c-9_armhf.deb ... Unpacking lirc-x (0.9.4c-9) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up lirc-x (0.9.4c-9) ... Jivelite lirc configuration finished finished - Reboot needed: Click here to Restart Device14. September 2018 at 16:48 #37834Hi Dennis,
Sorry, I was unclear. Both referred to the Audioplayer plugin menu.
Please paste the debug info from the audioplayer.
You can find the command line options in the advanced settings of Squeezelite in the Audioplayer menu.
You do not need to enter the console or parse any direct commands with Max2Play 😉14. September 2018 at 14:05 #37832Please paste the debug info from the audioplayer. Please also check the command line options for Squeezelite and add „hw:1“ if it is not in there.
13. September 2018 at 16:59 #37830Hi Dennis,
Please check your debug info in the Squeezebox Server and make sure it is not re-indexing during your playback. This might a reason.
You can also check the Settings/Reboot menu of Max2Play and its Health Checker which should be green. If it’s not, please copy its output here.
13. September 2018 at 11:44 #37823Hi Phanegem,
You can install the JustBoom Plugin and use its config for Jivelite infrared control (
Additional Settings for Justboom-Cards -> IR Control).13. September 2018 at 9:36 #37822For guests you can also activate the DLNA interface plugin for LMS and see if the device shows up on DLNA apps.
12. September 2018 at 13:00 #37814Wenn du ein Backup hast, kannst du das erstmal nutzen.
Wir werden jedoch versuchen, zeitnah einen Fix zu veröffentlichen. Das Problem scheint mit Stretch-Paketen zusammenzuhängen, also nicht direkt am 2.47 Update zu liegen.
12. September 2018 at 10:21 #37812Hallo Poseidon,
Vielen Dank für deine Anfrage.
Wir konnten das Problem leider auch feststellen.
Wir werden dies ausgiebig prüfen und dich hier auf dem aktuellsten Stand halten.
Bitte nenn uns noch dein genaues Setup (Pi Modell, Peripherie, etc.)
12. September 2018 at 9:21 #37811Hi radiomog,
Thanks for the quick update.
Please do let us know if the memory card was at fault if you find out.
11. September 2018 at 17:00 #37805Hi Mike,
Usually, the device name should show up next to its IP address in brackets. Please make sure you have the current version of Max2Play and try renaming your device once more to see if your router can parse its name then. Our WiFi IPs are not static but they should not change unless your router re-assigns them.
11. September 2018 at 16:15 #37804Hi Alexander,
Es gibt etliche Einstellungen für den Squeezebox Server und dessen Scanning, Indexing, etc. Du findest Sie nach dem Klick auf das Squeezebox Server Webinterface über den Settings-Button unten rechts. Dort kannst du auch „Information“ checken, weshalb dein Server durchgehend auf die NAS zugreift Server- und Scanner-Log.
11. September 2018 at 14:18 #37799Hi Gianpaolo,
Indeed it does, however, the changes in Raspbian when they migrate to a new version can only be used with a new image. We’ve had to create a Stretch image right away when the Raspberry Pi 3B+ came out because it did not support the older versions‘ Kernels and would not even boot with wheezy or Jessie.
It is likely that some kind of dependency is the cause of this issue for the installer and to be able to make the installer compatible with the newest models and version Max2Play, we have to focus on the newest.You can save LMS settings and create a backup img-file of your image or just burn it to a new card for a physical backup with our image burner plugin.
11. September 2018 at 14:14 #37798Hallo Termi,
Für PVR-Addons haben wir einen Container im Webinterface zum installieren (Install Kodi 17 PVR Addons).
11. September 2018 at 11:40 #37795Hi gianpaolo,
Thanks for the quick response.
This is probably the reason for the issue, wheezy is a rather old version of Raspbian.
We already went through Jessie lite and to the newest version Stretch during the last few years.
First, you can try making an apt-get upgrade in the Raspberry Settings to update your packages.
But if that does not solve the issue, please consider burning our newest image based on Raspbian Stretch.
You can download it free from this website and follow the wiki on how to burn it.11. September 2018 at 10:54 #37791Hi Mike,
Thanks for your detailed posts, I’ll try to answer all your questions:
– Your license can be activated on all your Pi’s. Try removing the license, saving with a blank field, rebooting and re-entering the license. Make sure your device is connected to the internet in the Health Checker (green box to the right in Settings/Reboot).
– Your player can work without the license since both HiFiBerry and Audioplayer are free plugins. You can check which ones need a premium license and which ones are free in our plugins overview webpage.
– Activate network Look-Up on both your device to easily switch between the two. After activating, a little box will show up in the webinterface’s upper right corner, listing all the max2play devices in your network.
– For access on your phone, make sure it is connected to the same network and add a slash at the end („max2play/“). Also, make sure your browser parses the url correctly and perhaps try a different one to rule it out as the source of error.
11. September 2018 at 10:54 #37790Hi Mike,
Thanks for your detailed posts, I’ll try to answer all your questions:
– Your license can be activated on all your Pi’s. Try removing the license, saving with a blank field, rebooting and re-entering the license. Make sure your device is connected to the internet in the Health Checker (green box to the right in Settings/Reboot).
– Your player can work without the license since both HiFiBerry and Audioplayer are free plugins. You can check which ones need a premium license and which ones are free in our plugins overview webpage.
– Activate network Look-Up on both your device to easily switch between the two. After activating, a little box will show up in the webinterface’s upper right corner, listing all the max2play devices in your network.
– For access on your phone, make sure it is connected to the same network and add a slash at the end („max2play/“). Also, make sure your browser parses the url correctly and perhaps try a different one to rule it out as the source of error.
11. September 2018 at 10:22 #37779Hi nick,
Thanks for the quick update, glad to hear your setup is working properly now 🙂
11. September 2018 at 9:54 #37777Hi guys,
Please let me know which version of Raspbian your Max2Play is based on (Settings/Reboot debug info).
With the newest image we offer, this would be the relevant output:
#### LINUX-VERSION #### Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.3 (stretch) Release: 9.3 Codename: stretch11. September 2018 at 9:51 #37776Hallo Carsten,
Danke für die schnelle Rückmeldung.
Die fehlerhafte Version und dessen Fehlermeldung deutet auf eine ältere Version des Plugins hin.
11. September 2018 at 9:09 #37770IMPORTANT:
There was a bug fix we added to our version 2.47 of Max2Play.
It fixes a problem with Bluetooth packages that can occur if you updated Max2Play recently.
Everyone updating their Max2Play now is not affected by this issue.
Anybody experiencing issues with their Bluetooth plugin:
– Install the plugin again in Settings/Reboot (Link) or make a beta update and then a normal update. This will fix the issue.
– If you install the plugin again and you were affected by the bug, you should get the following message when accessing the plugin after the new install:
Fixed Service File for Bluealsa compatibility for previous installs.11. September 2018 at 9:05 #37769Hallo,
Das Problem mit Bluetooth sollte nun gelöst sein. Es handelte sich um Änderungen der RPi Bluetoothpakete.
Jeder, der jetzt ein Update macht ist nicht betroffen.
Leute die das Problem haben, können einfach das Bluetooth Plugin neu installieren über Einstellungen/Reboot (Link) oder ein Beta Update machen und danach erneut das normale Update auf 2.47.
10. September 2018 at 17:23 #37758Yes, manually adding packages might not be ideal.
Please try uninstalling and reinstalling. During that, please wait ca. 1 minute after no new text shows up before rebooting.
10. September 2018 at 17:03 #37754Hallo Fam.Weigand,
Danke für die Anfrage. Ich konnte das Problem erfolgreich an einem RPi3B reproduzieren.
Wir werden umgehend versuchen, das Problem zu lösen und hier den aktuellen Stand veröffentlichen.
edit: der neueste Download von Max2Play ist weiterhin das 2.45 Image welches auf unserem Download-Reiter im Hauptmenü erhältlich ist.
-
This reply was modified 6 years, 4 months ago by
Heiner.
10. September 2018 at 16:32 #37749Hi Gianpaolo,
Thank you for contacting us with your issue.
I just tested the installer on a new image with RPi3B and was not able to recreate the issue.
The last three lines of yellow text in your webinterface should be:Processing triggers for fontconfig (2.11.0-6.7) ... Setting up gsfonts-x11 (0.24) ... Finished - please click here to reload Page to see ChangesWhat is your exactly hardware setup?
What user are you referring to? You should not be able to do anything in our plugin before installing the server.
10. September 2018 at 11:57 #37740Hallo Carsten,
Bitte entferne den autostart in allen Playern in „Audioplayer“ und check die debug info Ausgabe nachdem du Spotify Connect startest.
10. September 2018 at 11:56 #37739Hallo Termi,
Wir haben bisher noch keine Erfahrungen mit der Dreambox machen können.
Du kannst dich jedoch an der Kodi-Version und dessen Features orientieren. Max2Play bietet die Version 17.6 von Kodi mit allen Features.
Es gibt im Internet verschiedenste Möglichkeiten, Kodi für Streaming zu nutzen.
-
This reply was modified 6 years, 4 months ago by
-
