Forum Replies Created
-
-
13. Januar 2017 at 15:41 #25863
Hallo konus,
Sorry wegen der späten Antwort. Eigentlich sollte der Pi automatisch auf deutsch stehen wenn du in Einstellungen/Reboot deutsch als Sprache und Zeitzone auswählst. Bitte versuch ein frisches Image zu brennen und lediglich die Einstellungen auf deutsch umzustellen. Das sollte reichen um Kanal 12+13 zu nutzen.13. Januar 2017 at 15:38 #25862Hallo Stefan,
Hast du bereits mit den Command Line Options rumprobiert? Der Parameter volume_range_db könnte funktionieren.Bei Squeezelite mit shairtunes2 kannst du dem Link bei den Command Line Options folgen für verschiedene Beispiele.
13. Januar 2017 at 15:31 #25861Hallo Gerd,
Danke für deine Anregungen. Leider händelt jedes Gerät die Bluetooth-Kopplung anders und es kann deshalb zu Diskrepanzen zwischen verschiedenen Geräten im Zusammenhang mit Max2Play kommen. Als Fix für eine sofortige Besserung empfehlen wir dir die HTTP-Commands. Dies sind die Zeilen in der URL-Leiste die man sieht wenn man einen bestimmten Button oder Befehl im Max2Play Webinterface startet. Diese lassen sich in jedem Gerät als Schnellfunktion einfügen und im lokalen Netz direkt ausführen. eine Auswahl dieser Befehle findest in unserem Beta-Voice Control Plugin.13. Januar 2017 at 15:26 #25860Hi Sonicxs,
Sorry about the late response. I just tested the installation of shairtunes2 on a test device and did not encounter your error. Please try burning a fresh image, updating to our most current version and installing the SBS and shairtunes2 again.13. Januar 2017 at 15:25 #25859Hi noxid8,
We currently only support Odroid and Raspberry Pi for Max2Play. However, we do recommend the Raspberry Pi 3 first and foremost for its versatility and great support of all our features. The 7.9 nightly installation of the Squeezebox Server with our plugin support works very smoothly on the Pi3.13. Januar 2017 at 15:20 #25858Hi epkepk,
Currently, there is no option to change the brightness of the touchdisplay. However, you can select the black screen as a screensaver and have it start after a few seconds to ensure minimal power usage.13. Januar 2017 at 15:18 #25857Hi std,
Ich habe dein Topic mal in dieses Forum verschoben. Welchen Bootloader meinst du? Falls es sich um den BerryBoot handelt, dort sind wir inzwischen in der Liste der verschiedenen Images vorhanden: http://berryboot.alexgoldcheidt.com/images/Die Auswahl lässt sich bequem über die Ausgabe des Pi beim ersten Boot mit einer BerryBoot SD-Karte machen. Dort wählt man einfach das zuvor geladene Image von Max2Play aus und dieses wird gebootet.
13. Januar 2017 at 15:12 #25856Hallo herman,
Bitte versuche es mit der Hardware-Volume-Optimierung: https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/13. Januar 2017 at 15:11 #25855Hi aschiller,
Have you contacted slimdevices forums regarding this setup? We have not yet had a lot of experience with the WaveInput plugin and its capabilities, however, we would be interested in hearing what could be possible with it in combination with Max2Play.13. Januar 2017 at 15:07 #25854Hi kvo1,
You can either use this way: https://www.raspberrypi.org/documentation/linux/usage/rc-local.md
Or a cron job: https://www.raspberrypi.org/documentation/linux/usage/cron.md
To add things to start from boot.13. Januar 2017 at 14:59 #25853You could use it to edit the boot sequence. You can also use this way: https://www.raspberrypi.org/documentation/linux/usage/rc-local.md
Or a cron job: https://www.raspberrypi.org/documentation/linux/usage/cron.md11. Januar 2017 at 18:14 #25797Hi Ross and Steve,
So sorry about the late response. We are still working on getting up to date on all technical requests since Christmas. Thank you for your patience.Please check your share and how you specified the login data (username and pw). Try accessing the share from a PC, the same procedure is used and the same input should work on Max2Play’s interface. http should not be included in the input. Please check the IP address of your diskstation to make sure you have selected the right one. This is the most ideal input for the share to be recognized. Please create another user than „admin“ or „guest“ and assign it its own password. We have a diskstation here at work and actually have not encountered any of these issues before, so we are especially interested in what is causing your errors.
11. Januar 2017 at 15:28 #25771Hi kris,
You might want to try adding a hardware volume control parameter for your Amp: https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/
You can also try selecting the sysdefault instead of the default selection as your sound card driver.9. Januar 2017 at 17:56 #25717Hi tarmo,
Sorry about the late response. Please access the Max2Play web interface from any browser in your local network (smartphone, PC, etc.) and head to the Raspberry Settings. There in the bottom menu you will find the option „Install Iceweasel“ to install a browser on your device.9. Januar 2017 at 17:50 #25715Hi guys,
Happy new year! With it comes a new update on our Audiophonics development:
We have been working on an image and a specific plugin for Audiophonics. This plugin is already available in a beta release under http://shop.max2play.com/media/downloadable/beta/audiophonics.tar and it offers one-click installation for the Sabre V3 sound card, the Audiophonics power button and the Winstar OLED Display individually. This allows a simple and quick configuration of the whole RaspDAC setup. We will also officially inform the community with a blog article and more information soon. Stay tuned9. Januar 2017 at 17:44 #25713Hi Bernard,
The binary can be found under/opt/squeezelite/squeezelite
The launch script is under /etc/init.d/squeezelite
And the script for the continuous use is /opt/max2play/start_audioplayer.shPlease note: If you manually edit the last one, you have to do this again after every update since this will revert your manual changes.
9. Januar 2017 at 17:41 #25712Hi Thomas,
Sorry about the late response. Please make sure have your antivirus deactivated and check the Squeezebox Server’s debug for further information. Also make sure you have your filesystem expanded in the Settings/Reboot menu. We could access the advanced options for the upnpbridge in our tester, so it should be possible for the RPi 2/3. Please make sure you select the binary „armv6hf“ once you can access the advanced options.9. Januar 2017 at 17:38 #25711Hi Perlhuhn,
Sie können die Aktivitäts-LED unter
/sys/class/leds/led0 editieren. Weiterhin können Sie das Raspberry Pi Forum für diese und ähnliche grundsätzliche Fragen zum Raspberry Pi kontaktieren.9. Januar 2017 at 17:35 #25710Hallo Familie Weigand,
Sie können die Aktivitäts-LED unter
/sys/class/leds/led0
editieren.
Die LAN LED lässt sich nicht ohne weiteres manipulieren.9. Januar 2017 at 17:30 #25709Hi jcu,
Sorry about the late response, but thank you so much for the dedication to our project and your work. As you mentioned, we have been working on an image and a specific plugin for Audiophonics. This plugin is already available in a beta release under http://shop.max2play.com/media/downloadable/beta/audiophonics.tar and it offers one-click installation for the Sabre V3 sound card, the Audiophonics power button and the Winstar OLED Display individually. This allows a simple and quick configuration of the whole RaspDAC setup. We will also officially inform the community with a blog article and more information soon. Stay tuned9. Januar 2017 at 17:18 #25708Hi Welle,
Sorry about the late response. Please check the format of your drive and, if possible, format it to NTFS. This should definitely make it recognizable to the Pi.9. Januar 2017 at 17:15 #25707Hi lynoo,
Sorry about the late response. Please add these parameters to the command line options in the advanced options for your audio player (squeezelite or shairport):
hw:CARD=D2Qute,DEV=0
This will connect your sound card directly to the hardware volume control and hopefully get rid of the cracklings.
9. Januar 2017 at 16:32 #25704Hi lynoo,
You might have to check the rights settings of your files and folders. They can hinder the LMS from scanning your library correctly.9. Januar 2017 at 16:19 #25701Hi Gerstel,
Sorry about the late response. Have you checked whether your music files and folders might have special writing and reading rights? This might result in the LMS not integrating them correctly.9. Januar 2017 at 16:13 #25699Hi Andreas and Bill,
Thanks for your requests. We use shairport both in our Audioplayer plugin and in the newly added MultiShairport plugin. We just tested our current shairport client with a current iOS device and did not encounter any issues. We could play several songs continuously without interruptions or having to click play again. You can also still use the shairtunes2 plugin for the LMS which turns all your squeezelite players into airplay players. We will look into the possibility of including shairport-sync in a future update. If you found wrong documentation stating that we already use shairport-sync, please point us toward these mistakes and we will fix them.
9. Januar 2017 at 16:07 #25698Hi wenkman,
What you can do is utilize the HTTP-Requests. You can find some examples in our voice control plugin beta. To pause a player, you need: Pause for this device:
http://SERVERDEVICENAMEORIP:9000/status.html?p0=pause&player=MACADDRESS6. Januar 2017 at 15:42 #25611Hi nick and std,
We tried to point the necessity of an active phone-ID out in the installation yellow text of the plugin. It is a requirement for the login to work.I might make another How-To on exactly the steps you have to take to activate the plugin in the future. Thanks for your feedback.
6. Januar 2017 at 14:48 #25607Hallo Thorsten,
Wie std bereits erwähnte ist die Lizenz nutzerbezogen und du benötigsten nur eine, auch wenn wir als Communityprojekt natürlich für jeden Lizenzkauf dankbar sind.
Pro lokalem Netzwerk benötigst du jedoch nur einen Squeezebox Server. Mit diesem kannst du dann alle Player und dessen Pi’s kontrollieren und mit individuellem Playback versehen. Deshalb deaktiviere bitte die überschüssigen Server. Bezüglich deiner WLAN-Probleme könntest du noch das WPS feature austesten.
6. Januar 2017 at 14:05 #25605Hi Paulieserver,
You can find several options for this in the Raspberry Settings. Chief among them the HDMI Force Hotplug. You can also activate the „Reinitialize Display“ option in the Kodi menu of our web interface.6. Januar 2017 at 13:13 #25600Hi Slartibartfast,
The Idle time is currently 180 seconds. If you want to change this preset, you need to go to the console and enter the following:
nano /etc/default/hd-idle
and then in the following line’s output
HD_IDLE_OPTS="-i 180 -l /var/log/hd-idle.log"
readjust the time. -