Forum Replies Created
-
-
6. November 2017 at 15:15 #32309
Hi Patrick,
Unfortunately, we only offer images based on Ubuntu 14 for U3 and Ubuntu 16 for XU4.
You can find these images on our download page. The U3 image is in the legacy section below.6. November 2017 at 14:35 #32308Hi sb,
Kannst du noch den Debug Info Log (ganz unten im Squeezebox Server menü) kopieren und hier teilen?
Grundsätzlich ist die einfachste Herangehensweise wahrscheinlich das Neuinstallieren des Servers. Du kannst die bisherigen Einstellungen unten speichern und dann mit dem selben Button wie beim ersten Mal eine neue Installation starten.
6. November 2017 at 13:03 #32306Hallo beginner,
Die erste Variable, die ich untersuchen würde, wäre die Internetverbindung. Wenn möglich, und falls noch nicht bereits im Einsatz, versuche bitte einmal das Gerät über LAN-Kabel laufen zu lassen um sicherzustellen, dass es nicht an einer schwachen WLAN-Verbindung liegt.
Außerdem kannst du noch Hardware Lautstärke Regelung aktivieren: https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/
6. November 2017 at 13:01 #32305Hi wmrch,
Sorry about the informal response.
Hardware Volume Control connects the sound card’s volume to the end software’s volume control and synchronizes both.
You can find the guide for this configuration in our Wiki: https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/
6. November 2017 at 12:50 #32304Hi paud,
Did you configure the mount of your NAS in our Filesystem/Mount menu? If so, you should be able to remove any mountpoints in there with a button.
The behaviour you described should not occur with a usual mount. Please check what files and folders are in your mountpoint and whether there might be some special rights or files in there.
Please also try mounting a share that only has a few simple files to rule out the possibility of the share’s contents as the source of error.
6. November 2017 at 12:08 #32303Hi Jazzfood,
Thanks for the detailed follow-up. I am glad you got it to work, however as mentioned it should work after just one click on the installation button. We will try to investigate further based on your results, whether this issue is reproducable. Thanks for your help.
6. November 2017 at 12:05 #32302Hi Hydro, this should be no problem as is. The paired Bluetooth speaker and the wired speakers connected can run simultaneously as with two different players using MultiSqueeze:
3. November 2017 at 12:23 #32271Hi atacama,
Add hardware volume control in the command line options:
– For Mixer add „Digital“
– For Command Line Options add “–device hw:0” or “–device hw:1”, depending on whether you have built-in audio active (1) or not (0).3. November 2017 at 12:20 #32270Hi Thorsten,
I assume you are using the Max2Play Spotify Connect and not the Spotty plugin’s new feature for Spotify Connect?
In that case, please try clicking „reinstall“ to get the latest version of librespot on which this plugin is based.
Also, you can add the hw volume control, similarly to Squeezelite.
edit: Du kannst außerdem versuchen, bei den Command Line Options “–device hw:0” oder “–device hw:1” einzutragen. Je nachdem, welchen Slot deine Soundkarte hat (wenn Build-In Audio deaktivier ist, ist es 0, wenn nicht, ist es 1).
3. November 2017 at 12:17 #32269Hi Jazzfood,
I just tested it on a RPi3 and the install went through okay. You should get the blue text
ShellInABox is installed.The normal issue one runs into with shellinabox is that it gets blocked by the browser. But still the „installed“ indicator should be visible after the first installation attempt.
Do you have the button „Open Console Fullscreen“?
3. November 2017 at 11:03 #32267Hi Hydro,
1) The RPi3’s bluetooth module is compatible with most bluetooth speakers. However, we cannot guarantee a specific device to work, aside from the JBL Go which we use for testing. Also, there can always be dropouts with BT technology.
2) Yes, this is specifically the application we added in the 2.0 version of our Bluetooth plugin. Check the plugin’s description text for more info. You can either stream directly to the Pi or to all multiroom players with a custom Squeezebox channel for your phone.
3) Not sure I understand this question. You can only pair one device at a time. But you can pair one Pi with your phone and one with a speaker and stream your phone’s output to all players, including the BT-paired one.
For YouTube sound you can just use the built-in DLnA compatibility to stream with apps like AllConnect or BubbleUPnP to all Squeezebox players.
2nd Post: No, the Bluetooth plugin just handles audio streams, in- and output.
2. November 2017 at 18:01 #32263I mean just for testing, to rule out a faulty PS for the amp+.
I will see tomorrow whether we have a TP-Link dongle in house and then I’d test it as well.
2. November 2017 at 17:58 #32262There sure is, we are just working on the new version based on Raspbian Stretch, which poses unique new challenges. But hopefully we will be able to announce a new update, soon 😉
2. November 2017 at 14:49 #32260Hi Thomas,
Danke für die schnelle Rückmeldung und die netten Worte 🙂
Ich schließe das Thema damit. Du kannst natürlich gerne weitere Ergebnisse und Veränderungen hier teilen.
2. November 2017 at 14:24 #32252Hi Yasmail,
Do you mean HiFiBerry Amp+? The DAC should not have its own power supply.
Please try running it with a normal Pi power supply, if available (5V 2,5A).
Also, are you using the Raspberry Pi 2, or another model?
2. November 2017 at 13:34 #32250Hi Zwaffel,
Unfortunately, do not have the extended pin strip of the tutorial on hand to recreate this setup.
However, you can currently try using the official pinout pins for rotary control, as listed here, instead:
https://pinout.xyz/pinout/amp_zero2. November 2017 at 11:52 #32246Hallo Thomas,
Ich konnte das Problem in der Tat beim ersten Versuch rekreieren. Dort hat es 3 Versuche gebraucht bis die Verbindung aufgebaut werden konnte.
Nach einem Reboot konnte ich dieses jedoch nicht noch einmal feststellen, selbst nach mehreren Neustarts und mit unterschiedlichen Browsern.
Bitte deaktiviere die feste IP, falls noch nicht getan, diese gilt nur für LAN-Verbindung. Gleiches bei der Fritz.Box, um zu sehen ob dies den Sachverhalt beeinflußt.
1. November 2017 at 18:14 #32243Thanks for the follow-up. I will keep this in mind for future troubleshooting.
1. November 2017 at 17:59 #32242Hallo Dicker,
Falls noch nicht geschehen, kannst du mit SambaShare manuell einen Pfad im Max2Play-Gerät anlegen und direkt im Netzwerk teilen. Dort kannst du dann auch Dateien übertragen.
1. November 2017 at 17:24 #32240Hi Yasmail,
So assume you are using a WiFi dongle. What protocol does this dongle support and what is the name of it?
Also, what power supply do you use and what is the rest of your setup?
1. November 2017 at 17:23 #32239Hallo Thomas,
Ich bau das Setup mit dem XU4 mal nach und gucke ob ich das Problem rekreieren kann.
1. November 2017 at 17:19 #32238Hi cramcram,
It varies but the maximum I got was 3 seconds between menus. (RPi3, M2P 2.44, HB AMP2 HAT)
1. November 2017 at 17:18 #32237Hi ad,
It seems Kodi 17 is exclusive to Raspbian jessie or newer. So we would recommend burning a fresh jessie image to get the best Kodi 17 experience.
1. November 2017 at 17:13 #32235Hi Man48,
According to most long-time users of Max2Play, the LMS can handle a very large amount of music and data in general without missing a step with RPi 2 and 3. However, there can always be a specific factor that could slow it down.
You can try removing some of your more heavy files from the library temporarily, to see if this changes the performance.
You can also check the Health Checker on the Settings/Reboot menu, to see if the Pi is working at capacity.
1. November 2017 at 17:10 #32234Hi lemuba,
Firstly, congrats on finding your own solution.
Secondly, if you have not yet, you can add hardware volume control for shairport which is exactly what should fix your volume issue:
1. November 2017 at 17:05 #32233Hi Matthew,
First of all, thanks for the kind words on your first setup. This experience is what we hope for all our customers.
On your issues, it sounds like this might be related to power supply. So if you have any USB periphery, try disconnecting for a test to see if the problem persists and activate USB max current in the Raspberry Settings.
Also, try running the power supply of the Pi on a single outlet.
1. November 2017 at 17:01 #32232Hi shangrilafb,
Danke für die Info, wir gucken uns diese Module mal genauer an.
1. November 2017 at 16:35 #32231Hi dumtratt,
According to the creator of Spotty, the plugin currently has some issues with antivirus software:
http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0&p=898251&viewfull=1#post898251Obviously, this should not be a permanent fix, but you can try temporarily deactivating your AV while authenticating Spotty.
1. November 2017 at 11:26 #32228Hi Nojelc,
Sorry about the confusion. I know it seems counter-intuitive, but the right output device for your Sabre is sysdefault_hifiberry…
Also, check the command line options and if there’s a „hw:0“ in there, make sure to deactivate build-in audio in the Raspberry Settings.
-
