[PROBLEM] HDMI is problematic...

[jestersq5]

Hi,

Using a Pi 4B, connecting HDMI0 to Marantz AV7005 (it does not have a USB port that can work for streaming).  Here are the issues I'm having....

I need to have Moode fully booted before turning on the Receiver or the Receiver will not show video or play audio.
Sometimes the video works.
Sometimes the audio works.
Once they both worked.

I tried adding to the config.txt file... 

Code:

hdmi_force_hotplug=1

... but it did not become any more or less stable.  Any other thoughts?

[Tim Curtis]

There is very little information in your post, basically "it doesn't work".

Start by rebooting and then posting the Moode log.

Code:

moodeutl -l

[jestersq5]

There is very little information in your post, basically "it doesn't work".

Start by rebooting and then posting the Moode log.

Code:

moodeutl -l

Here is the log.  I'm VERY new to this, sorry, and I see there was another similar thread, my appologies.  

pi@moode:~ $ moodeutl -l
20200506 194821 worker: -- Start
20200506 194821 worker: Successfully daemonized
20200506 194821 worker: Integrity check (passed)
20200506 194821 worker: Session loaded
20200506 194821 worker: Debug logging (off)
20200506 194821 worker: Device raw: (0:ALSA|1:empty|i2s:none)
20200506 194821 worker: Device cfg: (On-board audio device|0|0|PCM|0)
20200506 194821 worker: ALSA volume set to (0%)
20200506 194821 worker: -- System
20200506 194822 worker: Host     (moode)
20200506 194822 worker: moOde    (6.5.2 2020-05-03)
20200506 194822 worker: Raspbian (10.3)
20200506 194822 worker: Kernel   (4.19.115-v7l+ #1305)
20200506 194822 worker: Platform (Pi-4B 2GB v1.1)
20200506 194822 worker: ARM arch (armv7l, 32-bit kernel)
20200506 194822 worker: MPD ver  (0.21.22)
20200506 194822 worker: CPU gov  (ondemand)
20200506 194822 worker: USB boot not available
20200506 194822 worker: File system not expanded yet
20200506 194822 worker: HDMI port on
20200506 194823 worker: File check (OK)
20200506 194823 worker: -- Network
20200506 194823 worker: eth0 exists
20200506 194823 worker: eth0 wait 0 for IP address
20200506 194826 worker: eth0 wait 1 for IP address
20200506 194829 worker: eth0 wait 2 for IP address
20200506 194833 worker: eth0 wait 3 for IP address
20200506 194836 worker: eth0 wait 4 for IP address
20200506 194851 worker: eth0 address not assigned
20200506 194851 worker: wlan0 exists
20200506 194851 worker: wifi country (US)
20200506 194851 worker: wlan0 trying SSID (JETS)
20200506 194851 worker: IP addr (192.168.1.39)
20200506 194851 worker: Netmask (255.255.255.0)
20200506 194851 worker: Gateway (192.168.1.1)
20200506 194851 worker: Pri DNS (192.168.1.1)
20200506 194851 worker: Domain  (None)
20200506 194851 worker: -- Audio
20200506 194851 worker: ALSA outputs unmuted
20200506 194851 worker: ALSA card number (0)
20200506 194851 worker: Audio output (On-board audio device)
20200506 194851 worker: Audio formats (U8, S16_LE)
20200506 194852 worker: ALSA mixer name (PCM)
20200506 194852 worker: MPD volume control (software)
20200506 194852 worker: Hdwr volume controller exists
20200506 194852 worker: Max ALSA volume (100%)
20200506 194852 worker: Reset renderer active flags
20200506 194852 worker: -- MPD
20200506 194852 worker: MPD conf updated
20200506 194852 worker: MPD started
20200506 194853 worker: MPD accepting connections
20200506 194853 worker: Configure MPD outputs
20200506 194853 worker: MPD output 1 ALSA default (on)
20200506 194853 worker: MPD output 2 ALSA crossfeed (off)
20200506 194853 worker: MPD output 3 ALSA parametric eq (off)
20200506 194853 worker: MPD output 4 ALSA graphic eq (off)
20200506 194853 worker: MPD output 5 ALSA polarity inversion (off)
20200506 194853 worker: MPD output 6 ALSA bluetooth (off)
20200506 194853 worker: MPD output 7 HTTP stream (off)
20200506 194853 worker: MPD crossfade (off)
20200506 194853 worker: -- Feature availability
20200506 194853 worker: Source select (available)
20200506 194853 worker: Source select (source: MPD)
20200506 194853 worker: Source select (output: On-board audio device)
20200506 194853 worker: Bluetooth (available)
20200506 194853 worker: Airplay renderer (available)
20200506 194853 worker: Airplay renderer (started)
20200506 194853 worker: Spotify renderer (available)
20200506 194853 worker: Spotify renderer (started)
20200506 194853 worker: Squeezelite renderer (available)
20200506 194853 worker: UPnP renderer (available)
20200506 194853 worker: DLNA server (available)
20200506 194853 worker: UPnP browser (available)
20200506 194853 worker: Audio scrobbler (available)
20200506 194853 worker: GPIO button handler (available)
20200506 194853 worker: -- Music sources
20200506 194853 worker: USB sources (none attached)
20200506 194853 worker: NAS and UPnP sources (none configured)
20200506 194853 worker: -- Miscellaneous
20200506 194853 worker: USB volume knob (Off)
20200506 194853 worker: USB auto-mounter (udisks-glue)
20200506 194853 worker: LED0 (On)
20200506 194853 worker: LED1 (On)
20200506 194853 worker: Saved MPD vol level (0)
20200506 194853 worker: Preamp volume level (0)
20200506 194853 worker: MPD volume level (91) restored
20200506 194853 worker: ALSA volume level (100%)
20200506 194853 worker: Auto-play (Off)
20200506 194853 worker: LocalUI started
20200506 194853 worker: Maintenance interval (3 hrs)
20200506 194853 worker: Screen saver activation (Never)
20200506 194854 worker: Session permissions (OK)
20200506 194854 worker: Watchdog started
20200506 194854 worker: Ready


I have just edited the config.txt to ensure that they have the following...

hdmi_force_edid_audio=1
hdmi_drive=2
hdmi_force_hotplug=1
config_hdmi_boost=5

I'll test it and report back.

[Tim Curtis]

Thx, nothing suspicious in the log.

[Tim Curtis]

Does your AVR have S/PDIF input?

[jestersq5]

Does your AVR have S/PDIF input?

It does, but I don't have a HAT for the pi at this point.  Wanted to get a feel to see if this was all worth it vs Airplay.  It may be.  Airplay on the receiver (which I think I bought maybe 10+ years ago) limits the EQ/Tone/Subwoofer settings, so I thought I'd get a feel for all of this using HDMI first.  I'll work on it a bit more tomorrow.

[TheOldPresbyope]

@jestersq5

Just out of curiosity, does your Marantz HDMI input work with any other device's HDMI output?

The config.txt options you cite sound right but you probably should be asking about them on the RaspberryPi Forums where the Raspbian/RaspberryPi gurus hang out.

Regards,
Kent

[DRONE7]

This may or may not be relevant..
I have an HDMI monitor that failed the edid most times (like your 'works occasionally') and I tried all the recommended RPI settings for HDMI without success.
Then discovered that the monitor (substitute your AVR) had an extremely fast time-out on start-up...
If I started the monitor before the Pi and was too slow starting the Pi then the monitor timed out and the Pi could not find it...
If I started the Pi first then by the time the monitor booted the Pi had found no suitable device and that was that...

Finally, having twigged to the timing, I was able to start both and have the Pi detect the monitor correctly.... Once I found the sequence I am able to boot both consistently..

No idea (blind venison ?) if this is your problem but in the absence of other fixes I thought to post my experience...as usual...ymmv and i may be way off beam...
Cheers,
Bob

[Pieter]

You could shave off a few seconds of the pi boot time by not having it wait for an Ethernet connection.

[Evotz]

This may or may not be relevant..
I have an HDMI monitor that failed the edid most times (like your 'works occasionally') and I tried all the recommended RPI settings for HDMI without success.
Then discovered that the monitor (substitute your AVR) had an extremely fast time-out on start-up...
If I started the monitor before the Pi and was too slow starting the Pi then the monitor timed out and the Pi could not find it...
If I started the Pi first then by the time the monitor booted the Pi had found no suitable device and that was that...

Finally, having twigged to the timing, I was able to start both and have the Pi detect the monitor correctly.... Once I found the sequence I am able to boot both consistently..

No idea (blind venison ?) if this is your problem but in the absence of other fixes I thought to post my experience...as usual...ymmv and i may be way off beam...
Cheers,
Bob

I admit, I'm relatively new to moOde, and I ran into the same problem as you with the HDMI/monitor power-up timing issue.  I searched this support forum and it seems like people who are using the HDMI for output are in the minority, so discussions related to HDMI was very few and uneventful.  I have a Pi 3B+ configured to only use HDMI audio.  I only turn on the monitor to do maintenance (i.e. updates etc) or when I want to search my collection on a bigger display (I am presbyopic).

Nevertheless, for my setup, to get the audio and video output from the HDMI working flawlessly without conforming to the critical timing or performing any rituals, I have these lines in my config.txt

hdmi_force_hotplug=1
hdmi_force_edid_audio=1
hdmi_drive=2
hdmi_group=1
hdmi_mode=16
hdmi_blanking=1

And for good measure, I have also disabled HDMI display off timer within moOde configuration.  Maybe if there's enough requests for these additional HDMI "features" (and do ask nicely), Tim can implement these hard-coding options within moOde configuration. 

Hopefully the information above contributed to our community.

Best,

EVO