NUCs require to detect a video device (powered on) on post process, otherwise they will not start up. It is necessary to turn your AVR on first them the NUC.
And this is my problem.
I boot the NUC very often alone (Denon AVR is powered off) and use the NUC with Remote Desktop for example.
But sometimes I use the NUC on my Denon AVR with my Panasonic TV. There I need the sound.
The fact to reboot the NUC to get sound is not comfortable due to the situationt that all open files/documents/programs... need bo be re-opend.
The very old Acer Reco 3610 had never ever this problem.
I think this is just a software issue. There is no chance to set the Denon HDMI AVAMP as default sound device.
Or do you have some software to fix this issue?
I had done some trials today.
Denon AVR is powered on -> NUC boot -> HDMI sound is working -> power off the Denon AVR -> Denon AVR is still visible in Windows Sound settings -> reboot NUC -> Denon AVR is still visible in Windows Sound settings after reboot and sound is working fine after I'm powered on the Denon AVR
Denon AVR is powered on -> NUC boot -> HDMI sound is working -> power off the Denon AVR -> Denon AVR is still visible in Windows Sound settings -> power off NUC -> power on NUC -> Denon AVR is not visible in Windows Sound settings and Denon AVR is not recognized after power on
What is the difference between reboot of the NUC and a power off/on?
So it looks like this issue is fixable by software, right?
Intel complies with the HDMI soft shut down cycle standard, as soon as you restart the NUC the HDMI link is kept so the NUC can recognize the AVR; however, when you shut down or power failure(hard shut down) the HDMI link is closed and NUC is not capable to recognize properly the AVR.
Thanks a lot Mike.
I understood now the differences between booting and power off/on and the HDMI link.
Again my question, sorry
Is this behauviour fixable by software driver? I guess so due to the fact my old Acer Revo 3610 with nVidia ION chipset could handle ths issue without any problem.