flysurfer

Forum Replies Created

Viewing 26 posts - 241 through 266 (of 266 total)
  • 22. September 2015 at 16:10 #15771

    Hi Alex,

    thanks a lot for your detailed report! I finally found the time to test the things you reported. Expanding the SD-card only works without having plugged any other USB-Sticks, SD-Cards or other filesystems as Raymond wrote.

    2. The Squeezeboxserver in 7.8 is not working because of a perl update to version 5.20. The nightly builds do have CPAN-libraries for perl 5.20 and the default 7.8 is missing this one. I built these for earlier perl versions (e.g. 5.18) and added them to Max2Play – but as 7.9 works I didn’t even recognize this is missing.

    3. The mount-options and fixed mount points for your usb hard drive do not work as expected because of a missing newline in /etc/fstab (the „##USERMOUNT“ must be on a new line, but it is not… this is a bug). You may fix this with sed "s/1##USERMOUNT/1\n##USERMOUNT/" /etc/fstab. I also added a patch to the Max2Play-Update-Script to fix this.

    4. Difficult to tell why the hardkernel USB-SPDIF is not working as expected. Maybe it is due to some access rights. You may try: stop and remove Shairport and kodi from Autostart or give Shairport and kodi another soundcard. Start squeezelite from commandline as user „odroid“ like the script is doing it. You may see which devices are using the sound output as root in a console with /bin/fuser -v /dev/snd/* 2>&1

    5. Kodi – never experienced such issues – but maybe it is connected with the hardkernel USB-SPDIF stick. Sometimes kodi „hangs“ if it has no access to the soundcard.

    6. VNC: The vnc-server tried to open a new display as it couldn’t see the existing one. There was just a small bug in the init script (/etc/init.d/x11vnc) that is fixed now. You just need to get the latest Beta and uninstall -> reinstall the plugin.

    To get the BETA-Versions and the updates I just did, you need to do a „Update to latest Beta“ on the Settings page. This is only available if you have the premium license. The changes will also be in the next release (probably within 2 weeks).

    Hope I could help you a little with your questions! I will create a new Image for the XU4 (with all fixes), that comes with the latest Max2Play-version soon.

    Cheers,
    Stefan

    17. September 2015 at 11:48 #15722

    Super, dass es jetzt läuft!

    Es wichtig in den FritzBox Benutzereinstellungen den Punkt „Anmeldung bei Zugriff aus dem Heimnetz“ auf die entsprechende Option zu setzen, die man nutzen möchte. Hier sollte „Anmeldung mit FRITZ!Box-Benutzernamen und Kennwort“ gewählt werden, wenn das Login mit Benutzername und Passwort erfolgen soll. Alternativ (bei Login nur mit Passwort) den Punkt „Anmeldung mit dem FRITZ!Box-Kennwort“ nutzen und im Max2Play Addon den Benutzernamen frei lassen.

    28. August 2015 at 10:54 #15481

    Hi Aleka,

    good to hear you sorted it out!

    Locking at your posted Infos and Log Files the kernel and modules for the Wolfson-Card are loaded correctly. There are some people using this setup and therefor we are quite sure that it works 😉

    The names of the different PI versions like B/B+/2/2B and the different supported soundcards do not make it easy to find the right setup.

    If you are looking for a DAC – have a visit at our shop. The HiFiBerry DAC+ are supported with Pi B+ and Pi 2.

    27. August 2015 at 18:57 #15464

    Hi Aleka,

    did you encounter any problems during installation of the Wolfson Card (e.g. run out of memory on SD-Card)? I just tested with a RPi B+ (latest Max2Play-Version) and installed the Wolfson Card with the Raspberry PI Addon. After a reboot the required modules are showing up. We do not have a real card for testing, but several people got it running with this setting.

    On the bottom of the Raspberry Pi Settings Addon you have a „Debug“ output. At the bottom of this output you should see this lines if the installation went ok:

    
    dtoverlay=rpi-cirrus-wm5102-overlay
    kernel=vmlinuz-3.18.9cludlmmapfll
    

    If you could post the output of „lsmod“ (login via console and SSH as user „root“ password „max2play“), we might help you better. Which Max2Play SD-Card Image did you use? Did you update Max2Play to the latest version and expanded the filesystem of you SD-Card?

    Stefan

    23. August 2015 at 18:26 #15444

    Hi kfth,

    you need to unplug all external storages like USB-drivs and run the filesystem expansion again. The message you posted only occurs, if other filesystems then the normal SD-Card (or EMMC-Card) are found.

    Stefan

    23. August 2015 at 18:23 #15443

    Hi Stuart,

    with VNC you can only attach to a activ x-server session (desktop). On the Raspberry PI this session gets created on start of VNC, if it is not running yet. Kodi is running standalone (without desktop) on the PI to save some resources (faster, less memory). On the ODROID U3 or XU4 you can see Kodi through VNC as it is running on the normal desktop.

    Stefan

    21. August 2015 at 11:23 #15439

    Hallo Roger,

    danke für den Hinweis! Wir haben den Fehler (ist scheinbar Routerabhängig und ist uns beim Testen nicht aufgefallen) in der aktuellen Version bereits behoben (2.20). Beim Fixieren der IP-Adresse wird jetzt auch ein Nameservereintrag zur Auflösung von IP-Adressen gesetzt.

    Viele Grüße
    Stefan

    20. August 2015 at 11:33 #15436

    Hi Sean,

    I just had a look at the instructions from the waveshare website and I just found already build kernels and no sources and instructions on how they built the kernel. You may find kernel sources for the wolfson audio card on Github. To get both, the Wolfson Card and the display to work together you need to compile your own kernel based on the sources from wolfson and waveshare. You need to get the changes by waveshare, that they applied to the original Raspbian Kernel and you may start with the already patched kernel sources from wolfson. Compiling on a PI 2 takes some time – but you may crosscompile it on a VM-Ware with the right settings.

    Well – this is really not too easy, if you never done this before… sorry that we can’t really help you with this.

    Cheers,
    Stefan

    18. August 2015 at 18:28 #15418

    Hi Ferenc,

    good news: I added the setting for the Amp+ (IQAudio) with the unmute code. It is already available in the Beta of Max2Play and will be in the Main Version this week.

    As I do not have a card for testing I cannot say, if the equalizer works correctly.

    18. August 2015 at 15:29 #15404

    Hi Ferenc,

    I can add support for this card, if it is not working with the current DAC+ setting. There has to be at least an unmute call for the AMP+, as it seems to be muted on when the device boots up. I will ask Gordon from IQAudio about the settings and integrate it into the next release.

    Cheers,
    Stefan

    16. August 2015 at 12:17 #15381

    Hi,

    if using shairtunes as plugin for the squeezebox server, you can currently not send the output to synchronized squeezeplayers.

    But if your focus is using airplay, you may use shairport (standalone player on tab „Audioplayer“ in Web interface of Max2Play). Depending on which device (Raspberry PI / ODROID) and soundcard (e.g. HiFiBerry) you use, this shairport player may run at the same time as squeezelite does. With this setup (shairport activated on all devices running Max2Play) you can select multiple airplay devices from your idevice and let them play together (synchronize the players with your idevice like itunes on Mac).

    Following setups work with Squeezelite and Shairport running at the same time:
    – Raspberry PI without external soundcard (using HDMI or headphone jack)
    – ODROID U3/XU3/XU4/C1
    – Most USB-DACs that are connected to the ODROID / Raspberry PI

    Not working in this modus are soundcards like HiFiBerry and others connected to the GPIO Pins on the Rasbperry.

    Cheers,
    Stefan

    11. August 2015 at 12:09 #15345

    Hi René,

    there is currently no easy update method for Kodi on the Raspberry PI. I don’t think, that the packages provided via APT-GET will work as expected.

    Do you have some special features, that you are looking for?

    11. August 2015 at 12:06 #15344

    Hi,

    it mainly depends on what exactly happens once your BT-speakers are shut down. As I understand from your post Squeezelite is still running after BT-speakers are not available anymore. The scripts you posted seems to check for the BT-connection and either starts or stops the squeezelite process. We have a cronjob in the Max2Play-Image that checks for a running Squeezelite and starts it automatically if „Autostart“ is enabled. If the BT-Connection is not available this should normally fail (you should check this). So simplest thing to do would be a script, that just stops squeezelite once the BT-connection is not available anymore and start this script with the /etc/rc.local at startup.

    I took the hcitool-part from the other script. Didn’t test it, as I don’t have a Bluetooth Speaker.

    #!/bin/bash
    while (sleep 5)
    do
      running_squeezelite=$(ps -Al | grep squeezelite | wc -l)
      if [ "0" -lt "$running_squeezelite" ]; then
        connected=$(hcitool con) > /dev/null
        if [[ $connected =~ .*${address}.* ]] ; then
           #everything is fine
        else
           /etc/init.d/squeezelite stop
        fi
      fi
    done
    
    7. August 2015 at 11:20 #15308

    Hi,

    thanks for your positive feedback! As you have a quite complex setup with 2 players (squeezelite and shairport) on each device, it gets difficult to auto-mute one player as soon as the other player plays something. On some soundcards it is even not possible to give two players access to the soundinterface at the same time (even if they are not playing anything).
    The only thing that might work (besides stopping music manually), would be to write a script that checks if the current squeezelite instance is playing something (make a http-Request to the squeezebox server for the desired squeezelite player or watch the CPU Usage of squeezelite) and watch the CPU-Usage of the task shairport and decide what to do. Both checks should be within a small C-programm (checking every 5 seconds) that starts a shell-script, that stops either shairplay or squeezelite (depending on a config file) on the device and restarts it later on. If you are using this method you must remove the cronjob (running under user „pi“) that automatically starts the audioplayers.

    Well – it sounds quite complicated and it is 😉

    5. August 2015 at 11:30 #15279

    As some features in the webinterface rely on the SYSTEM_USER setting, there might be some other problems too (audioplayer soundcard setting is set to a wrong value with the reset). A reinstall might be the best solution.

    5. August 2015 at 11:28 #15278

    Glad you sorted it out!

    Make sure to set „user“ and „password“ correctly to fit your settings on the NAS. The default values are just to show that there should be set something. Also delete the settings that do not work from the list – otherwise you will always get error messages, even if one of the mounts is working.

    Cheers,
    Stefan

    4. August 2015 at 9:42 #15272

    OK – that „Reset“ seems be the reason and this is quite likely a bug! Thanks for investigating on this. I will fix this with the next update of Max2Play.

    3. August 2015 at 16:01 #15262

    Hi Tomasz,

    first: thanks a lot for your positive feedback!! Really appreciated!

    The scripts that come with Max2Play have a default setting for the odroid (if no USER is set) as this was the first device we supported. This default setting gets overrun at runtime by variables in the /opt/max2play/*.conf. This changes the user from odroid to „pi“ in the scripts you mentioned. This line does the „magic“:
    USER=$(grep -a "SYSTEM_USER" /opt/max2play/audioplayer.conf | sed -n -e 's/^[A-Z_]*\=//p')

    If this does not happen correctly, it is really strange… you may have a look at the file „/opt/max2play/audioplayer.conf“ and see why the variable SYSTEM_USER is not set.

    • This reply was modified 8 years, 10 months ago by flysurfer.
    3. August 2015 at 15:48 #15260

    Hi T,

    you may post your new Topic inside the existing „Main-Topics“ like the subforum of Questions related to Max2Play on Raspberry PI. It is not possible to post a new Topic on Level 1. If you have suggestions on new Level-1 Topics, please contact us and we might add it.

    30. Juli 2015 at 15:23 #15240

    Hi Soko,

    it is possible to connect your doorbell to some audiooutput with Max2Play. You basically need to write your own bash-script to play a MP3. Following things are needed:

    1. WiringPI library and a small script written in C that compiles on the PI to capture the event of the GPIO-PIN. This script should execute a Shell Script.

    This is an example of a C-Script, that captures a button event on the PI:

    //build with gcc -I. -o button button.c -lwiringPi
    #include <stdio.h>
    #include <string.h>
    #include <errno.h>
    #include <stdlib.h>
    #include <wiringPi.h>
    
    typedef enum { false, true } bool;
    static bool globalActive = false;
    static int globalCounter = 0;
    
    void myInterrupt(void) {
      int pin = digitalRead(2);
      if(pin == LOW && globalActive == false){
        globalActive = true;
        printf ("Button pressed\n");
      }else if(pin == HIGH && globalActive == true){
        printf ("Button Released\n");    
        int sysreturn = 0;    
        sysreturn = system("/opt/max2play/scriptyouwant.sh");    
        printf("System: %d", sysreturn);
        globalActive = false;
      }
    }
    
    int main (void)
    {
      wiringPiSetup () ;
    
      wiringPiISR (2, INT_EDGE_BOTH, &myInterrupt) ;
    
      for (;;) {
        sleep(1000);
      }
      return 0 ;
    }

    2. Shell-Script, that plays a MP3 with either mpc (command line MPD-Tool) or tells the squeezeboxserver (may be on another device in your network) via http-Get request to play a mp3 on one of your audioplayers (or on all). If you go big, use a squeezebox server and make use the command-line arguments like this in your Shell-Script (you may find the documentation for this command line interface in the squeezebox server interface after installation):

    
    # Example CLI-Call to Play current song via http-GET Request to Squeezebox Server on Max2Play 
    wget -q -O - "http://max2play:9000/status.html?p0=play&p1=preset_1.single&player=[MAC-Address URL-encoded]"
    

    Cheers,
    Stefan

    27. Juli 2015 at 16:08 #15219

    Ok – yeah, you need to change the soundcard output on the audioplayer tab, if you want to use the equalizer. By default the soundcard setting points directly to the hifiberry amp, if you choose this setting initially. I will think about how to explain that setting a little further in the equalizer menu. Thanks for your feedback on this!

    27. Juli 2015 at 15:51 #15217

    Hi Atinkler,

    did you change the soundcard setting for squeezelite to „plugequal – Equalizer for plughw:0,0“ in advanced settings?

    Just tested this with the HiFiBerry Amp and it is working for me.

    Cheers,
    Stefan

    27. Juli 2015 at 15:11 #15215

    Thanks for your post! We will change this setting in our next release!

    27. Juli 2015 at 14:41 #15214

    Hi Atinkler,

    the current equalizer on the audioplayer tab is only working with squeezelite. As the MPD-Player needs the user „mpd“ and not the system user „pi“ to control the equalizer, we have to add the equalizer feature to the „Music Player MPD“ tab with slightly different settings to get it working. Besides that, you need to set the Sound Device in the soundcard settings of the MPD player to „plug:plugequal“. If you do not want to wait until our next release you may run this on the console as root to change the equalizer settings:
    „usermod -aG audio mpd“
    „sudo -H -u mpd alsamixer -D equal“

    Cheers,
    Stefan

    3. Juli 2015 at 9:31 #15101

    Hi timmo11,

    if the complete path of the executable file is „/root/rescan“, than it should work by pasting this into the „Start my own Script“.

    You might try to debug, if something is not working as expected: add some logging to the command in the webinterface to see what the command-line output is. In your case you might try this for the „Start my own Script“:

    /root/rescan 2>&1 > /tmp/rescan-output

    After pushing the button, there should be a file with the output of your script – to open it use „cat /tmp/rescan-output“

    • This reply was modified 8 years, 11 months ago by flysurfer.
    2. Juli 2015 at 11:37 #15090

    Hi Adrian,

    the Debug-Information seems OK. What you should try:

    If your Sharename is „Data“ with upper case letters then use //192.168.0.1/Data for the Path.

    Additionally you might try to add uid=1000 to the options that it looks like user=myusername,password=mypassword,sec=ntlm,uid=1000,iocharset=utf8

    Cheers,
    Stefan

Viewing 26 posts - 241 through 266 (of 266 total)