Forum Replies Created
-
-
8. August 2017 at 9:01 #30489
Hi dave,
This is pretty much the feature of synchronize in the Squeezebox Server, in a nutshell. You connect two or more players and once you start playback on any of them, the rest should automatically start as well. Just select the synchronize-feature, select your two adjoining rooms and they should start showing up as a group in your app.
7. August 2017 at 16:36 #30483Hi Tobias,
The Logitech Boom should not require you to use a three character IP ending.
However, you can set an IP of your choice, with two or three characters at the end, if you are connected via ethernet and select and save it in the „Fixed LAN IP Setup“ under WiFi/LAN in the web interface. You might have to save your selection of an IP two times and it can take a few seconds to change, but we tested it successfully today and it should work.
7. August 2017 at 16:28 #30482Hallo Werner,
Ich sehe jetzt erst, dass du eine andere Version von Squeezelite installiert hast. Bitte gehe in das Audioplayer-Menü, öffne die Erweiterten Einstellungen von Squeezelite, mache einen Haken bei „Update Squeezelite“ und klicke auf „speichern“.
7. August 2017 at 16:21 #30481Hi Zanoroy,
I assume you are referring to a solution with Jivelite. If you mean a solution for the LMS web interface, you can have a look at their technical information through the Help-Button at http://LMSADDRESS/html/docs/help.html
With Jivelite, you will indeed need to maned the SlimBrowerApplet in addition to the skin you would use. You can find the file to edit in the following directory in Max2Play:
/tmp/jivelite.txtAlso, you should probably best consult the slimdevices forum where you will also find the originators of Jivelite. Here is the announcement thread of Jivelite: http://forums.slimdevices.com/showthread.php?98156-Announce-JiveLite-cut-down-squeezebox-control-application
7. August 2017 at 16:12 #30480Hi oj,
Thanks for pointing us towards this issue. We will fix it in the next beta update and subsequent release.
For now, you can select „compile from sources“ in the dropdown menu to receive the correct build.
7. August 2017 at 11:45 #30473Hi bencat,
First of all sorry about the inconvenience.
Which version of Max2Play do you currently have? Please update to 2.44 if you have not yet. Also, which version of the LMS do you have installed? If it is not too much of a hassle for your, we recommend installing the new, improved version 7.9 instead of the nightly before.
7. August 2017 at 11:40 #30472Hi schmello,
Wir haben unser Access Point Setup noch nicht mit einem Raspberry Pi 1 testen können. Falls du jedoch dazu kommst, lass uns bitte hier von den Ergebnissen wissen.
7. August 2017 at 11:37 #30471Hi amelie,
Du you have the Pi connected to your network via ethernet or WiFi? If its WiFi, please run it via ethernet for a while to check whether the disruptions continue to rule out the WiFi access as a source of error.
7. August 2017 at 11:35 #30470Hi schmello,
Wir haben den Orange Pi noch nicht mit Max2Play getestet und können daher nicht sagen, ob oder inwiefern Kompatibilitäten bestehen.Die Pi-Images basieren auf Raspbian Jessie lite und die Odroid Images auf Ubuntu, als Anhaltspunkt 😉
7. August 2017 at 11:33 #30469Hi fabien,
Both provide the same sound quality, but we do recommend using the newest version.
7. August 2017 at 11:32 #30468Hi Tecuma and fabien,
What info, if any, do you get in the web interface of Max2Play in Kodi’s menu under „Kodi (Video) start installation – Replaces current Version:“? It should tell you that this version is installed:
2:15.2-2~jessie7. August 2017 at 11:28 #30467Hallo Andreas,
Bitte versuche die Version manuell zu installieren. Hier ist die URL zum einfügen in die Installationszeile:
http://downloads.slimdevices.com/LogitechMediaServer_v7.9.0/logitechmediaserver_7.9.0_arm.deb
7. August 2017 at 11:24 #30466Hi Titanium,
Indeed I could not detect anything problematic about the steps you have taken and your configuration.
While it does not happen very often or easily, the corruption of an SD card can occur. I am happy to hear you were able to mitigate the situation. If anything comes up again, just post in this topic and I’ll be able to respond asap.
7. August 2017 at 11:15 #30465Hi Bassie,
Please select the sysdefault output device in Spotify Connect. You do not have to add any command line options to the Spotify player.
7. August 2017 at 10:46 #30463Hi Piet,
First of all, congrats on starting with Max2Play 🙂
Now for your issue, you have multiple options to control the playback of your Squeezelite player. However, the player itself does not have any interface to control it. The control is handled entirely by the LMS. So you need to access the web interface of the LMS on your NAS. It also has a port similar to 9000, perhaps 9001 or 9002. But you can check it in the network overview of your PC or in the web interface of your NAS.
Another, more convenient way to control your playback is through one of the many great apps for Squeezebox. If you have an Android device, check out Squeezer. With iOS, we recommend iPeng and with Windows, you can with SoftSqueeze. These applications automatically servers and palyers in your network and let you control their playback.
7. August 2017 at 10:06 #30461Hi Ronnie,
Thanks for the heads-up. I marked this thread to indicate the updated situation for other British users.
7. August 2017 at 10:05 #30460Hi linndidi,
Wir haben bereits auf die Umstellung reagiert. Inzwischen gibt es für Max2Play 2 Lösungen für Spotify mit der nötigen Dokumentation.
Einmal das von dir erwähnte Spotty. Hier sind einmal eine HowTo zum Einrichten und einmal die Diskussion hier im Forum:
https://www.max2play.com/en/forums/topic/new-hope-for-spotify-lms-plugin/Und einmal unser eigenes Spotify Connect plugin, welches einen eigenen Player auf dem Pi laufen lässt:
7. August 2017 at 9:37 #30459No problem, if it shows up again, just make a new post 😉
7. August 2017 at 9:35 #30458Hi nwooton,
I just tested the RPi-Display plugin with our Adafruit screen here and the screen shows the boot sequence right after the installation and reboot.
What version of Max2Play are you running? Also, please try removing the display settings and installing the drivers again.
4. August 2017 at 10:46 #30428Hallo Uwe,
Du kannst definitiv noch versuchen, die aktiven Plugins von Drittanbieter auf dem LMS zu deaktivieren, um zu sehen ob das Problem bestehen bleibt.
Gab es inzwischen wieder eine unerwünschte Wiedergabe?
4. August 2017 at 10:43 #30427Hi Steini,
Kannst du beim Ausfall den Log des Servers nochmal kopieren? Dieser sollte um einiges extensiver sein.
4. August 2017 at 10:32 #30425Hi fabien,
Unfortunately, we have not had any experience with these products yet.
However, we hope you find the right setup for your needs 🙂
In case you have not seen it yet, here is also an active discussion on the linked device. You might want to ask about compatibility there:
https://www.head-fi.org/threads/xmos-xu208-usb-bridges-the-latest-gen-has-arrived.803111/4. August 2017 at 10:28 #30424Hi Bassie,
When using other players on this device, like Squeezelite, make sure that these players do not exclusively block or mute the sound card. Add ‚-C 10‘ to the Squeezelite commandline settings in advanced options on the Audioplayer tab, to tell Squeezelite to disconnect from the soundcard after 10 seconds if nothing is playing and make sure to remove the ‚-Q‘ option. Otherwise, the volume will be set to 0 when Squeezelite is paused.
Make sure to ‚Disable IPv6‘ in Raspberry Pi Settings (if not disabled yet).
3. August 2017 at 16:31 #30387Hallo Werner,
Der Parameter -Q synchronisiert die ALSA Volume mit der Squeezebox Server-Lautstärke.
Bitte versuche die Kommandozeile ohne den -Q-Wert einzutragen und teile den Log vom Debug Info hier, falls weiterhin Probleme bestehen.
3. August 2017 at 16:25 #30386Hi Hans,
Have you tried out any Android devices, yet? Normally this should work with iOS as well. However, we do not have an iPhone 4 here to test this. I will check the functionality with iOS again tomorrow.
For now, you can also go the old-fashioned route of our classic tutorial for the Access Point: https://www.instructables.com/id/Raspberry-Pi-Mobile-Media-Center-with-Smartphone-C/
You just need to first connect it via LAN to set up the access point.
3. August 2017 at 13:30 #30374Hi Bassie,
There sure are some log files.
You can find logs for all your plugins in the bottom of the web interface by clicking on „Debug Info“.
Do you have the newest version of Max2Play? If so, please also uncheck the new Access Point Autostart (and reboot) to rule it out as a source of error.
3. August 2017 at 13:27 #30373If you are using Squeezelite or any other player as well, have you tried disabling it for a while to see whether the problem with Spotify Connect persists?
Generally, this issue is probably related to the Spotify servers. But this step would rule out Squeezelite interference as the source of the error, which could also be related.
3. August 2017 at 12:50 #30370Hi Tecuma,
By empty do you mean completely empty or just the contents of the page and the main menu is still visible?
Also, which version of Kodi did you run before the update and can you reach all the other plugin pages?
3. August 2017 at 12:46 #30368Hi amelie,
Have you done the steps in the web interface, yet?
When using other players on this device, like Squeezelite, make sure that these players do not exclusively block or mute the sound card. Add ‚-C 10‘ to the Squeezelite commandline settings in advanced options on the Audioplayer tab, to tell Squeezelite to disconnect from the soundcard after 10 seconds if nothing is playing and make sure to remove the ‚-Q‘ option. Otherwise, the volume will be set to 0 when Squeezelite is paused.
Make sure to ‚Disable IPv6‘ in Raspberry Pi Settings (if not disabled yet).
Also, do you have any command line options set up in the player’s interface?
-
