lemting Posted January 20, 2017 Share Posted January 20, 2017 Hi Tim, I am experiencing the same thing as Franz and at least in my case, I am sure that I have the volume at 100% on my iPad playing Tidal. Is there something that I can check? Thanks. Sent from my iPad using Computer Audiophile same for me Link to comment
TimCurtis Posted January 20, 2017 Share Posted January 20, 2017 same for me Hi, I just ran a few quick tests with iPad Mini playing Youtube Music and Apple Music and no issues. I'm using HAT DAC's and AMP's. Maybe the Tidal app has its own software volume control? -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
lemting Posted January 20, 2017 Share Posted January 20, 2017 in fact i didn't use tidal moode airplay selected on audio setting on my macbook pro i just try to send music from itunes to moode : no sound Link to comment
TimCurtis Posted January 20, 2017 Share Posted January 20, 2017 in fact i didn't use tidalmoode airplay selected on audio setting on my macbook pro i just try to send music from itunes to moode : no sound Hi, Reboot and post moode log. I'll take a look. cat /var/log/moode.log Also, what audio device are u using? -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
lemting Posted January 20, 2017 Share Posted January 20, 2017 sabre ES9023 24bit 192Khz TCXO, and Raspberry 3.0 Link to comment
lemting Posted January 20, 2017 Share Posted January 20, 2017 Hi, Reboot and post moode log. I'll take a look. cat /var/log/moode.log Also, what audio device are u using? -Tim i will try to do that during this week end Link to comment
franz159 Posted January 20, 2017 Share Posted January 20, 2017 Hi Tim, I am experiencing the same thing as Franz and at least in my case, I am sure that I have the volume at 100% on my iPad playing Tidal. Is there something that I can check? Thanks. Sent from my iPad using Computer Audiophile I also double checked the volume is up to maximum on the Airplay streaming device. I tested with my MacBook Pro, iPad and iPhone 6. Are you aware of any router configuration that might be causing this? I also noticed that the zeroconf/Bonjour protocol is not working for me (so I cannot find moode.loca). However, from safari, I can discover my other raspberry running Kodi.... I'm puzzled Link to comment
TimCurtis Posted January 20, 2017 Share Posted January 20, 2017 I also double checked the volume is up to maximum on the Airplay streaming device.I tested with my MacBook Pro, iPad and iPhone 6. Are you aware of any router configuration that might be causing this? I also noticed that the zeroconf/Bonjour protocol is not working for me (so I cannot find moode.loca). However, from safari, I can discover my other raspberry running Kodi.... I'm puzzled Hi, Reboot and post moode log and i'll take a look. cat /var/log/moode.log -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
JoseL Posted January 20, 2017 Share Posted January 20, 2017 Hi, Is there anybody here using Soundirok app to control Moode? I just installed it on my iPad Air2. Using Moode's IP address the app was able to index my entire music library (2744 albums, AAIF format), however the album covers were not uploaded. Each one of my album folders contains its own cover as a folder.jpg image. I tried several iterations on the Colection URL entry without success. Please advice and TIA, JoseL Link to comment
franz159 Posted January 21, 2017 Share Posted January 21, 2017 Hi, Reboot and post moode log and i'll take a look. cat /var/log/moode.log -Tim I rebooted, but when I try to stream through AirPlay I always get the same outcome. I attached various logs, including moode.log (cut from reboot start time) here: www.francescomoretta.com/foto/varie/moode/Franz_moode_logs.tar.gz moode.log seems ok to me 20170120 194419 worker: Startup 20170120 194425 worker: Host (moode31) 20170120 194425 worker: Hdwr (Pi-3B 1GB) 20170120 194425 worker: Arch (armv7l) 20170120 194425 worker: Kver (4.4.24-sc1) 20170120 194425 worker: Ktyp (Advanced) 20170120 194425 worker: Gov (performance) 20170120 194425 worker: OS (moodeOS 1.1) 20170120 194425 worker: Rel (Moode 3.1 2016-12-05) 20170120 194425 worker: Upd (None) 20170120 194425 worker: MPD (0.19.19) 20170120 194425 worker: Session loaded 20170120 194425 worker: Debug logging (off) 20170120 194425 worker: File check... 20170120 194426 worker: File check ok 20170120 194426 worker: Auto-shuffle deactivated 20170120 194426 worker: USB sources (EFI) 20170120 194426 worker: MPD scheduler policy (rr) 20170120 194426 worker: MPD started 20170120 194427 worker: wlan0 exists 20170120 194427 worker: wlan0 trying SSID (AndreaMichelaNYC) 20170120 194427 worker: UPnP renderer started 20170120 194427 worker: HDMI port off 20170120 194427 worker: Audio (USB audio device) 20170120 194428 worker: ALSA outputs unmuted 20170120 194428 worker: ALSA mixer name (PCM) 20170120 194428 worker: MPD volume control (software) 20170120 194428 worker: MPD output 1 ALSA default (enabled) 20170120 194428 worker: MPD output 2 ALSA crossfeed (disabled) 20170120 194429 worker: Hdwr volume controller exists 20170120 194429 worker: Volume level (95) restored 20170120 194429 worker: wlan0 (192.168.1.8) 20170120 194429 worker: eth0 exists 20170120 194429 worker: eth0 address not assigned 20170120 194429 worker: Airplay receiver started 20170120 194429 worker: Airplay volume (auto) 20170120 194429 worker: NAS sources (none configured) 20170120 194429 worker: MPD consume reset to off 20170120 194429 worker: MPD crossfade (off) 20170120 194429 worker: Watchdog started 20170120 194429 worker: End startup 20170120 194429 worker: Ready Thanks for your help! Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 I rebooted, but when I try to stream through AirPlay I always get the same outcome.I attached various logs, including moode.log (cut from reboot start time) here: www.francescomoretta.com/foto/varie/moode/Franz_moode_logs.tar.gz moode.log seems ok to me 20170120 194419 worker: Startup 20170120 194425 worker: Host (moode31) 20170120 194425 worker: Hdwr (Pi-3B 1GB) 20170120 194425 worker: Arch (armv7l) 20170120 194425 worker: Kver (4.4.24-sc1) 20170120 194425 worker: Ktyp (Advanced) 20170120 194425 worker: Gov (performance) 20170120 194425 worker: OS (moodeOS 1.1) 20170120 194425 worker: Rel (Moode 3.1 2016-12-05) 20170120 194425 worker: Upd (None) 20170120 194425 worker: MPD (0.19.19) 20170120 194425 worker: Session loaded 20170120 194425 worker: Debug logging (off) 20170120 194425 worker: File check... 20170120 194426 worker: File check ok 20170120 194426 worker: Auto-shuffle deactivated 20170120 194426 worker: USB sources (EFI) 20170120 194426 worker: MPD scheduler policy (rr) 20170120 194426 worker: MPD started 20170120 194427 worker: wlan0 exists 20170120 194427 worker: wlan0 trying SSID (AndreaMichelaNYC) 20170120 194427 worker: UPnP renderer started 20170120 194427 worker: HDMI port off 20170120 194427 worker: Audio (USB audio device) 20170120 194428 worker: ALSA outputs unmuted 20170120 194428 worker: ALSA mixer name (PCM) 20170120 194428 worker: MPD volume control (software) 20170120 194428 worker: MPD output 1 ALSA default (enabled) 20170120 194428 worker: MPD output 2 ALSA crossfeed (disabled) 20170120 194429 worker: Hdwr volume controller exists 20170120 194429 worker: Volume level (95) restored 20170120 194429 worker: wlan0 (192.168.1.8) 20170120 194429 worker: eth0 exists 20170120 194429 worker: eth0 address not assigned 20170120 194429 worker: Airplay receiver started 20170120 194429 worker: Airplay volume (auto) 20170120 194429 worker: NAS sources (none configured) 20170120 194429 worker: MPD consume reset to off 20170120 194429 worker: MPD crossfade (off) 20170120 194429 worker: Watchdog started 20170120 194429 worker: End startup 20170120 194429 worker: Ready Thanks for your help! Hi,What USB DAC are u using? Try the following tests: 1) - Standard kernel - Turn UPnP renderer off - Test Airplay 2) - Set Airplay volume to 'Software' on Audio config - Test Airplay 3) - Turn Airplay receiver off in Audio config - Run the cmd below and start an Airplay stream from your client - Open a new issue on shairport-sync Git and paste the debug output so the dev can examine it. Provide details including including USB DAC model, the cmd string below, etc. https://github.com/mikebrady/shairport-sync/issues /usr/local/bin/shairport-sync -vvv -a "moode31 Airplay" -S soxr -w -B /var/www/command/spspre.sh -E /var/www/command/spspost.sh --metadata-pipename=/tmp/shairport-sync-metadata --get-coverart -- -d hw:1 -c "PCM" -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
franz159 Posted January 21, 2017 Share Posted January 21, 2017 Hi,What USB DAC are u using? Try the following tests: 1) - Standard kernel - Turn UPnP renderer off - Test Airplay 2) - Set Airplay volume to 'Software' on Audio config - Test Airplay 3) - Turn Airplay receiver off in Audio config - Run the cmd below and start an Airplay stream from your client - Open a new issue on shairport-sync Git and paste the debug output so the dev can examine it. Provide details including including USB DAC model, the cmd string below, etc. https://github.com/mikebrady/shairport-sync/issues /usr/local/bin/shairport-sync -vvv -a "moode31 Airplay" -S soxr -w -B /var/www/command/spspre.sh -E /var/www/command/spspost.sh --metadata-pipename=/tmp/shairport-sync-metadata --get-coverart -- -d hw:1 -c "PCM" -Tim Hi Tim. I'm using a Chord MoJo on USB port. Both attempts to follow your instructions (1) and (2) had a negative outcome. I then tried (3), activating AirPlay manually,. I will open an issue as instructed and I will post the output log, but I noticed an error showing up immediately in the first 2 lines of the log as you can see in the log at http://www.francescomoretta.com/foto/varie/moode/Airplay_debug_log.txt Looking for the configuration file "/usr/local/etc/shairport-sync.conf". Can't resolve the configuration file "/usr/local/etc/shairport-sync.conf I found the conf file in /etc/shairport-sync.conf and copied it in /usr/local/etc and re-tested, but the streaming is now failing with another error, as you can see in this second log at http://www.francescomoretta.com/foto/varie/moode/Airplay_debug_log_2.txt audio_alsa: Sample format not available for device "hw:1": Invalid argument avahi: avahi_unregister. Request to shut down all rtsp conversation threadsasking playing threads to stop Thanks Link to comment
franz159 Posted January 21, 2017 Share Posted January 21, 2017 After verifying that Airplay is failing for device hw:1 (Chord MoJo on USB) I wondered.... and what happens on hw:0 (raspberry onboard analog output?) ...easy to test (never done before).... - connect a Y RCA cable from the raspberyy into the other line in of the amp - in Moode configure MPD to use "On-board audio device" - retry Airplay ..and..... it works both from Mac and Ipad (using Tidal, Spotify..... whatever) Thanks Tim for providing me a way to debug. I will share my logs with shairport developers. Franz Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 After verifying that Airplay is failing for device hw:1 (Chord MoJo on USB) I wondered.... and what happens on hw:0 (raspberry onboard analog output?) ...easy to test (never done before).... - connect a Y RCA cable from the raspberyy into the other line in of the amp - in Moode configure MPD to use "On-board audio device" - retry Airplay ..and..... it works both from Mac and Ipad (using Tidal, Spotify..... whatever) Thanks Tim for providing me a way to debug. I will share my logs with shairport developers. Franz Hi, Nice bit of debugging :-) There are a few other reports of shairport-sync audio format compatibility errors with some USB dac's. MikeB is working on a new version of shairport-sync that provides a bit-depth option. It may resolve the compatibility issues. When it's released I'll include the new version in Moode. -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
bradt Posted January 21, 2017 Share Posted January 21, 2017 Tim, I'm running Moode Audio on my RPi3B. I have a HiFiBerry Digi+ card installed. Down stream the RPi is connected to my DAC via an optical cable and up stream I'm trying unsuccessfully to connect it via WiFi to my Windows Server 2012 R2 running JRiver MC22. I keep getting the following error message: "mpd-config: connection to mpd failed" I took your suggestion from earlier posts and rebooted Moode Audio and below is my log. 20170120 200712 engine-mpd: Connect 20170120 200712 engine-mpd: Session loaded 20170120 200712 openMpdSocket(): could not connect to MPD 20170120 200712 engine-mpd: Connection to mpd failed 20170120 200713 watchdog: MPD restarted (check syslog for SEGV) 20170120 200715 engine-mpd: Connect 20170120 200715 engine-mpd: Session loaded 20170120 200715 openMpdSocket(): could not connect to MPD 20170120 200715 engine-mpd: Connection to mpd failed 20170120 200718 engine-mpd: Connect 20170120 200718 engine-mpd: Session loaded 20170120 200718 openMpdSocket(): could not connect to MPD 20170120 200718 engine-mpd: Connection to mpd failed 20170120 200719 watchdog: MPD restarted (check syslog for SEGV) 20170120 200726 watchdog: MPD restarted (check syslog for SEGV) 20170120 200732 watchdog: MPD restarted (check syslog for SEGV) 20170120 200738 watchdog: MPD restarted (check syslog for SEGV) 20170120 200744 watchdog: MPD restarted (check syslog for SEGV) How do I get Moode Audio on my RPi to communicate with JRMC22 over WiFi? Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 Tim, I'm running Moode Audio on my RPi3B. I have a HiFiBerry Digi+ card installed. Down stream the RPi is connected to my DAC via an optical cable and up stream I'm trying unsuccessfully to connect it via WiFi to my Windows Server 2012 R2 running JRiver MC22. I keep getting the following error message: "mpd-config: connection to mpd failed" I took your suggestion from earlier posts and rebooted Moode Audio and below is my log. 20170120 200712 engine-mpd: Connect 20170120 200712 engine-mpd: Session loaded 20170120 200712 openMpdSocket(): could not connect to MPD 20170120 200712 engine-mpd: Connection to mpd failed 20170120 200713 watchdog: MPD restarted (check syslog for SEGV) 20170120 200715 engine-mpd: Connect 20170120 200715 engine-mpd: Session loaded 20170120 200715 openMpdSocket(): could not connect to MPD 20170120 200715 engine-mpd: Connection to mpd failed 20170120 200718 engine-mpd: Connect 20170120 200718 engine-mpd: Session loaded 20170120 200718 openMpdSocket(): could not connect to MPD 20170120 200718 engine-mpd: Connection to mpd failed 20170120 200719 watchdog: MPD restarted (check syslog for SEGV) 20170120 200726 watchdog: MPD restarted (check syslog for SEGV) 20170120 200732 watchdog: MPD restarted (check syslog for SEGV) 20170120 200738 watchdog: MPD restarted (check syslog for SEGV) 20170120 200744 watchdog: MPD restarted (check syslog for SEGV) How do I get Moode Audio on my RPi to communicate with JRMC22 over WiFi? Hi, Reboot and post moode log. cat /var/log/moode.log -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
bradt Posted January 21, 2017 Share Posted January 21, 2017 20170120 204110 engine-mpd: Connect 20170120 204110 engine-mpd: Session loaded 20170120 204110 openMpdSocket(): could not connect to MPD 20170120 204110 engine-mpd: Connection to mpd failed 20170120 204113 watchdog: MPD restarted (check syslog for SEGV) 20170120 204119 watchdog: MPD restarted (check syslog for SEGV) 20170120 204125 watchdog: MPD restarted (check syslog for SEGV) 20170120 204131 watchdog: MPD restarted (check syslog for SEGV) 20170120 204137 watchdog: MPD restarted (check syslog for SEGV) 20170120 204143 watchdog: MPD restarted (check syslog for SEGV) 20170120 204149 watchdog: MPD restarted (check syslog for SEGV) 20170120 204156 watchdog: MPD restarted (check syslog for SEGV) 20170120 204202 watchdog: MPD restarted (check syslog for SEGV) 20170120 204208 watchdog: MPD restarted (check syslog for SEGV) 20170120 204214 watchdog: MPD restarted (check syslog for SEGV) 20170120 204220 watchdog: MPD restarted (check syslog for SEGV) 20170120 204226 watchdog: MPD restarted (check syslog for SEGV) 20170120 204232 watchdog: MPD restarted (check syslog for SEGV) 20170120 204238 watchdog: MPD restarted (check syslog for SEGV) 20170120 204244 watchdog: MPD restarted (check syslog for SEGV) 20170120 204251 watchdog: MPD restarted (check syslog for SEGV) 20170120 204257 watchdog: MPD restarted (check syslog for SEGV) 20170120 204303 watchdog: MPD restarted (check syslog for SEGV) 20170120 204309 watchdog: MPD restarted (check syslog for SEGV) 20170120 204315 watchdog: MPD restarted (check syslog for SEGV) 20170120 204321 watchdog: MPD restarted (check syslog for SEGV) 20170120 204327 watchdog: MPD restarted (check syslog for SEGV) 20170120 204334 watchdog: MPD restarted (check syslog for SEGV) pi@moode:~ $ Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 20170120 204110 engine-mpd: Connect20170120 204110 engine-mpd: Session loaded 20170120 204110 openMpdSocket(): could not connect to MPD 20170120 204110 engine-mpd: Connection to mpd failed 20170120 204113 watchdog: MPD restarted (check syslog for SEGV) 20170120 204119 watchdog: MPD restarted (check syslog for SEGV) 20170120 204125 watchdog: MPD restarted (check syslog for SEGV) 20170120 204131 watchdog: MPD restarted (check syslog for SEGV) 20170120 204137 watchdog: MPD restarted (check syslog for SEGV) 20170120 204143 watchdog: MPD restarted (check syslog for SEGV) 20170120 204149 watchdog: MPD restarted (check syslog for SEGV) 20170120 204156 watchdog: MPD restarted (check syslog for SEGV) 20170120 204202 watchdog: MPD restarted (check syslog for SEGV) 20170120 204208 watchdog: MPD restarted (check syslog for SEGV) 20170120 204214 watchdog: MPD restarted (check syslog for SEGV) 20170120 204220 watchdog: MPD restarted (check syslog for SEGV) 20170120 204226 watchdog: MPD restarted (check syslog for SEGV) 20170120 204232 watchdog: MPD restarted (check syslog for SEGV) 20170120 204238 watchdog: MPD restarted (check syslog for SEGV) 20170120 204244 watchdog: MPD restarted (check syslog for SEGV) 20170120 204251 watchdog: MPD restarted (check syslog for SEGV) 20170120 204257 watchdog: MPD restarted (check syslog for SEGV) 20170120 204303 watchdog: MPD restarted (check syslog for SEGV) 20170120 204309 watchdog: MPD restarted (check syslog for SEGV) 20170120 204315 watchdog: MPD restarted (check syslog for SEGV) 20170120 204321 watchdog: MPD restarted (check syslog for SEGV) 20170120 204327 watchdog: MPD restarted (check syslog for SEGV) 20170120 204334 watchdog: MPD restarted (check syslog for SEGV) pi@moode:~ $ Hi, moode log should look something like below after reboot. I can't work with what you posted. -Tim pi@rp3:~ $ cat /var/log/moode.log 20170120 211622 worker: Startup 20170120 211625 worker: Host (rp3) 20170120 211625 worker: Hdwr (Pi-3B 1GB) 20170120 211625 worker: Arch (armv7l) 20170120 211625 worker: Kver (4.4.39-moode1+) 20170120 211625 worker: Ktyp (Advanced) 20170120 211625 worker: Gov (performance) 20170120 211625 worker: OS (moodeOS 1.1) 20170120 211625 worker: Rel (Moode 3.1 2016-12-05) 20170120 211625 worker: Upd (2017-01-11-TEST) 20170120 211625 worker: MPD (0.20.2) 20170120 211625 worker: Session loaded 20170120 211625 worker: Debug logging (off) 20170120 211625 worker: File check... 20170120 211626 worker: File check ok 20170120 211626 worker: Auto-shuffle deactivated 20170120 211626 worker: USB sources (none attached) 20170120 211626 worker: MPD scheduler policy (rr) 20170120 211626 worker: MPD started 20170120 211626 worker: wlan0 exists 20170120 211626 worker: wlan0 trying SSID (AirnetN2) 20170120 211626 worker: Rotary encoder driver loaded 20170120 211626 worker: HDMI port off 20170120 211626 worker: Audio (I2S audio device) 20170120 211626 worker: Audio (Mamboberry LS DAC+) 20170120 211627 worker: ALSA outputs unmuted 20170120 211627 worker: ALSA mixer name (Digital) 20170120 211627 worker: MPD volume control (software) 20170120 211627 worker: MPD output 1 ALSA default (enabled) 20170120 211627 worker: MPD output 2 ALSA crossfeed (disabled) 20170120 211627 worker: MPD output 3 ALSA equalizer (disabled) 20170120 211627 worker: Hdwr volume controller not detected 20170120 211627 worker: Volume level (15) restored 20170120 211627 worker: wlan0 wait 1 for address 20170120 211630 worker: wlan0 (192.168.1.211) 20170120 211630 worker: eth0 exists 20170120 211630 worker: eth0 address not assigned 20170120 211630 worker: Airplay receiver started 20170120 211630 worker: Airplay volume (auto) 20170120 211631 worker: NAS sources (mountall initiated) 20170120 211631 worker: MPD consume reset to off 20170120 211631 worker: MPD crossfade (off) 20170120 211631 worker: Watchdog started 20170120 211631 worker: End startup 20170120 211631 worker: Readypi@rp3:~ $ Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
bradt Posted January 21, 2017 Share Posted January 21, 2017 I can't figure out how to produce a log that looks anything like yours. I cleared the log and tried again and I get the same thing. I'm logged into pi@moode:~ whereas you appear to be logged into pi@rp3:~. Is that the issue? Any ideas? Thanks. Brad Link to comment
franz159 Posted January 21, 2017 Share Posted January 21, 2017 Hi, Nice bit of debugging :-) There are a few other reports of shairport-sync audio format compatibility errors with some USB dac's. MikeB is working on a new version of shairport-sync that provides a bit-depth option. It may resolve the compatibility issues. When it's released I'll include the new version in Moode. -Tim shairport-sync issue with Chord MoJo connected on USB port reported: https://github.com/mikebrady/shairport-sync/issues/463 Link to comment
lemting Posted January 21, 2017 Share Posted January 21, 2017 Hi, Reboot and post moode log. I'll take a look. cat /var/log/moode.log Also, what audio device are u using? -Tim pi@moode:~ $ cat /var/log/moode.log 20170117 195520 worker: Startup 20170117 195522 worker: Host (moode) 20170117 195522 worker: Hdwr (Pi-3B 1GB) 20170117 195522 worker: Arch (armv7l) 20170117 195522 worker: Kver (4.4.24-sc1) 20170117 195522 worker: Ktyp (Advanced) 20170117 195522 worker: Gov (ondemand) 20170117 195522 worker: OS (moodeOS 1.1) 20170117 195522 worker: Rel (Moode 3.1 2016-12-05) 20170117 195522 worker: Upd (None) 20170117 195522 worker: MPD (0.19.19) 20170117 195522 worker: Session loaded 20170117 195522 worker: Debug logging (off) 20170117 195522 worker: File check... 20170117 195523 worker: File check ok 20170117 195525 worker: Auto-shuffle deactivated 20170117 195525 worker: USB sources (none attached) 20170117 195525 worker: MPD scheduler policy (time-share) 20170117 195525 worker: MPD started 20170117 195525 worker: wlan0 does not exist (off) 20170117 195525 worker: HDMI port off 20170117 195525 worker: Audio (I2S audio device) 20170117 195525 worker: Audio (Audiophonics ES9023 DAC) 20170117 195525 worker: ALSA outputs unmuted 20170117 195525 worker: ALSA mixer name (Digital) 20170117 195525 worker: MPD volume control (disabled) 20170117 195526 worker: MPD output 1 ALSA default (enabled) 20170117 195526 worker: MPD output 2 ALSA crossfeed (disabled) 20170117 195526 worker: Hdwr volume controller not detected 20170121 104024 worker: Volume level (0) restored 20170121 104024 worker: wlan0 address not assigned 20170121 104024 worker: eth0 exists 20170121 104024 worker: eth0 (192.168.1.33) 20170121 104024 worker: Airplay receiver started 20170121 104024 worker: Airplay volume (auto) 20170121 104026 worker: NAS sources (mountall initiated) 20170121 104026 worker: MPD consume reset to off 20170121 104026 worker: MPD crossfade (off) 20170121 104026 worker: Watchdog started 20170121 104026 worker: End startup 20170121 104026 worker: Ready Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 pi@moode:~ $ cat /var/log/moode.log20170117 195520 worker: Startup 20170117 195522 worker: Host (moode) 20170117 195522 worker: Hdwr (Pi-3B 1GB) 20170117 195522 worker: Arch (armv7l) 20170117 195522 worker: Kver (4.4.24-sc1) 20170117 195522 worker: Ktyp (Advanced) 20170117 195522 worker: Gov (ondemand) 20170117 195522 worker: OS (moodeOS 1.1) 20170117 195522 worker: Rel (Moode 3.1 2016-12-05) 20170117 195522 worker: Upd (None) 20170117 195522 worker: MPD (0.19.19) 20170117 195522 worker: Session loaded 20170117 195522 worker: Debug logging (off) 20170117 195522 worker: File check... 20170117 195523 worker: File check ok 20170117 195525 worker: Auto-shuffle deactivated 20170117 195525 worker: USB sources (none attached) 20170117 195525 worker: MPD scheduler policy (time-share) 20170117 195525 worker: MPD started 20170117 195525 worker: wlan0 does not exist (off) 20170117 195525 worker: HDMI port off 20170117 195525 worker: Audio (I2S audio device) 20170117 195525 worker: Audio (Audiophonics ES9023 DAC) 20170117 195525 worker: ALSA outputs unmuted 20170117 195525 worker: ALSA mixer name (Digital) 20170117 195525 worker: MPD volume control (disabled) 20170117 195526 worker: MPD output 1 ALSA default (enabled) 20170117 195526 worker: MPD output 2 ALSA crossfeed (disabled) 20170117 195526 worker: Hdwr volume controller not detected 20170121 104024 worker: Volume level (0) restored 20170121 104024 worker: wlan0 address not assigned 20170121 104024 worker: eth0 exists 20170121 104024 worker: eth0 (192.168.1.33) 20170121 104024 worker: Airplay receiver started 20170121 104024 worker: Airplay volume (auto) 20170121 104026 worker: NAS sources (mountall initiated) 20170121 104026 worker: MPD consume reset to off 20170121 104026 worker: MPD crossfade (off) 20170121 104026 worker: Watchdog started 20170121 104026 worker: End startup 20170121 104026 worker: Ready Hi, The log looks ok. I ran a few quick tests with a Mamboberry LS which uses ES9023 chip similar to the Audiophionics device that is listed in the log. The LS is connected to an audio system that has its own volume control. Client is iTunes on a Mac. No issues using Airplay. Try the following tests: 1) - Standard kernel - Reboot - Test Airplay 2) - Turn Airplay receiver off in Audio config - Run the cmd below and start an Airplay stream from your client - Open a new issue on shairport-sync Git and paste the debug output so the dev can examine it. Provide details including I2S DAC model, the cmd string below, etc. https://github.com/mikebrady/shairport-sync/issues /usr/local/bin/shairport-sync -vvv -a "Moode Airplay" -S soxr -w -B /var/www/command/spspre.sh -E /var/www/command/spspost.sh --metadata-pipename=/tmp/shairport-sync-metadata --get-coverart -- -d hw:0 -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
jonez Posted January 21, 2017 Share Posted January 21, 2017 Hi Tim, i have an issue with booting moode off an 8GB SD card. The card reads just fine when plugged into my Macbook's card reader and writing the image works without issues. I use Etcher to write the image, which even verifies the card after writing the image. However, moode won't boot reliably off this card. After plugging in the card last time, it first didn't work, then i fumbled a bit with the card and noticed it wasn't positioned perfectly in the SD slot. After that, moode booted fine on power-on, but next reboot it failed again. And I didn't touch the card in between. I therefore temporarily switched to another spare 2GB card, which works perfectly fine. However, the newest version of moode won't fit anymore onto this smaller card. So I'm back struggling with the 8 GB card. Before I invest money in getting another card, I wonder if there's any way I can diagnose the issue without an external monitor? I simply don't have any external monitor available. Will moode write any kind of log file/... to the card during boot? If it helps: The pi (Rev 1B) is connected via Ethernet. Thanks, Jonas Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 Hi Tim, i have an issue with booting moode off an 8GB SD card. The card reads just fine when plugged into my Macbook's card reader and writing the image works without issues. I use Etcher to write the image, which even verifies the card after writing the image. However, moode won't boot reliably off this card. After plugging in the card last time, it first didn't work, then i fumbled a bit with the card and noticed it wasn't positioned perfectly in the SD slot. After that, moode booted fine on power-on, but next reboot it failed again. And I didn't touch the card in between. I therefore temporarily switched to another spare 2GB card, which works perfectly fine. However, the newest version of moode won't fit anymore onto this smaller card. So I'm back struggling with the 8 GB card. Before I invest money in getting another card, I wonder if there's any way I can diagnose the issue without an external monitor? I simply don't have any external monitor available. Will moode write any kind of log file/... to the card during boot? If it helps: The pi (Rev 1B) is connected via Ethernet. Thanks, Jonas Hi Jonas, The symptom "moode won't boot reliably off this card" suggests something external to Moode software for example bad sd card, power supply etc. I'd recommend swapping out the sd card for a known good one. I use Sandisk Ultra SD cards and have never had a bad card. https://www.amazon.com/SanDisk-Ultra-Micro-Adapter-SDSQUNC-016G-GN6MA/dp/B010Q57SEE/ref=sr_1_2?s=pc&ie=UTF8&qid=1485015168&sr=1-2&keywords=sandisk+ultra+class+10+micro+sd -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
jonez Posted January 21, 2017 Share Posted January 21, 2017 Hi Jonas, The symptom "moode won't boot reliably off this card" suggests something external to Moode software for example bad sd card, power supply etc. I'd recommend swapping out the sd card for a known good one. I use Sandisk Ultra SD cards and have never had a bad card. https://www.amazon.com/SanDisk-Ultra-Micro-Adapter-SDSQUNC-016G-GN6MA/dp/B010Q57SEE/ref=sr_1_2?s=pc&ie=UTF8&qid=1485015168&sr=1-2&keywords=sandisk+ultra+class+10+micro+sd -Tim Hi Tim, thanks for the quick reply! Sounds like I shouldn't bother fixing the card/booting off that card. For the record: the card is a Transcend Class 10. Will checkout the Sandisk one. I also have an Extreme III from Sandisk in my camera, which works like a charm. Thanks much! Jonas Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now