01-05-2024, 08:23 PM
This problem occurs in any receiver mode (though only the pure/direct are of interest to me). Others have reported this problem/wish elsewhere (I cant remember where). I can find no setting for HDMI "no signal" behaviour - and I am not sure the receiver could meaningfully second-guess what is going to come next when the signal drops.
I think the solution would be below the MPD level. Like a plugin (term used loosely) in the ALSA framework that is always connected to the hdmi. For example something like plughw, but that keeps the output device fed/open even if nothing is coming in (generic solution), or add this feature to CamillaDSP output (less generic)? (NB I dont yet understand the ALSA architecture - Its on my big todo list!)
I think the solution would be below the MPD level. Like a plugin (term used loosely) in the ALSA framework that is always connected to the hdmi. For example something like plughw, but that keeps the output device fed/open even if nothing is coming in (generic solution), or add this feature to CamillaDSP output (less generic)? (NB I dont yet understand the ALSA architecture - Its on my big todo list!)
- Digital source, room EQ & 3-way x-over to HDMI (6 channels):
- Pi-4B 1.5 4GB, RaspiOS 11.8 Bullseye 64-bit, moOde 8.3.7 2023-12-07
- HDMI demux, DACs & Power Amps:
- Onkyo TX-SR875 or TX-NR905 in pure/direct mode
- Speakers:
- Linn Kaber Aktiv (currently tri-amped passive)
