Thank you.
I had been trying (unsuccessfully!) to use Bubbleupnp which controls most of the other devices in the house. I will use your suggestion.
Richard
Hello!
Please help to solve clics/pops for dsd playback on MPD - its help for moode, because it based on it!
https://github.com/lintweaker/mpd-dsd-019/issues/25
Please help to solve clics/pops for dsd playback on MPD - its help for moode, because it based on it!
https://github.com/lintweaker/mpd-dsd-019/issues/25
I still need to send to you the package, on my todo
Here is an example of the grouping I'm testing for the Radio stations;
What do you think ?
Attachments
Hi Richard,
Turn on UPnP renderer in System config. U should see "Moode UPNP" show up in Bubble.
-Tim
Hi,
I think u will have to wait for these patches to be incorporated into mainline MPD release. I'd suggest posting the issue on MPD forum so at least Max K sees it. I don't know whether he and the other MPD devs monitor lintweaker.
-Tim
Yes, In this case it's the Silk browser that came as a standard install on my Fire.
Skip
Tim
I did that and I could see Moode in the Bubble display. But when I tried to select and play a track nothing responded. I wonder if the Moode program I downloaded has in some way got corrupted. I will try wiping the SD card clean and doing a fresh install.
Richard
I still need to send to you the package, on my todo
Here is an example of the grouping I'm testing for the Radio stations;
What do you think ?
Hi Richard,
The challenge is that there are many possible ways to organize the station list that are equally good. How to decide?
An alternative to subfolders is to add metadata to the radio station sql table for example Genre, Country, Group, and then make a Library panel like screen. This would be a lot of work!
-Tim
Skip
Thanks, I will give that a try after I have reinstalled Moode (see post above)
Richard
Hi Richard,
Very odd. It should be 100% when MPD set to Software volume control and DAC in fact has on-chip hardware volume controller.
If u know a little Linux ssh then post the output from the following commands:
1) amixer -c 1
2) aplay -l
3) ./mlog.sh
Regards,
Tim
Hi Tim,
here we go...
Regards
Kai
___
pi@moode2:~ $ ./mlog.sh
20160626 192218 worker: Startup
20160626 192220 worker: Host (moode2)
20160626 192220 worker: Hdwr (Pi-3B 1GB)
20160626 192220 worker: Arch (armv7l)
20160626 192220 worker: Krnl (4.4.8-v7+)
20160626 192220 worker: OS (moodeOS 1.0)
20160626 192220 worker: Rel (Moode 2.6 2016-06-07)
20160626 192220 worker: MPD (0.19.15)
20160626 192220 worker: Session loaded
20160626 192220 worker: Debug logging (off)
20160626 192220 worker: File check...
20160626 192220 worker: File check ok
20160626 192221 worker: Auto-shuffle deactivated
20160626 192221 worker: USB sources ()
20160626 192221 worker: MPD started
20160626 192221 worker: wlan0 does not exist
20160626 192221 worker: Audio (I2S audio device)
20160626 192221 worker: Audio (HiFiBerry Amp(Amp+))
20160626 192221 worker: ALSA outputs unmuted
20160626 192221 worker: ALSA mixer name (Master)
20160626 192221 worker: MPD volume control (hardware)
20160626 192221 worker: Hdwr volume controller exists
20160626 192221 worker: Volume level (0) restored
20160626 192221 worker: wlan0 address not assigned
20160626 192221 worker: eth0 exists
20160626 192221 worker: eth0 (192.168.178.234)
20160626 192221 worker: Airplay receiver started
20160626 192222 worker: NAS sources (mountall initiated)
20160626 192222 worker: MPD consume reset to off
20160626 192222 worker: Autoplay on
20160626 192222 worker: Watchdog started
20160626 192222 worker: End startup
20160626 192222 worker: Ready
20160626 192328 waitWorker(): Start (sys-config, w_active=0)
20160626 192328 waitWorker(): End (sys-config, w_active=0)
20160626 192329 engine-mpd: Connect
20160626 192329 engine-mpd: Session loaded
20160626 192329 engine-mpd: Generating enhanced metadata
20160626 192329 engine-mpd: Metadata returned to client
20160626 192329 engine-mpd: Connect
20160626 192329 engine-mpd: Session loaded
20160626 192329 engine-mpd: Idle
20160626 192334 waitWorker(): Start (sys-config, w_active=1)
20160626 192335 waitWorker(): Wait (1)
20160626 192336 waitWorker(): Wait (2)
20160626 192337 worker: Job airplaysvc
20160626 192337 engine-mpd: Connect
20160626 192337 engine-mpd: Session loaded
20160626 192337 engine-mpd: Generating enhanced metadata
20160626 192337 engine-mpd: Metadata returned to client
20160626 192337 engine-mpd: Connect
20160626 192337 engine-mpd: Session loaded
20160626 192337 engine-mpd: Idle
20160626 192337 waitWorker(): Wait (3)
20160626 192337 waitWorker(): End (sys-config, w_active=0)
20160626 192338 engine-mpd: Connect
20160626 192338 engine-mpd: Session loaded
20160626 192338 engine-mpd: Generating enhanced metadata
20160626 192338 engine-mpd: Metadata returned to client
20160626 192338 engine-mpd: Connect
20160626 192338 engine-mpd: Session loaded
20160626 192338 engine-mpd: Idle
20160626 192343 waitWorker(): Start (sys-config, w_active=1)
20160626 192343 worker: Job airplaysvc
20160626 192343 worker: Airplay metadata on
20160626 192343 worker: (/usr/local/bin/shairport-sync -a "Moode_Airplay2" -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 -c Master > /dev/null 2>&1 &)
20160626 192344 waitWorker(): Wait (1)
20160626 192344 waitWorker(): End (sys-config, w_active=0)
20160626 192345 engine-mpd: Connect
20160626 192345 engine-mpd: Session loaded
20160626 192345 engine-mpd: Generating enhanced metadata
20160626 192345 engine-mpd: Metadata returned to client
20160626 192345 engine-mpd: Connect
20160626 192345 engine-mpd: Session loaded
20160626 192345 engine-mpd: Idle
Tim
I have no idea what is going on but I downloaded 2.6 again and reloaded it on the SD card. I still had no joy then changed the Volume Control to "Hardware" and the MDAC sprang into life. Is it because the MDAC has a volume control itself?
I think I will quit while I am ahead! Thank you very much for the help.
Richard
I've already posted! Nobody wants to do anything! We need to gather together and constantly remind them!
You can maintain me?
Can somebody explain me: why sound completely different compare to volumio1.55? Moode sounds much more harsh and bright, with huge amount of bass. Hardware is same, just swapping sd's.
My setup: Rpi 2 + PiFi Digi Coaxial + Lavry DA 10 + Primare A30.1 + Elac 249, all settings are the same. Jitter? Evil spirit? I'm going crazy?
My setup: Rpi 2 + PiFi Digi Coaxial + Lavry DA 10 + Primare A30.1 + Elac 249, all settings are the same. Jitter? Evil spirit? I'm going crazy?
Hi Alexey!
I've tested all available audio players for raspberry pi and am using a very sensitive high end audio system for testing. MOODE is one of the 2 best sounding players together with Archphile. Except Archphile soundwise there is no competition at all. Volumio is clearly inferior compared to MOODE and shows too much rounded, muddy sound with unprecise bass to my ears. Moode delivers straight, honest and clear sound performance that of course demands a balanced audio system to give adequate synergy. Sorry- only my subjective impression.
Greetingz, Robert
Hi Kai,
The log shows correct volume mixer configuration for the AMP+ and for shairport-sync. Both are using the name "Master" which is supposed to be the name that AMP+ requires.
20160626 192221 worker: Audio (I2S audio device)
20160626 192221 worker: Audio (HiFiBerry Amp(Amp+))
20160626 192221 worker: ALSA outputs unmuted
20160626 192221 worker: ALSA mixer name (Master)
20160626 192221 worker: MPD volume control (hardware)
20160626 192221 worker: Hdwr volume controller exists
20160626 192343 worker: (/usr/local/bin/shairport-sync -a "Moode_Airplay2" -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 -c Master > /dev/null 2>&1 &)
Post output of the following command to verify that AMP+ is in fact using mixer name "Master"
amixer -c 0
Regards,
Tim
this is output of amixer -c 0
pi@moode2:~ $ amixer -c 0
Simple mixer control 'Master',0
Capabilities: volume volume-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 248
Mono: 0 [0%]
Simple mixer control 'Channels',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 248
Front Left: 218 [88%]
Front Right: 218 [88%]
pi@moode2:~ $ amixer -c 0
Simple mixer control 'Master',0
Capabilities: volume volume-joined
Playback channels: Mono
Capture channels: Mono
Limits: 0 - 248
Mono: 0 [0%]
Simple mixer control 'Channels',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 248
Front Left: 218 [88%]
Front Right: 218 [88%]
Hi Kai,
ALSA shows output of 88% volume level. If there is low sound level at the speakers then it would suggest something external to Moode software.
-Tim