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 I hope so... Mike commented on the issue blog that it looks like the Chord MoJo does not offer CD format, i.e. 44,100 samples per second, 16 bit signed integer little-endian interleaved stereo, which Shairport Sync requires. In terms of sample frequency I should be good, since the Mojo is supposed to play up to 768KHz PCM and DSD256 in DoP format... What I'm not sure is the bit number, will MoJo accept a 16 bit input stream? In fact, examining for example Audio Info in Moode, even when playing a source file decoded to 16 bit, 44.1 kHz Stereo , I see that the output stream format is always 32 bit, 44.1 kHz, Stereo. Similarly, on my Mac Audio Midi Setup, I see the MoJo as 2 channels, 32 bit Apologies for the maybe stupid question, but could this be the issue? Airplay streaming at 16 bit and MoJo supporting only a 32 bit stream? Link to comment
franz159 Posted January 21, 2017 Share Posted January 21, 2017 I hope so... Mike commented on the issue blog that it looks like the Chord MoJo does not offer CD format, i.e. 44,100 samples per second, 16 bit signed integer little-endian interleaved stereo, which Shairport Sync requires. In terms of sample frequency I should be good, since the Mojo is supposed to play up to 768KHz PCM and DSD256 in DoP format... What I'm not sure is the bit number, will MoJo accept a 16 bit input stream? In fact, examining for example Audio Info in Moode, even when playing a source file decoded to 16 bit, 44.1 kHz Stereo , I see that the output stream format is always 32 bit, 44.1 kHz, Stereo. Similarly, on my Mac Audio Midi Setup, I see the MoJo as 2 channels, 32 bit Apologies for the maybe stupid question, but could this be the issue? Airplay streaming at 16 bit and MoJo supporting only a 32 bit stream? ******************* UPDATE*********************************** After following up with Mike Brady, I confirm that the issue was related to 16 vs 32 bit depth of the stream. Therefore I compiled the current "development branch" of shairport-sync, following the instructions for Jessie in the README https://github.com/mikebrady/shairport-sync/blob/master/README.md and I'm now using version 3.0 pi@moode31ny:/usr/local/bin $ ./shairport-sync -V 3.0d16-OpenSSL-Avahi-ALSA-soxr-metadata-sysconfdir:/etc I also had to add an additional parameter (output_format) in the alsa section of /etc/shairport-sync.conf file as follows alsa ={ output_format = "S32"; // can be "U8", "S8", "S16", "S24", "S24_3LE", "S24_3BE" or "S32", but the device must have the capability. Except where stated using (*LE or *BE), endianness matches that of the processor. // output_device = "default"; // the name of the alsa output device. Use "alsamixer" or "aplay" to find out the names of devices, mixers, etc. // mixer_control_name = "PCM"; // the name of the mixer to use to adjust output volume. If not specified, volume in adjusted in software. // mixer_device = "default"; // the mixer_device default is whatever the output_device is. Normally you wouldn't have to use this. // audio_backend_latency_offset = 0; // Set this offset to compensate for a fixed delay in the audio back end. E.g. if the output device delays by 100 ms, set this to -4410. // audio_backend_buffer_desired_length = 6615; // If set too small, buffer underflow occurs on low-powered machines. Too long and the response times with software mixer become annoying. }; ....the entire comment thread with Mike Brady is here and YES, I'm actually streaming through Airplay now! Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 ******************* UPDATE*********************************** After following up with Mike Brady, I confirm that the issue was related to 16 vs 32 bit depth of the stream. Therefore I compiled the current "development branch" of shairport-sync, following the instructions for Jessie in the README https://github.com/mikebrady/shairport-sync/blob/master/README.md and I'm now using version 3.0 pi@moode31ny:/usr/local/bin $ ./shairport-sync -V 3.0d16-OpenSSL-Avahi-ALSA-soxr-metadata-sysconfdir:/etc I also had to add an additional parameter (output_format) in the alsa section of /etc/shairport-sync.conf file as follows alsa ={ output_format = "S32"; // can be "U8", "S8", "S16", "S24", "S24_3LE", "S24_3BE" or "S32", but the device must have the capability. Except where stated using (*LE or *BE), endianness matches that of the processor. // output_device = "default"; // the name of the alsa output device. Use "alsamixer" or "aplay" to find out the names of devices, mixers, etc. // mixer_control_name = "PCM"; // the name of the mixer to use to adjust output volume. If not specified, volume in adjusted in software. // mixer_device = "default"; // the mixer_device default is whatever the output_device is. Normally you wouldn't have to use this. // audio_backend_latency_offset = 0; // Set this offset to compensate for a fixed delay in the audio back end. E.g. if the output device delays by 100 ms, set this to -4410. // audio_backend_buffer_desired_length = 6615; // If set too small, buffer underflow occurs on low-powered machines. Too long and the response times with software mixer become annoying. }; ....the entire comment thread with Mike Brady is here and YES, I'm actually streaming through Airplay now! Hi, Glad that its working :-) -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 unplugged my RPi, plugged it back in again and captured the following log: login as: pi [email protected]'s password: Linux 4.4.30-v7+ J-Lite Core, armv7l Architecture __ ____ ____ __ _ ___ ___ ___/ /__ / __ \/ __/ / ' \/ _ \/ _ \/ _ / -_) /_/ /\ \ /_/_/_/\___/\___/\_,_/\__/\____/___/ moodeOS Version 1.1 dual-kernel © 2016 Tim Curtis moodeOS is based on Debian GNU/Linux and is custom factored for Moode Audio Player. moodeOS and Moode Audio Player are provided for free by the copyright holders and contributors and come with no expressed or implied warranties or any other guarantees. Last login: Fri Jan 20 20:57:58 2017 from bradssurfacepro4.web-pass.com pi@moode:~ $ cat var/log/moode.log cat: var/log/moode.log: No such file or directory pi@moode:~ $ cat /var/log/moode.log 20170121 120733 worker: Startup 20170121 120735 worker: Host (moode) 20170121 120735 worker: Hdwr (Pi-3B 1GB) 20170121 120735 worker: Arch (armv7l) 20170121 120735 worker: Kver (4.4.30-v7+) 20170121 120735 worker: Ktyp (Standard) 20170121 120735 worker: Gov (ondemand) 20170121 120735 worker: OS (moodeOS 1.1) 20170121 120735 worker: Rel (Moode 3.1 2016-12-05) 20170121 120735 worker: Upd (None) 20170121 120735 worker: MPD () 20170121 120735 worker: Session loaded 20170121 120735 worker: Debug logging (on) 20170121 120735 worker: File check... 20170121 120735 worker: File check ok 20170121 120736 worker: Auto-shuffle deactivated 20170121 120736 worker: USB sources (none attached) 20170121 120736 worker: MPD scheduler policy (time-share) 20170121 120736 worker: MPD started 20170121 120736 worker: wlan0 exists 20170121 120736 worker: wlan0 trying SSID (BradsNetN) 20170121 120736 worker: UPnP renderer started 20170121 120736 worker: HDMI port off 20170121 120736 worker: Audio (I2S audio device) 20170121 120736 worker: Audio (HIFI Digi+) 20170121 120736 worker: ALSA outputs unmuted 20170121 120736 worker: ALSA mixer name (Digital) 20170121 120736 worker: MPD volume control (software) 20170121 120736 openMpdSocket(): could not connect to MPD 20170121 120736 readMpdResponse() error: fgets() fail due to socket being timed out or PHP/MPD connection failure 20170121 120736 readMpdResponse() $resp: () 20170121 120736 worker: 20170121 120736 worker: 20170121 120737 worker: Hdwr volume controller not detected 20170121 120737 worker: Volume level (0) restored 20170121 120737 worker: wlan0 (192.168.1.143) 20170121 120737 worker: eth0 exists 20170121 120737 worker: eth0 address not assigned 20170121 120737 worker: NAS sources (none configured) 20170121 120737 readMpdResponse() error: fgets() fail due to socket being timed out or PHP/MPD connection failure 20170121 120737 readMpdResponse() $resp: () 20170121 120737 worker: MPD consume reset to off 20170121 120737 worker: MPD crossfade (off) 20170121 120737 readMpdResponse() error: fgets() fail due to socket being timed out or PHP/MPD connection failure 20170121 120737 readMpdResponse() $resp: () 20170121 120737 worker: Watchdog started 20170121 120737 worker: End startup 20170121 120737 worker: Ready 20170121 120737 watchdog: MPD restarted (check syslog for SEGV) 20170121 120743 watchdog: MPD restarted (check syslog for SEGV) 20170121 120749 watchdog: MPD restarted (check syslog for SEGV) 20170121 120755 watchdog: MPD restarted (check syslog for SEGV) 20170121 120802 watchdog: MPD restarted (check syslog for SEGV) 20170121 120808 watchdog: MPD restarted (check syslog for SEGV) 20170121 120817 watchdog: MPD restarted (check syslog for SEGV) 20170121 120823 watchdog: MPD restarted (check syslog for SEGV) 20170121 120829 watchdog: MPD restarted (check syslog for SEGV) 20170121 120836 watchdog: MPD restarted (check syslog for SEGV) 20170121 120842 watchdog: MPD restarted (check syslog for SEGV) 20170121 120848 watchdog: MPD restarted (check syslog for SEGV) 20170121 120857 watchdog: MPD restarted (check syslog for SEGV) 20170121 120903 watchdog: MPD restarted (check syslog for SEGV) 20170121 120909 watchdog: MPD restarted (check syslog for SEGV) 20170121 120915 watchdog: MPD restarted (check syslog for SEGV) 20170121 120921 watchdog: MPD restarted (check syslog for SEGV) 20170121 120927 watchdog: MPD restarted (check syslog for SEGV) 20170121 120933 watchdog: MPD restarted (check syslog for SEGV) 20170121 120940 watchdog: MPD restarted (check syslog for SEGV) 20170121 120946 watchdog: MPD restarted (check syslog for SEGV) 20170121 120952 watchdog: MPD restarted (check syslog for SEGV) 20170121 120958 watchdog: MPD restarted (check syslog for SEGV) 20170121 121004 watchdog: MPD restarted (check syslog for SEGV) 20170121 121010 watchdog: MPD restarted (check syslog for SEGV) 20170121 121016 watchdog: MPD restarted (check syslog for SEGV) 20170121 121023 watchdog: MPD restarted (check syslog for SEGV) 20170121 121029 watchdog: MPD restarted (check syslog for SEGV) 20170121 121035 watchdog: MPD restarted (check syslog for SEGV) 20170121 121041 watchdog: MPD restarted (check syslog for SEGV) 20170121 121047 watchdog: MPD restarted (check syslog for SEGV) 20170121 121053 watchdog: MPD restarted (check syslog for SEGV) 20170121 121059 watchdog: MPD restarted (check syslog for SEGV) 20170121 121106 watchdog: MPD restarted (check syslog for SEGV) 20170121 121112 watchdog: MPD restarted (check syslog for SEGV) 20170121 121118 watchdog: MPD restarted (check syslog for SEGV) 20170121 121124 watchdog: MPD restarted (check syslog for SEGV) 20170121 121130 watchdog: MPD restarted (check syslog for SEGV) 20170121 121136 watchdog: MPD restarted (check syslog for SEGV) 20170121 121143 watchdog: MPD restarted (check syslog for SEGV) 20170121 121149 watchdog: MPD restarted (check syslog for SEGV) 20170121 121155 watchdog: MPD restarted (check syslog for SEGV) 20170121 121201 watchdog: MPD restarted (check syslog for SEGV) 20170121 121207 watchdog: MPD restarted (check syslog for SEGV) 20170121 121213 watchdog: MPD restarted (check syslog for SEGV) 20170121 121219 watchdog: MPD restarted (check syslog for SEGV) 20170121 121226 watchdog: MPD restarted (check syslog for SEGV) 20170121 121232 watchdog: MPD restarted (check syslog for SEGV) 20170121 121238 watchdog: MPD restarted (check syslog for SEGV) 20170121 121244 watchdog: MPD restarted (check syslog for SEGV) 20170121 121251 watchdog: MPD restarted (check syslog for SEGV) 20170121 121257 watchdog: MPD restarted (check syslog for SEGV) 20170121 121303 watchdog: MPD restarted (check syslog for SEGV) 20170121 121309 watchdog: MPD restarted (check syslog for SEGV) 20170121 121315 watchdog: MPD restarted (check syslog for SEGV) 20170121 121321 watchdog: MPD restarted (check syslog for SEGV) 20170121 121327 watchdog: MPD restarted (check syslog for SEGV) 20170121 121334 watchdog: MPD restarted (check syslog for SEGV) 20170121 121340 watchdog: MPD restarted (check syslog for SEGV) 20170121 121346 watchdog: MPD restarted (check syslog for SEGV) 20170121 121352 watchdog: MPD restarted (check syslog for SEGV) 20170121 121358 watchdog: MPD restarted (check syslog for SEGV) 20170121 121404 watchdog: MPD restarted (check syslog for SEGV) 20170121 121411 watchdog: MPD restarted (check syslog for SEGV) 20170121 121417 watchdog: MPD restarted (check syslog for SEGV) 20170121 121423 watchdog: MPD restarted (check syslog for SEGV) 20170121 121429 watchdog: MPD restarted (check syslog for SEGV) 20170121 121435 watchdog: MPD restarted (check syslog for SEGV) 20170121 121441 watchdog: MPD restarted (check syslog for SEGV) 20170121 121447 watchdog: MPD restarted (check syslog for SEGV) 20170121 121453 watchdog: MPD restarted (check syslog for SEGV) 20170121 121500 watchdog: MPD restarted (check syslog for SEGV) 20170121 121506 watchdog: MPD restarted (check syslog for SEGV) 20170121 121512 watchdog: MPD restarted (check syslog for SEGV) 20170121 121518 watchdog: MPD restarted (check syslog for SEGV) 20170121 121524 watchdog: MPD restarted (check syslog for SEGV) 20170121 121530 watchdog: MPD restarted (check syslog for SEGV) 20170121 121537 watchdog: MPD restarted (check syslog for SEGV) 20170121 121543 watchdog: MPD restarted (check syslog for SEGV) 20170121 121549 watchdog: MPD restarted (check syslog for SEGV) 20170121 121555 watchdog: MPD restarted (check syslog for SEGV) 20170121 121601 watchdog: MPD restarted (check syslog for SEGV) 20170121 121607 watchdog: MPD restarted (check syslog for SEGV) 20170121 121613 watchdog: MPD restarted (check syslog for SEGV) 20170121 121620 watchdog: MPD restarted (check syslog for SEGV) 20170121 121626 watchdog: MPD restarted (check syslog for SEGV) 20170121 121632 watchdog: MPD restarted (check syslog for SEGV) 20170121 121638 watchdog: MPD restarted (check syslog for SEGV) 20170121 121644 watchdog: MPD restarted (check syslog for SEGV) 20170121 121650 watchdog: MPD restarted (check syslog for SEGV) pi@moode:~ $ It's long but it looks more in keeping with the sample log you posted. What do you think I need to do to connect Moode Audio to JRMC22? This is new to me and I really appreciate your patience and support. Brad Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 Tim, I unplugged my RPi, plugged it back in again and captured the following log: login as: pi [email protected]'s password: Linux 4.4.30-v7+ J-Lite Core, armv7l Architecture __ ____ ____ __ _ ___ ___ ___/ /__ / __ \/ __/ / ' \/ _ \/ _ \/ _ / -_) /_/ /\ \ /_/_/_/\___/\___/\_,_/\__/\____/___/ moodeOS Version 1.1 dual-kernel © 2016 Tim Curtis moodeOS is based on Debian GNU/Linux and is custom factored for Moode Audio Player. moodeOS and Moode Audio Player are provided for free by the copyright holders and contributors and come with no expressed or implied warranties or any other guarantees. Last login: Fri Jan 20 20:57:58 2017 from bradssurfacepro4.web-pass.com pi@moode:~ $ cat var/log/moode.log cat: var/log/moode.log: No such file or directory pi@moode:~ $ cat /var/log/moode.log 20170121 120733 worker: Startup 20170121 120735 worker: Host (moode) 20170121 120735 worker: Hdwr (Pi-3B 1GB) 20170121 120735 worker: Arch (armv7l) 20170121 120735 worker: Kver (4.4.30-v7+) 20170121 120735 worker: Ktyp (Standard) 20170121 120735 worker: Gov (ondemand) 20170121 120735 worker: OS (moodeOS 1.1) 20170121 120735 worker: Rel (Moode 3.1 2016-12-05) 20170121 120735 worker: Upd (None) 20170121 120735 worker: MPD () 20170121 120735 worker: Session loaded 20170121 120735 worker: Debug logging (on) 20170121 120735 worker: File check... 20170121 120735 worker: File check ok 20170121 120736 worker: Auto-shuffle deactivated 20170121 120736 worker: USB sources (none attached) 20170121 120736 worker: MPD scheduler policy (time-share) 20170121 120736 worker: MPD started 20170121 120736 worker: wlan0 exists 20170121 120736 worker: wlan0 trying SSID (BradsNetN) 20170121 120736 worker: UPnP renderer started 20170121 120736 worker: HDMI port off 20170121 120736 worker: Audio (I2S audio device) 20170121 120736 worker: Audio (HIFI Digi+) 20170121 120736 worker: ALSA outputs unmuted 20170121 120736 worker: ALSA mixer name (Digital) 20170121 120736 worker: MPD volume control (software) 20170121 120736 openMpdSocket(): could not connect to MPD 20170121 120736 readMpdResponse() error: fgets() fail due to socket being timed out or PHP/MPD connection failure 20170121 120736 readMpdResponse() $resp: () 20170121 120736 worker: 20170121 120736 worker: 20170121 120737 worker: Hdwr volume controller not detected 20170121 120737 worker: Volume level (0) restored 20170121 120737 worker: wlan0 (192.168.1.143) 20170121 120737 worker: eth0 exists 20170121 120737 worker: eth0 address not assigned 20170121 120737 worker: NAS sources (none configured) 20170121 120737 readMpdResponse() error: fgets() fail due to socket being timed out or PHP/MPD connection failure 20170121 120737 readMpdResponse() $resp: () 20170121 120737 worker: MPD consume reset to off 20170121 120737 worker: MPD crossfade (off) 20170121 120737 readMpdResponse() error: fgets() fail due to socket being timed out or PHP/MPD connection failure 20170121 120737 readMpdResponse() $resp: () 20170121 120737 worker: Watchdog started 20170121 120737 worker: End startup 20170121 120737 worker: Ready 20170121 120737 watchdog: MPD restarted (check syslog for SEGV) 20170121 120743 watchdog: MPD restarted (check syslog for SEGV) 20170121 120749 watchdog: MPD restarted (check syslog for SEGV) 20170121 120755 watchdog: MPD restarted (check syslog for SEGV) 20170121 120802 watchdog: MPD restarted (check syslog for SEGV) 20170121 120808 watchdog: MPD restarted (check syslog for SEGV) 20170121 120817 watchdog: MPD restarted (check syslog for SEGV) 20170121 120823 watchdog: MPD restarted (check syslog for SEGV) 20170121 120829 watchdog: MPD restarted (check syslog for SEGV) 20170121 120836 watchdog: MPD restarted (check syslog for SEGV) 20170121 120842 watchdog: MPD restarted (check syslog for SEGV) 20170121 120848 watchdog: MPD restarted (check syslog for SEGV) 20170121 120857 watchdog: MPD restarted (check syslog for SEGV) 20170121 120903 watchdog: MPD restarted (check syslog for SEGV) 20170121 120909 watchdog: MPD restarted (check syslog for SEGV) 20170121 120915 watchdog: MPD restarted (check syslog for SEGV) 20170121 120921 watchdog: MPD restarted (check syslog for SEGV) 20170121 120927 watchdog: MPD restarted (check syslog for SEGV) 20170121 120933 watchdog: MPD restarted (check syslog for SEGV) 20170121 120940 watchdog: MPD restarted (check syslog for SEGV) 20170121 120946 watchdog: MPD restarted (check syslog for SEGV) 20170121 120952 watchdog: MPD restarted (check syslog for SEGV) 20170121 120958 watchdog: MPD restarted (check syslog for SEGV) 20170121 121004 watchdog: MPD restarted (check syslog for SEGV) 20170121 121010 watchdog: MPD restarted (check syslog for SEGV) 20170121 121016 watchdog: MPD restarted (check syslog for SEGV) 20170121 121023 watchdog: MPD restarted (check syslog for SEGV) 20170121 121029 watchdog: MPD restarted (check syslog for SEGV) 20170121 121035 watchdog: MPD restarted (check syslog for SEGV) 20170121 121041 watchdog: MPD restarted (check syslog for SEGV) 20170121 121047 watchdog: MPD restarted (check syslog for SEGV) 20170121 121053 watchdog: MPD restarted (check syslog for SEGV) 20170121 121059 watchdog: MPD restarted (check syslog for SEGV) 20170121 121106 watchdog: MPD restarted (check syslog for SEGV) 20170121 121112 watchdog: MPD restarted (check syslog for SEGV) 20170121 121118 watchdog: MPD restarted (check syslog for SEGV) 20170121 121124 watchdog: MPD restarted (check syslog for SEGV) 20170121 121130 watchdog: MPD restarted (check syslog for SEGV) 20170121 121136 watchdog: MPD restarted (check syslog for SEGV) 20170121 121143 watchdog: MPD restarted (check syslog for SEGV) 20170121 121149 watchdog: MPD restarted (check syslog for SEGV) 20170121 121155 watchdog: MPD restarted (check syslog for SEGV) 20170121 121201 watchdog: MPD restarted (check syslog for SEGV) 20170121 121207 watchdog: MPD restarted (check syslog for SEGV) 20170121 121213 watchdog: MPD restarted (check syslog for SEGV) 20170121 121219 watchdog: MPD restarted (check syslog for SEGV) 20170121 121226 watchdog: MPD restarted (check syslog for SEGV) 20170121 121232 watchdog: MPD restarted (check syslog for SEGV) 20170121 121238 watchdog: MPD restarted (check syslog for SEGV) 20170121 121244 watchdog: MPD restarted (check syslog for SEGV) 20170121 121251 watchdog: MPD restarted (check syslog for SEGV) 20170121 121257 watchdog: MPD restarted (check syslog for SEGV) 20170121 121303 watchdog: MPD restarted (check syslog for SEGV) 20170121 121309 watchdog: MPD restarted (check syslog for SEGV) 20170121 121315 watchdog: MPD restarted (check syslog for SEGV) 20170121 121321 watchdog: MPD restarted (check syslog for SEGV) 20170121 121327 watchdog: MPD restarted (check syslog for SEGV) 20170121 121334 watchdog: MPD restarted (check syslog for SEGV) 20170121 121340 watchdog: MPD restarted (check syslog for SEGV) 20170121 121346 watchdog: MPD restarted (check syslog for SEGV) 20170121 121352 watchdog: MPD restarted (check syslog for SEGV) 20170121 121358 watchdog: MPD restarted (check syslog for SEGV) 20170121 121404 watchdog: MPD restarted (check syslog for SEGV) 20170121 121411 watchdog: MPD restarted (check syslog for SEGV) 20170121 121417 watchdog: MPD restarted (check syslog for SEGV) 20170121 121423 watchdog: MPD restarted (check syslog for SEGV) 20170121 121429 watchdog: MPD restarted (check syslog for SEGV) 20170121 121435 watchdog: MPD restarted (check syslog for SEGV) 20170121 121441 watchdog: MPD restarted (check syslog for SEGV) 20170121 121447 watchdog: MPD restarted (check syslog for SEGV) 20170121 121453 watchdog: MPD restarted (check syslog for SEGV) 20170121 121500 watchdog: MPD restarted (check syslog for SEGV) 20170121 121506 watchdog: MPD restarted (check syslog for SEGV) 20170121 121512 watchdog: MPD restarted (check syslog for SEGV) 20170121 121518 watchdog: MPD restarted (check syslog for SEGV) 20170121 121524 watchdog: MPD restarted (check syslog for SEGV) 20170121 121530 watchdog: MPD restarted (check syslog for SEGV) 20170121 121537 watchdog: MPD restarted (check syslog for SEGV) 20170121 121543 watchdog: MPD restarted (check syslog for SEGV) 20170121 121549 watchdog: MPD restarted (check syslog for SEGV) 20170121 121555 watchdog: MPD restarted (check syslog for SEGV) 20170121 121601 watchdog: MPD restarted (check syslog for SEGV) 20170121 121607 watchdog: MPD restarted (check syslog for SEGV) 20170121 121613 watchdog: MPD restarted (check syslog for SEGV) 20170121 121620 watchdog: MPD restarted (check syslog for SEGV) 20170121 121626 watchdog: MPD restarted (check syslog for SEGV) 20170121 121632 watchdog: MPD restarted (check syslog for SEGV) 20170121 121638 watchdog: MPD restarted (check syslog for SEGV) 20170121 121644 watchdog: MPD restarted (check syslog for SEGV) 20170121 121650 watchdog: MPD restarted (check syslog for SEGV) pi@moode:~ $ It's long but it looks more in keeping with the sample log you posted. What do you think I need to do to connect Moode Audio to JRMC22? This is new to me and I really appreciate your patience and support. Brad Hi Brad, The line below from the log shows no version number for MPD. It should show MPD (0.19.19). Obviously, nothing will work without MPD running. I saw this once before when a user hand edited mpd.conf incorrectly. I'd try starting with a fresh image. 20170121 120735 worker: MPD () -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 Brad, The line below from the log shows no version number for MPD. It should show MPD (0.19.19). Obviously, nothing will work without MPD running. I saw this once before when a user hand edited mpd.conf incorrectly. I'd try starting with a fresh image. 20170121 120735 worker: MPD () -Tim Hi Brad, the message 20170121 121650 watchdog: MPD restarted (check syslog for SEGV) seems to indicate that MPD could not start properly and raised some segmentation fault error (aka crashed). You might want to look into logfile /var/log/syslog to see if you can get any hint If you have changed manually the content of "/etc/mpd.conf" file here is the content of mine: ######################################### # This file is automatically generated by # the player MPD configuration page. ######################################### follow_outside_symlinks "yes" follow_inside_symlinks "yes" db_file "/var/lib/mpd/tag_cache" sticker_file "/var/lib/mpd/sticker.sql" log_file "/var/log/mpd/mpd.log" pid_file "/var/run/mpd/pid" music_directory "/var/lib/mpd/music" playlist_directory "/var/lib/mpd/playlists" state_file "/var/lib/mpd/state" user "mpd" group "audio" bind_to_address "any" port "6600" log_level "default" zeroconf_enabled "yes" zeroconf_name "moode" samplerate_converter "soxr very high" volume_normalization "no" audio_buffer_size "8192" buffer_before_play "30%" filesystem_charset "UTF-8" id3v1_encoding "UTF-8" gapless_mp3_playback "yes" auto_update "no" mixer_type "software" max_output_buffer_size "81920" restore_paused "yes" replaygain "off" max_connections "20" decoder { plugin "ffmpeg" enabled "yes" } input { plugin "curl" } audio_output { type "alsa" name "ALSA default" device "hw:1,0" dsd_usb "yes" } audio_output { type "alsa" name "ALSA crossfeed" device "crossfeed" dsd_usb "yes" } Corresponding to this MPD configuration Link to comment
franz159 Posted January 21, 2017 Share Posted January 21, 2017 As of late I noticed strange reboots of my raspberry pi3 with Moode31. Digging into logfiles, in particulr into /var/log/messages I believe that the last message logged before a reboot was something like this: Jan 21 16:30:30 moode31ny kernel: [ 81.796312] [b]ip_tables[/b]: (C) 2000-2006 Netfilter Core Team Therefore I started googling and I found this interesting story: https://developers.soundcloud.com/blog/shoot-yourself-in-the-foot-with-iptables-and-kmod-auto-loading I'm not 100% sure if this is the same thing happening to me, but it really seems the same thing. I have to admit I do not understand the whole thing completely: what I believe I understand is that there is un-necessary and un-wanted tracking of connections which eventually fills up this "connection tracking table" causing the reboot of the system. I believe I have now "stopped" this unwanted connection tracking by (manually) issuing the command [color=#2A2E2E][font=&]iptables -t raw -A PREROUTING -j NOTRACK[/font][/color] but I'm still monitoring the situation.... If somebody understanding more than me how this iptables tracking works would like to jump in and shed some light, that would be appreciated.... -------------------------------------------- .... or I simply made my system unstable with the various tweaks I have been playing with..... I will start from a fresh image.... Link to comment
franz159 Posted January 21, 2017 Share Posted January 21, 2017 As of late I noticed strange reboots of my raspberry pi3 with Moode31. Digging into logfiles, in particulr into /var/log/messages I believe that the last message logged before a reboot was something like this: Jan 21 16:30:30 moode31ny kernel: [ 81.796312] [b]ip_tables[/b]: (C) 2000-2006 Netfilter Core Team Therefore I started googling and I found this interesting story: https://developers.soundcloud.com/blog/shoot-yourself-in-the-foot-with-iptables-and-kmod-auto-loading I'm not 100% sure if this is the same thing happening to me, but it really seems the same thing. I have to admit I do not understand the whole thing completely: what I believe I understand is that there is un-necessary and un-wanted tracking of connections which eventually fills up this "connection tracking table" causing the reboot of the system. I believe I have now "stopped" this unwanted connection tracking by (manually) issuing the command [color=#2A2E2E][font=&]iptables -t raw -A PREROUTING -j NOTRACK[/font][/color] but I'm still monitoring the situation.... If somebody understanding more than me how this iptables tracking works would like to jump in and shed some light, that would be appreciated.... -------------------------------------------- .... or I simply made my system unstable with the various tweaks I have been playing with..... I will start from a fresh image.... I promise this will be my last post for the day! I was getting crazy today with a reboot every 2 or 3 minutes..... I disconnected my USB hard disk and the reboots stopped. I think it's a matter of power: in fact I am powering the raspberry through an USB port on a power strip (which does have 4 USB ports). I guess that when I have too many devices charging on the same power strip where the raspberry is connected, my pi3 does not get enough power for the USB disk and the wifi internal adapter! I need to think to a better way of powering it.... IFI iPower maybe? Link to comment
TimCurtis Posted January 21, 2017 Share Posted January 21, 2017 I promise this will be my last post for the day! I was getting crazy today with a reboot every 2 or 3 minutes..... I disconnected my USB hard disk and the reboots stopped. I think it's a matter of power: in fact I am powering the raspberry through an USB port on a power strip (which does have 4 USB ports). I guess that when I have too many devices charging on the same power strip where the raspberry is connected, my pi3 does not get enough power for the USB disk and the wifi internal adapter! I need to think to a better way of powering it.... IFI iPower maybe? Hi, That was an interesting article from the SoundCloud devs. From what I've read the iFi power adapter is very good. -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
heathen Posted January 22, 2017 Share Posted January 22, 2017 I'm having trouble connecting to a Samba share. I just recently installed 3.1 on a RPi3 with a Hifiberry Digi+. Installation was a breeze, and I got it working with the default internet radio stations just fine. After trying to connect to a Samba share, though, Moode has become much slower, nonresponsive, and is not connecting to the Samba share. I'm certain that the fault is mine, but I don't know what I'm doing wrong. For what it's worth, my Windows machine is able to access the Samba share without any problems. Edit: When I try to just remove the NAS source the system just hangs and after restart the source is still there, and if I try to remove it again it hangs again... Link to comment
TimCurtis Posted January 23, 2017 Share Posted January 23, 2017 I'm having trouble connecting to a Samba share. I just recently installed 3.1 on a RPi3 with a Hifiberry Digi+. Installation was a breeze, and I got it working with the default internet radio stations just fine. After trying to connect to a Samba share, though, Moode has become much slower, nonresponsive, and is not connecting to the Samba share. I'm certain that the fault is mine, but I don't know what I'm doing wrong. For what it's worth, my Windows machine is able to access the Samba share without any problems. Edit: When I try to just remove the NAS source the system just hangs and after restart the source is still there, and if I try to remove it again it hangs again... Hi, Post your drive mapping from Windows for example: z: --> \\server\share Do you specify a userid and password to connect from Windows? -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
heathen Posted January 23, 2017 Share Posted January 23, 2017 Hi, Post your drive mapping from Windows for example: z: --> \\server\share Do you specify a userid and password to connect from Windows? -Tim The Samba share isn't mapped to a drive letter in Windows. It shows up under "Network" in Windows Explorer. Also, I don't need to supply a userid and password to connect from Windows. If it helps, here is the entry from smb.conf: [Music1] comment = Primary Music Storage path = /media/lucas/storage1/Music browseable = yes read only = no Link to comment
TimCurtis Posted January 23, 2017 Share Posted January 23, 2017 The Samba share isn't mapped to a drive letter in Windows. It shows up under "Network" in Windows Explorer. Also, I don't need to supply a userid and password to connect from Windows. If it helps, here is the entry from smb.conf:[Music1] comment = Primary Music Storage path = /media/lucas/storage1/Music browseable = yes read only = no Hi, To troubleshoot, ssh into moode and try and mount the Samba share manually. -TIm Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
heathen Posted January 23, 2017 Share Posted January 23, 2017 Hi, To troubleshoot, ssh into moode and try and mount the Samba share manually. -TIm I'm able to ssh into moode but I don't know how to mount the Samba share manually. Link to comment
Gabriele Fubiani Posted January 23, 2017 Share Posted January 23, 2017 Hello to allnot being an expert in these systems, I ask a help to someone in the forum, to be able to be recognized in MOODEAUDIO, my Nas WD MY BOOK LIVE.I can not figure out what to put in the appropriate windows.Thanks to those who can 'help me.Greetings Ciao A tuttinon essendo esperto di questi sistemi , chiedo un aiuto a qualcuno del forum , per riuscire a far riconoscere a MOODEAUDIO ,il mio Nas WD MY BOOK LIVE.Non riesco a capire cosa devo mettere nelle apposite finestre .Grazie a chi puo' aiutarmi .Saluti Link to comment
DomieMic65 Posted January 27, 2017 Share Posted January 27, 2017 Since yesterday I have the m2tech Evo DAC Two Plus for testing and I see that it doesn't connect with the Moode in USB, even though it is supposed to work with Linux. It doesn't show at all on Moode MPD config menu! Has anyone use this DAC with Rpi3/Moode? The other option would be to use a I2S HAT for the rpi to connect with the Two Plus but I would like to know if it works wth USB too. May be a firmware update that the test unit I have does not have? Don't know... It sounds quite good connected to my Mac! A very interesting little DAC with many upgrades (clock, PS)! Sent from my Nexus 5X Mac Mini with JRMC26 or Audirvana / Raspberry4B_4GB(GentooPlayer_LMS) / Raspberry Rpi3B+: Allo DigiOne(GentooPlayer) - M2Tech Evo DAC Two Plus/iPurifier2 - Schiit Vali 2 - Densen DM20pre/30pwr amps - Spendor SP2/3E, Sennheiser HD600 & HD25Aluminum - Audeze Sine Cables: Vovox, DIY, Furutech. Portable sources: iPad, DELL Laptop with JRiver MC26 Link to comment
frengo Posted January 27, 2017 Share Posted January 27, 2017 Hello everyone. Can anyone tell me how to (or post a link That I illustrious how-to) connect (and enable) six buttons on the RaspPI2 with MoodeAudio with standard "Play / Stop", "Pause / Stop", "Next Track / Previous track", and "Volume up / Volume down" functions ? Maybe it's already been done and I can not find related thread ... Thank you in advance. Frengo. Link to comment
kvm Posted January 31, 2017 Share Posted January 31, 2017 Hello everyone I have recently upgraded/ reinstalled moodeOS 3.1. I connected my 1TB USB HDD with just about 10K tracks. The "update MPD" in the configure--> source menu is taking 'forever' - I waited more than 20+ hours! I tried reinstalling the OS but to no avail. The Library tab lists some arbitrary 2 tracks. The 'Browse' tab lists the USB drive but only shows '$RECYCLE_BIN folder but no other folder shows up for some strange reason. I couldn't find any way to check the MPD update progress either! However surprisingly, I could find all the tracks over Moode DLNA DB when accessed from my TV's media player. So was wondering how/why the MPD update is stuck while DLNA DB is updated. This same HDD was working fine with 2.7 but I don't remember how much time it took to update MPD last time. Pl help me to solve this issue. thanks Link to comment
TimCurtis Posted January 31, 2017 Share Posted January 31, 2017 Hello everyone I have recently upgraded/ reinstalled moodeOS 3.1. I connected my 1TB USB HDD with just about 10K tracks. The "update MPD" in the configure--> source menu is taking 'forever' - I waited more than 20+ hours! I tried reinstalling the OS but to no avail. The Library tab lists some arbitrary 2 tracks. The 'Browse' tab lists the USB drive but only shows '$RECYCLE_BIN folder but no other folder shows up for some strange reason. I couldn't find any way to check the MPD update progress either! However surprisingly, I could find all the tracks over Moode DLNA DB when accessed from my TV's media player. So was wondering how/why the MPD update is stuck while DLNA DB is updated. This same HDD was working fine with 2.7 but I don't remember how much time it took to update MPD last time. Pl help me to solve this issue. thanks Hi, Very odd. To troubleshoot try examining mpd log: - System config: Clear system logs - Sources: UPDATE MPD DB - cat /var/log/mpd/mpd.log MPD log level can be increased by editing /etc/mpd.conf and then restarting mpd - change log_level "default" to log_level "verbose" -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
kvm Posted January 31, 2017 Share Posted January 31, 2017 Many thanks Tim for the quick reply. Really appreciate it! I could debug this further with your above suggestions and could find that MPD update is stuck with some file in $RECYCLE_BIN which upon clearing, went thru. Now the update completed successfully! Many thanks, again! Link to comment
chauphuong Posted February 1, 2017 Share Posted February 1, 2017 Is there anyway to reduce bass for speakers in Moode 3.1? Link to comment
macuniverse Posted February 1, 2017 Share Posted February 1, 2017 Is there any plans to implement Spotify Connect in Moode? That's you control Spotify playing in Moode using another device. This is the only thing preventing me using it ATM. I listen to 50/50 Spotify and my own FLAC files. PS. I'm not referring to Spotify app which is limited at best (not to mention unstable at times) Link to comment
TimCurtis Posted February 1, 2017 Share Posted February 1, 2017 Is there any plans to implement Spotify Connect in Moode? That's you control Spotify playing in Moode using another device. This is the only thing preventing me using it ATM. I listen to 50/50 Spotify and my own FLAC files. PS. I'm not referring to Spotify app which is limited at best (not to mention unstable at times) Hi, https://twitter.com/MoodeAudio https://github.com/plietar/librespot/issues Once the volume issues are addressed, I'll add it to my TODO list. -Tim Enjoy the Music ! http://moodeaudio.org http://twitter.com/MoodeAudio Link to comment
macuniverse Posted February 1, 2017 Share Posted February 1, 2017 Hi, https://twitter.com/MoodeAudio https://github.com/plietar/librespot/issues Once the volume issues are addressed, I'll add it to my TODO list. -Tim Hi Tim, thanks for the quick reply. I don't have a Twitter or FB account (don't use them) so I missed the recent dev efforts. Looking forward to giving it a go in Moode. Link to comment
DomieMic65 Posted February 2, 2017 Share Posted February 2, 2017 To Tim and all.. What is the ALSA version of the Mood? Thnx Mac Mini with JRMC26 or Audirvana / Raspberry4B_4GB(GentooPlayer_LMS) / Raspberry Rpi3B+: Allo DigiOne(GentooPlayer) - M2Tech Evo DAC Two Plus/iPurifier2 - Schiit Vali 2 - Densen DM20pre/30pwr amps - Spendor SP2/3E, Sennheiser HD600 & HD25Aluminum - Audeze Sine Cables: Vovox, DIY, Furutech. Portable sources: iPad, DELL Laptop with JRiver MC26 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