Hi again,
So, while I managed to get the HDMI audio working via the Intel Display Audio protocols late last night, I was too tired to run other tests (ie: receiver input switching, resuming from sleep / hibernation, etc.). I will test various things tonight and during the weekend, including possible handshake delay fixes.
For now, there are 5 caveats / notes I observed so far from last night:
1. Obvious 2-second handshake delay: This seems to be a rampant HDMI problem with various possible causes and solutions. Everything from hardware combinations to HDMI cable lengths to driver issues.
2. Stereo Only: Huge limitation for HTPC intentions. I couldn't see anywhere in the various control panels indicating that Intel Display Audio is capable of anything greater than 2 channels. HTPC software (ie: XBMC, MPC-HC, etc.) may be able to get around this limitation, but I haven't tested them yet.
3. Other HD Audio device: In my Device Manager, the other "High Definition Audio Device" (motherboard's native HD Audio engine?) remains installed without the yellow bang mark. I can select it in "Control Panel > Sound", but does not output sound via any testing method I mentioned in my previous post.
4. Suspicious cmd.exe: After updating the HD 4600 graphics adapter driver (before Intel Display Audio update), my AVG 2014 popped up a warning of suspicious activity regarding the cmd.exe file. Initially, I let AVG send this to the Virus Vault. However, knowing this is a critical file, I restored it and created an exception rule. I'll have to reboot in Safe Mode and then run a manual scan on cmd.exe to see if AVG still suspects something.
5. Intel Graphics System Tray icon: This last one is relatively minor, but despite disabling the system tray icon in Graphics Properties, the icon re-appears after every restart. The igfxTray.exe file that controls this is not listed in any Windows Startup folder or service that I've checked.
That's it for now. I'll post again as I find info that could be helpful to others. Likewise, please share your experiences and potential solutions.
Cheers,
RedEyeGuy.