flysurfer

Forum Replies Created

Viewing 30 posts - 121 through 150 (of 266 total)
1 2 3 4 5 6 7 8 9
  • Back to forum
    Posted in: Enjoy Music in Bedroom and Bath – Alarm, Sleeptimer, Integrated Button Control
  • flysurfer Moderator
    23. September 2016 at 10:36 #23168

    Hi asplundj,

    with the Google Music Plugin-installer on the Squeezebox Server tab in Max2Play web interface, it is not needed to do any further plugin installation within the LMS.

    We only tested this with the Jessie version, as the old Wheezy-version will not be fully supported with further addons (to difficult for us to test all versions).

    To install plugins from SSL-secured repositories within LMS your hint on libio-socket-ssl-perl is very good. We will add this as a patch to the Max2Play Squeezebox Server installation, as a lot of Repositories are hosted on Github.

    Cheers,
    Stefan

    flysurfer Moderator
    22. September 2016 at 11:44 #23133

    Hallo Tom,

    der Fehler liegt an der URL-Codierung des „+“ Zeichens. Das muss als „%2B“ eingetragen werden, dann funktioniert es.

    Bsp: http://max2play:9000/status.html?p0=mixer&p1=volume&p2=%2B6&player=b8:27:eb:df:27:b3

    Oder in deinem Beispiel
    http://bad:9000/status.html?p0=mixer&p1=volume&p2=%2B6&player=b8:27:eb:f8:35:84&start=0

    Viele Grüße
    Stefan

    flysurfer Moderator
    16. September 2016 at 20:53 #23072

    Hi,


    @gapmedia    : once you change the Kernel on the Max2Play Image to support the Wolfson/Cirrus card, it won’t run anymore because the Kernelchange was only working with the older „debian wheezy“ based Max2Play version (you may still download this version on our page). I also removed this option in the newest version from the Raspberry Pi Settings Addon.

    @Jac: The WPS connection is just a way to do it more simple on startup for people who do not want to connect a LAN cable and have a router with WPS. In your first screen, do you find your wifi network in the list after you click „start scan“? If yes, after selecting your network and adding your password, does it show that you are connected or does it show any errors?

    Regarding IPv6: you may disable this in the Raspberry Pi Settings Addon. If your Router supports IPv6 your Raspberry will also get an IPv6 address besides IPv4 and the URL in your Browser may change on a reboot of Max2Play… If you have problems, either disable IPv6 or enter the IPv4 Address instead of the name (e.g. „http://max2play“) in your browser. As IPv6 gets more popular I will try to get everything working with IPv6.

    Stefan

    flysurfer Moderator
    16. September 2016 at 11:33 #23064

    Nachtrag zur Lösung

    Diese Änderung wird in einem der nächsten Updates vorhanden sein und setzt automatisch den Nutzer für Squeezelite auf „root“ wenn der GPIO Parameter gesetzt ist (audioplayer.conf SYSTEM_USER bleibt „pi“):
    in Datei /etc/init.d/squeezelite 

    
SQUEEZELITE_PARAMETER=$(grep -a "SQUEEZELITE_PARAMETER" /opt/max2play/audioplayer.conf | sed -n -e 's/^[A-Z_]*\=//p')
# NEUER CODE
if [ $(echo $SQUEEZELITE_PARAMETER | grep " -G " | wc -l) -gt "0" ]; then
    USER=root
fi
# ENDE
    flysurfer Moderator
    16. September 2016 at 11:26 #23063

    Hi Felix,

    das hat mit dem Ändern des Nutzers zu tun. Es gibt ein paar Scripte (auch das zum Starten von Jivelite), die nach dem Benutzer prüfen (in der audioplayer.conf) und wenn dieser nicht „pi“ ist dann automatisch „odroid“ nehmen. Das liegt ein wenig an der Entwicklung von Max2Play (war anfangs für ODROID).
    Um es zum laufen zu bringen müsste man entweder im Startscript von Squeezelite unter /etc/init.d/squeezelite den USER auf „root“ setzen und in der audioplayer.conf wieder auf „pi“ (am einfachsten und sichersten) ODER im Start von Jivelite (Autostart beim Booten sollte reichen) in der Datei /opt/max2play/start_audioplayer.sh die Zeile im Bereich wo Jivelite gestartet wird
    USER=$(grep -a "SYSTEM_USER" /opt/max2play/audioplayer.conf | sed -n -e 's/^[A-Z_]*\=//p')
    ersetzen durch
    USER="pi"
    Diese Lösungen sind allerdings nicht Update-Sicher, da bei einem Max2Play Update die Dateien wieder überschrieben werden.

    Das die WiringPi Bibliothek immer als sudo oder root ausgeführt werden muss, lässt sich wohl so einfach nicht ändern. Damit muss Squeezelite leider mit der GPIO Option auch als sudo oder root laufen. Ich werde dafür noch ein Update für das Squeezelite Startscript bauen, was auf den GPIO-Parameter prüft und anschließend direkt den Nutzer auf „root“ setzt.

    flysurfer Moderator
    7. September 2016 at 14:45 #22910

    Hi JavM,

    it seems like your speakers need special identification with a Pin-Code – at least the Debug info says
    Enter PIN code: Trusted: 0 -> 1

    Did you push the „Connect“ button on your speakers when clicking connect in the Max2Play web interface?

    The messages also says Connected: 1, that indicates it was paired correct, but cannot be used until the code is entered and the device is „trusted“.

    As the Max2Play Bluetooth Plugin does not offer this method of pairing, I think it might be necessary to do the pairing one time from the command line. This has to be done only once:
    – Login with SSH (Putty) or use the Remote Control Plugin from Max2Play to login with SSH via Web interface as user „pi“ with password „raspberry“.
    – start /usr/bin/bluetoothctl
    – enter trust 00:1D:DF:50:67:D8 and enter the pin when asked

    flysurfer Moderator
    16. August 2016 at 15:15 #22292

    Hi,

    something seems to have gone wrong while installing / deinstalling some services. Please use the following code for your rc.local:

    #!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
  printf "My IP address is %s\n" "$_IP"
fi

#Max2Play
sudo -u pi -H -s /opt/max2play/autostart_xbmc.sh > /dev/null 2>&1 &

#Network Check for Mountpoints
COUNTER=0;while [ -z "$(/sbin/ifconfig eth0 | grep -i 'inet ad')" -a -z "$(/sbin/ifconfig wlan0 | grep -i 'inet ad')" -a "$COUNTER" -lt "5" ]; do echo "Waiting for network";COUNTER=$((COUNTER+1));sleep 3;done;set +e;/bin/mount -a;set -e;

#Max2Play Start Audioplayer
sudo -u pi -H -s /opt/max2play/start_audioplayer.sh > /dev/null 2>&1 &

if [ "$(LANG=C && /sbin/ifconfig eth0 | grep 'inet addr:' | wc -l)" -lt "1" ]; then sudo /opt/max2play/wps_config.sh; fi

exit 0

    If you remember what you did before this happened, please tell us and we will fix the bug.

    Thx.

    flysurfer Moderator
    11. August 2016 at 11:03 #22181

    Hi Cyn,

    could you try to update to latest Beta on Settings tab of Web interface or install the Beta of the Plugin with the Link http://shop.max2play.com/media/downloadable/beta/remotecontrol.tar

    This will offer some more details on the page. After updating you can check if ShellinaBox is running at the bottom – just click on DEBUG.

    It should look similar to this:
    Max2Play Remote Control SSH

    If it doesnt show any process running, please try to uninstall and reinstall ShellinaBox.

    Stefan

    flysurfer Moderator
    9. August 2016 at 18:13 #22125

    I just finished building the CPAN resources for ARM and Perl 5.22. Michael normally doesn’t build the arm binaries as he has no Pi/Odroid.

    I also adjusted the LMS-Installer Script (in BETA of Max2Play) to fetch the compiled sources from our server and put them into the right place…

    If you like, you may use the installer script for Max2Play -> update to latest Beta with Web interface -> intall LMS via Web interface… no guarantee, but this should work – I will test it tomorrow with a fresh install.

    • This reply was modified 8 years, 3 months ago by flysurfer.
    flysurfer Moderator
    9. August 2016 at 14:27 #22099

    I updated the installer script for Max2Play to work with ODROID Ubuntu 16.04. There are still some other issues due to the new Ubuntu version that need to be addressed within the web interface of Max2Play, but the basic installation is working.

    I will publish a Max2Play-Version for the ODROID XU4 and Ubuntu 16.04 in our Download section within the next week.

    flysurfer Moderator
    8. August 2016 at 17:28 #22085

    Hi Bob,

    there might be some problems due to php7 and some config file changes. LMS as nightly build comes only with Perl 5.20 support for ARM, so this libraries need to be build.

    I will have a look at the Max2Play installer script and see if I can fix it to work on Ubuntu 16.04 once I find the time for it.

    flysurfer Moderator
    8. August 2016 at 12:17 #22076

    What does the Plugin page say after you installed? Does it show „ShellInABox is installed“ and a window below saying „connection is not secure“, or does it only show the „install“ button? You may also Update Max2Play to the latest beta on the settings page and try again.

    flysurfer Moderator
    12. Juli 2016 at 14:46 #21501

    Good news – thanks to Marting, there is now an easy way to update the Joggler Skin with the changes from Martin. Just choose the Patch in the dropdown menu for the skins on Jivelite Page of Max2Play web interface and click install.

    This is now available in the Beta of Max2Play and will be part of the official 2.34 release.

    flysurfer Moderator
    12. Juli 2016 at 10:39 #21447

    Thanks to OneArmedBandit this bug is solved now 🙂 I changed exactly the code you posted.

    I’ll let you know when we have new plugins for testing and send you the forum links for discussions.

    flysurfer Moderator
    8. Juli 2016 at 15:24 #21341

    Hi Hammerhead,

    well, that doesn’t sound too good… we updated the latest prebuild-sd-card-images to version 2.32. Maybe you start again with a fresh image. SD-Card expansion and wifi should work without any problems (as long as you start the expansion before the card is full). If you have a Pi 2 and not a Pi 3 with buil- in wifi, it might depend on your wifi-stick if anything is not working correct (e.g. disconnects). The kodi package is part of the image – no need to install anything.

    So what are the major benefits of Max2Play: if you are only using you player for Kodi via HDMI and nothing else, you can take OpenELEC or some other distribution. If you want a flexible system with support of different players (Audioplayer, Multi-room Setup) and a lot of other things (see our features / plugins page) you won’t find a system that is this easy to configure. In other words, Kodi is just one little part of Max2Play.

    flysurfer Moderator
    5. Juli 2016 at 16:58 #21223

    Raymond, thanks for your investigation 🙂

    When you install jivelite, it tries to keep the settings but deletes everything in the jivelite folder and this also deletes the custom skins that may have been installed before.

    flysurfer Moderator
    5. Juli 2016 at 14:42 #21209

    Hi Raymond,

    did you choose the Digital Clock Screensaver in the Settings for the „When Off“ setting (sounds like you have set Blankscreensaver in the „When Off“ event)?

    flysurfer Moderator
    4. Juli 2016 at 15:37 #21140

    @OneArmedBandit:
    Would you like to participate in further testing and/or Max2Play development? Your approach to solve the problem and your testing skills could help us a lot for new Addons / Features / Hardware!

    We are currently building a developer area for Max2Play. Main goal is to make it easier for developers to create custom Max2Play Addons and share them with the community.

    All the best
    Stefan

    flysurfer Moderator
    4. Juli 2016 at 14:20 #21130

    Thanks a lot for finding that bug and your detailed report! We created a fix that is applied with any update (beta update and 2.32 update) that solves that issue.

    Cheers,
    Stefan

    flysurfer Moderator
    4. Juli 2016 at 11:16 #21092

    Hi Bristow,

    thanks for sharing your code! I changed it a little to keep the JogglerSkin working and added the changes to the Jivelite installer in Max2Play. If anyone is interested: update Max2Play to the latest Beta version and install Jivelite from Source (not the compiled version).

    Stefan

    flysurfer Moderator
    28. Juni 2016 at 18:16 #20905

    Hi,

    if Jivelite doesn’t show any visualisation after adding the „-v“ parameter to the startup of Squeezelite, it might be neccessary to „Reset Jivelite Settings“ on Jivelite Tab of Max2Play web interface. After this you must restart Jivelite and choose your skin (Joggler Skin for 7″ touchdisplay) and your language again. VU-Meter and Spectrum should now show up when playing music.

    flysurfer Moderator
    20. Juni 2016 at 14:32 #20758

    Hi Bristow,

    you have to modify the Clock Applet in „/opt/jivelite/jivelite/share/jive/applets/Clock/ClockApplet.lua“ and add the skinname that is used for your 3.2inch display with the correct positioning for the elements shown on the screen. The function you have to modify is:

    
-- DIGITAL CLOCK SKIN
function Digital:getDigitalClockSkin(skinName)

    Try to have a look at how we changed the Digigtal Clock positioning for the Joggler Skin. We would be happy, if you share your results. You may create a patch of the changes that we can add to Jivelite.

    All the Best,
    Stefan

    flysurfer Moderator
    20. Juni 2016 at 12:06 #20747

    Hi Rainer,

    If you deactivate the InBuild-Audiocard on Raspberry Pi Settings in Max2Play web interface…

    -> can be enabled / disabled in the first block of settings on „Raspberry Pi Settings“ tab.

    flysurfer Moderator
    20. Juni 2016 at 12:05 #20746

    @hansi9990: danke für den Tipp! Ich vermute, dass wird bei einigen Nutzern das Problem sein. Wir werden das im Wiki aufnehmen.

    Hi Luke,

    I just tried your Setup with latest Max2Play Default Image: installed Max2Play Bluetooth Addon and configurated Squeezelite to use Pulse as sound output (important). After this I used the Max2Play Touchdisplay Addon to install the 3.5″ Adafruit Display. Did a reboot and reconnected speakers with Bluetooth – playing fine without problems.

    Maybe you did something in a different way – but it should basically just work out of the box.

    All the Best,
    Stefan

    flysurfer Moderator
    20. Juni 2016 at 11:12 #20743

    Hi Rainer,

    are there any errors when starting squeezelite? If squeezelite is shown as running in the Max2Play web interface and the audio stream seems to play fine you might try „-o hw:1 -V Digital“ as your HifiBerry Card might be the second audiocard, depending on the status of the InBuild-Audiocard of the RPi. If you deactivate the InBuild-Audiocard on Raspberry Pi Settings in Max2Play web interface, the „-o hw:0 -V Digital“ command will work.

    All the Best,
    Stefan

    flysurfer Moderator
    2. Juni 2016 at 8:35 #20428

    Hi!
    You need to update to latest max2play beta on settings page and then just reinstall the skin on jivelite page. Reason: The location of the sources for the skin have changed.

    flysurfer Moderator
    26. Mai 2016 at 17:56 #20329

    Hi alex,

    according to this: https://www.hifiberry.com/guides/mixer-settings/ you should keep the playback boost off and reduce the Digital Volume slightly to about 96%.

    Anyway I would recommend to directly connect the squeezelite volume control to the hardware control of your DAC. With the standard setting you have a software volume control and a fixed hardware volume on your DAC – but this doesn’t improve audioquality.
    You can connect the volume control for squeezelite to your DAC by adding
    -o hw:0 -V Digital
    to the command line options of Squeezelite in the advanced settings of the audioplay tab.

    flysurfer Moderator
    26. Mai 2016 at 17:11 #20325

    Hallo,

    bei der Installation des kleinen Skins für die 3.2 Zoll Displays über Jivelite hatte sich in den Quellen etwas geändert. Wir haben das in der aktuellen Beta von Max2Play angepasst. Bitte führe ein Beta-Update auf der Einstellungsseite durch und installiere das Skin noch mal auf der Jivelite Seite. Danach sollte es passen.

    Viele Grüße
    Stefan

    flysurfer Moderator
    26. Mai 2016 at 16:21 #20317

    Hi,

    you may also just click install to get the latest nightly or 7.9 version on the „Squeezebox Server“ tab of the web interface. Your settings will not be changed. This will automatically load the latest available package from the download pages and install them.

    flysurfer Moderator
    26. Mai 2016 at 15:56 #20314

    Hallo Wayne23,

    danke für die genaue Schilderung des Problems. Ich habe noch ein paar Fragen:

    zu deinem Punkt

    „Fehlersuche an der Synology DS -> 1.1. Aufruf Webapplikation Logitech-Host“

    – Was genau ist damit gemeint? Auf der Synology DS sollte nur die lokale Musik in einem Ordner liegen (wird auf Max2Play als Netzwerkresource gemountet und vom Squeezebox Server auf dem Raspberry indexiert). Wenn du z.B. Webradio zum Testen hörst, kannst du die Diskstation beim Test erstmal vernachlässigen.
    – Du schreibst:

    Ich versuche nun von der Host-Webapp einen Song manuell zu starten -> nichts.

    Kannst du mal genau schauen, was passiert. Also: laufen die Sekunden wie beim normalen Abspielen oder wird das Abspielen immer wieder zurückgesetzt. Was meinst du mit „Host-Webapp“ oder „Webapp“? Du kannst den Squeezebox Server am Rechner z.B. über http://wohnzimmer:9000 aufrufen.

    Der Server sagt im Logfile, dass er den Squeezelite Player nicht mehr findet, der eigentlich auf dem gleichen Gerät wie der Server läuft. Kann es vielleicht sein, dass sich dein Router über Nacht resettet und der Raspberry eine neue IP bekommt? Du kannst das mit der IP z.B. im Reiter „LAN/Wlan“ checken und hier die IP fixieren. Dadurch, dass bei dir der Player „Wohnzimmer“ am nächsten Morgen zweimal als Abspielgerät erscheint, deutet vieles darauf hin, dass sich der Player mit einer neuen Adresse am Squeezebox-Server anmeldet, du aber weiterhin den „alten“, nicht mehr existierenden Player steuerst.

    Ein weiterer möglicher Fehler liegt in der externen USB-Soundkarte. Du könntest Squeezelite testweise ebenfalls mal über HDMI laufen lassen und schauen, ob es damit funktioniert. Für den Test am besten Kodi deaktivieren (aus Autostart entfernen). Allerdings spricht dagegen, dass du Squeezelite nicht neu startest und auch den Raspberry Pi nicht neu bootest.

    Zu deinem Anspruch: völlig richtig! So wie du es dir vorstellst sollte es auch sein 🙂 Wir bekommen das schon hin!

Viewing 30 posts - 121 through 150 (of 266 total)
1 2 3 4 5 6 7 8 9