Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Official moOde 6.7.1 support thread
Question 
(07-22-2020, 10:15 PM)Tim Curtis Wrote: Hi,

Post all bug reports for moOde 6.7.1 or moOde 6.7.0 -> 6.7.1 in-place update in this thread. Please paste log output, scripts, etc in code boxes for readability.

-Tim

Hi,

just made an update from 4.2 (running for > 2 yrs without any problems) to current 6.7.1. Configs:

1) Raspi 3B with HifiBerry DAC+ --> installed on an external SSD (128 GB Intenso USB 3) --> no probs at all, runs fine, great SQ
2) Raspi 3B with 7" official display connected via HDMI to Marantz AVR --> same install --> sound only via headphone jack, no sound via HDMI

This is what moodeutl -l says:

Code:
pi@moode-WZ:~ $ moodeutl -l
20201216 160739 worker: -- Start
20201216 160739 worker: Successfully daemonized
20201216 160740 worker: Integrity check (passed)
20201216 160740 worker: Session loaded
20201216 160740 worker: Debug logging (off)
20201216 160740 worker: Device raw: (0:Headphones|1:empty|2:empty|3:empty
20201216 160740 worker: Device i2s: (none)
20201216 160740 worker: Device mpd: (0:Pi Headphone jack)
20201216 160740 worker: Device ses: (0|Pi Headphone jack|Headphone|0%)
20201216 160740 worker: ALSA Headphone volume set to (0%)
20201216 160740 worker: -- System
20201216 160742 worker: Host     (moode-WZ)
20201216 160742 worker: moOde    (6.7.1 2020-07-22)
20201216 160742 worker: RaspiOS  (10.4)
20201216 160742 worker: Kernel   (5.4.51-v7+ #1325)
20201216 160742 worker: Platform (Pi-3B 1GB v1.2)
20201216 160742 worker: ARM arch (armv7l, 32-bit kernel)
20201216 160742 worker: MPD ver  (0.21.24)
20201216 160742 worker: CPU gov  (ondemand)
20201216 160742 worker: USB boot enabled
20201216 160743 worker: File system not expanded yet
20201216 160743 worker: HDMI port on
20201216 160743 worker: File check (OK)
20201216 160743 worker: -- Network
20201216 160743 worker: eth0 exists
20201216 160744 worker: IP addr (192.168.178.53)
20201216 160744 worker: Netmask (255.255.255.0)
20201216 160744 worker: Gateway (192.168.178.1)
20201216 160744 worker: Pri DNS (192.168.178.1)
20201216 160744 worker: Domain  (fritz.box)
20201216 160744 worker: wlan0 does not exist
20201216 160744 worker: -- Audio
20201216 160745 worker: MPD conf updated
20201216 160745 worker: ALSA outputs unmuted
20201216 160745 worker: ALSA card number (0)
20201216 160745 worker: Audio output (Pi Headphone jack)
20201216 160746 worker: Audio formats (U8, S16_LE)
20201216 160746 worker: ALSA mixer name (Headphone)
20201216 160746 worker: MPD volume control (software)
20201216 160746 worker: Hdwr volume controller exists
20201216 160746 worker: Max ALSA volume (100%)
20201216 160746 worker: Reset renderer active flags
20201216 160746 worker: -- MPD
20201216 160746 worker: MPD started
20201216 160747 worker: MPD accepting connections
20201216 160747 worker: Configure MPD outputs
20201216 160747 worker: MPD output 1 ALSA default (on)
20201216 160747 worker: MPD output 2 ALSA crossfeed (off)
20201216 160747 worker: MPD output 3 ALSA parametric eq (off)
20201216 160747 worker: MPD output 4 ALSA graphic eq (off)
20201216 160747 worker: MPD output 5 ALSA polarity inversion (off)
20201216 160747 worker: MPD output 6 ALSA bluetooth (off)
20201216 160747 worker: MPD output 7 HTTP stream (off)
20201216 160747 worker: MPD crossfade (off)
20201216 160747 worker: -- Feature availability
20201216 160747 worker: Source select (available)
20201216 160747 worker: Source select (source: MPD)
20201216 160747 worker: Source select (output: Pi Headphone jack)
20201216 160748 worker: Bluetooth (available)
20201216 160748 worker: Airplay renderer (available)
20201216 160748 worker: Spotify renderer (available)
20201216 160748 worker: Squeezelite renderer (available)
20201216 160748 worker: UPnP renderer (available)
20201216 160748 worker: DLNA server (available)
20201216 160748 worker: UPnP browser (available)
20201216 160748 worker: Audio scrobbler (available)
20201216 160748 worker: GPIO button handler (available)
20201216 160748 worker: -- Music sources
20201216 160748 worker: USB source (6523-21A2)
20201216 160748 worker: NAS and UPnP sources (none configured)
20201216 160748 worker: -- Miscellaneous
20201216 160748 worker: USB volume knob (Off)
20201216 160748 worker: USB auto-mounter (udisks-glue)
20201216 160748 worker: LED0 (On)
20201216 160748 worker: LED1 (On)
20201216 160748 worker: Saved MPD vol level (0)
20201216 160748 worker: Preamp volume level (0)
20201216 160748 worker: MPD volume level (80) restored
20201216 160748 worker: ALSA Headphone volume (100%)
20201216 160748 worker: Auto-play (Off)
20201216 160748 worker: LocalUI started
20201216 160748 worker: Maintenance interval (3 hrs)
20201216 160748 worker: Screen saver activation (Never)
20201216 160748 worker: Session permissions (OK)
20201216 160748 worker: Watchdog started
20201216 160748 worker: Ready

As far as I can see, nothing suspicious. Audio output should work via HDMI as it worked with 4.2 for years. Nevertheless: Output is only via headphone jack.

Tim: In a previous post I found the following statement from you:


Quote:If you are using HDMI audio out then unplug it because IIRC the Pi does not support simultaneous HDMI and 3.5mm RCA output.

In my case, HDMI does not work regardless RCA plugged and vice versa: RCA out always works. In the MPD config page ""Audio Output" I can only select "Pi Headphone Jack" - which I did due to lacking further options, e.g. "HDMI". Is this the problem?

For further info, this is my /boot/config.txt:
Code:
pi@moode-WZ:/boot $ cat config.txt
disable_splash=1
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_force_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=audio=on
lcd_rotate=2
dtoverlay=disable-wifi
#dtoverlay=disable-bt
hdmi_ignore_cec_init=1
hdmi_ignore_cec=1

Any further ideas?

Thanks a lot in advance and kind greetz from Germany
Regards
Jörg
Reply
Very odd.

This log entry indicates there is no HDMI port, only Headphone
20201216 160740 worker: Device raw: (0:Headphones|1:empty|2:empty|3:empty

This log entry indicates the HDMI port is on
20201216 160743 worker: HDMI port on

If Linux is able to recognize and configure HDMI port(s) it will show up in the device list printed by the command below.

Code:
aplay -l

Maybe something that was added to config.txt is causing an issue?
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
(12-16-2020, 04:30 PM)Tim Curtis Wrote: Very odd.

This log entry indicates there is no HDMI port, only Headphone
20201216 160740 worker: Device raw: (0:Headphones|1:empty|2:empty|3:empty

This log entry indicates the HDMI port is on
20201216 160743 worker: HDMI port on

If Linux is able to recognize and configure HDMI port(s) it will show up in the device list printed by the command below.

Code:
aplay -l

Maybe something that was added to config.txt is causing an issue?

Even more odd:
Code:
cat  /proc/asound/cards
0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                     bcm2835 Headphones

Looks like that there is no HDMI port at all. Just doing apt update and upgrade and will reboot afterwards - I will report then.

Do not think that the additional lines in config.txt cause issues - at least the cec inactivation worked as intended. Perhaps some sort of kernel regression?
Regards
Jörg
Reply
Doubtful cos if there were a kernel issue it would affect everyone that uses 6.7.1 and HDMI.

Best to start with stock image from moodeaudio.org and confirm HDMI port shows up.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
(12-16-2020, 04:52 PM)Kikaha Wrote:
(12-16-2020, 04:30 PM)Tim Curtis Wrote: Very odd.

This log entry indicates there is no HDMI port, only Headphone
20201216 160740 worker: Device raw: (0:Headphones|1:empty|2:empty|3:empty

This log entry indicates the HDMI port is on
20201216 160743 worker: HDMI port on

If Linux is able to recognize and configure HDMI port(s) it will show up in the device list printed by the command below.

Code:
aplay -l

Maybe something that was added to config.txt is causing an issue?

Even more odd:
Code:
cat  /proc/asound/cards
0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                     bcm2835 Headphones

Looks like that there is no HDMI port at all. Just doing apt update and upgrade and will reboot afterwards - I will report then.

Do not think that the additional lines in config.txt cause issues - at least the cec inactivation worked as intended. Perhaps some sort of kernel regression?
Jorg,
try to disable HDMI and then enable it again in the system config page, clicking on SET both time...
regards,
Francesco
Reply
(12-16-2020, 04:52 PM)Kikaha Wrote:
(12-16-2020, 04:30 PM)Tim Curtis Wrote: Very odd.

This log entry indicates there is no HDMI port, only Headphone
20201216 160740 worker: Device raw: (0:Headphones|1:empty|2:empty|3:empty

This log entry indicates the HDMI port is on
20201216 160743 worker: HDMI port on

If Linux is able to recognize and configure HDMI port(s) it will show up in the device list printed by the command below.

Code:
aplay -l

Maybe something that was added to config.txt is causing an issue?

Even more odd:
Code:
cat  /proc/asound/cards
0 [Headphones     ]: bcm2835_headphonbcm2835 Headphones - bcm2835 Headphones
                     bcm2835 Headphones

Looks like that there is no HDMI port at all. Just doing apt update and upgrade and will reboot afterwards - I will report then.

Do not think that the additional lines in config.txt cause issues - at least the cec inactivation worked as intended. Perhaps some sort of kernel regression?

Hm. Looks like I bricked my raspi. Apt update and apt ugrade finished, but no boot... I will set up the entire system again.
Regards
Jörg
Reply
Quote:2) Raspi 3B with 7" official display connected via HDMI to Marantz AVR --> same install --> sound only via headphone jack, no sound via HDMI

Possibly an unexpected conflict somewhere because of the local display?

I just looked at my only Official Display-equipped moOde player. It's running the testing version of moOde r7.0.0 but it has the same behavior as reported by the OP. Here's snippets of moodeutl -l and aplay -l outputs

Code:
20201216 121755 worker: -- Device
20201216 121755 worker: ALSA cards: (0:Headphones | 1:empty | 2:empty | 3:empty
20201216 121755 worker: Configured: (0:Pi Headphone jack | mixer:(Headphone) | alsavol:0)
20201216 121755 worker: ALSA mixer actual (Headphone)
20201216 121756 worker: ALSA Headphone volume set to (0%)
20201216 121756 worker: -- System
20201216 121757 worker: Host     (moodeld)
20201216 121757 worker: moOde    (7.0.0 2020-12-15)
20201216 121757 worker: RaspiOS  (10.6)
20201216 121757 worker: Kernel   (5.4.77-v7+ #1371)
20201216 121757 worker: Platform (Pi-3B+ 1GB v1.3)
20201216 121757 worker: ARM arch (armv7l, 32-bit kernel)
20201216 121757 worker: MPD ver  (0.22.3_p0x3)
20201216 121757 worker: CPU gov  (ondemand)
20201216 121757 worker: USB boot enabled
20201216 121757 worker: File system expanded
20201216 121757 worker: HDMI port on

and

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 8/8
...

Confirming, the Pi HDMI does not appear in the Output Device pulldown list in MPD Config.

Turning off the HDMI port, rebooting, turning the HDMI port back on, and rebooting did not change the situation.

OTOH, I'm running moOde r6.7.1 on another Pi-3B+ with an actual HDMI device attached (a 3.5in LCD display). Same snippets:

Code:
20201214 112406 worker: Device raw: (0:b1|1:Headphones|2:empty|3:empty
20201214 112406 worker: Device i2s: (none)
20201214 112406 worker: Device mpd: (1:Pi Headphone jack)
20201214 112406 worker: Device ses: (1|Pi Headphone jack|Headphone|0%)
20201214 112406 worker: ALSA Headphone volume set to (0%)
20201214 112406 worker: -- System
20201214 112408 worker: Host     (moode671)
20201214 112408 worker: moOde    (6.7.1 2020-07-22)
20201214 112408 worker: RaspiOS  (10.6)
20201214 112408 worker: Kernel   (5.4.79-v7+ #1373)
20201214 112408 worker: Platform (Pi-3B+ 1GB v1.3)
20201214 112408 worker: ARM arch (armv7l, 32-bit kernel)
20201214 112408 worker: MPD ver  (0.21.24)
20201214 112408 worker: CPU gov  (ondemand)
20201214 112408 worker: USB boot enabled
20201214 112408 worker: File system expanded
20201214 112409 worker: HDMI port on

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
 Subdevices: 4/4
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
 Subdevices: 3/4
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3

and of course the PI HDMI output device shows up in MPD Config.

I see only one difference in the /boot/config.txt files.

- hdmi_group=0 in the player not offering the Pi HDMI device
- hdmi_group=1 in the player which does

However, on yet another RPi3A+ player running the testing version of moode-r7.0.0 with no local display, the Pi HDMI output device is offered in MPD Config. In its /boot/config.txt file, hdmi_group=0 so this seems a red herring, which by all rights it should be.

Regards,
Kent
Reply
I guess I have it. Seems to be an issue with the power. Since the Official 7" Display is mounted to the Raspi, I have two USB plugs for power. It is recommended to use the display`s power plug and I obviously used the other one directly on the Raspi. With the said strange effects. When using the recommended power plug the system will not boot at all: The wellknown "colorful" screen appears. Seenms that the new SSD draws too much current in combination with the touch display.

Will try again with powered USB hub or stronger power adapter. Both I currently do not have at hand, but will come back later.

Kent: Perhaps it is worthwhile to check which power plugs you use on your raspis w/o Official 7" Display...

Thanks for your thoughts and ideas - eventually these pushed me in the right direction  Blush
Regards
Jörg
Reply
@Kikaha 

Ah, additional components. In addition to the SSD perhaps the HDMI connection is drawing current too but I have no knowledge of the electronic circuitry involved in an HDMI connection.

Certainly adequate power is needed but in my case I have a 3A supply feeding both the RPi and the Official Display through their individual power inputs using a USB power-splitter cable. I see no problems that I can associate with poor power. For example, the display shows the traditional 4 strawberry icons, one for each CPI, and no lightning bolt icon warning of an undervoltage condition. There are no power-associated warnings in the dmesg output.

I don't think we've ruled out the possibility that there is an unresolved configuration issue here.

...und Schöne Feiertage!

Regards,
Kent
Reply
I got same results with my Pi-Touch rig on 671 and upcoming 700. It looks like the attached Pi Touch results in the HDMI port being disabled. It might be different on a Pi-4 that has 2 HDMI ports ?
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply


Forum Jump: