I don't believe this is a hardware issue.
We are able to get DD+ bitstreaming with WASAPI in XBMC. Also, users have reported DD+ Netflix working in Windows 8.0
Driver guys just need to step up and resolve this issue.
I am reiterating again - I am in the SF Bay Area, work close to Intel HQ. If anyone in Intel HQ is interested, I am ready to bring in my NUC system which is exhibiting this problem and get them more info. (That is how desperate I am to see this problem fixed - Such a waste that an awesome low power system fails at being a primary HTPC).
1 of 1 people found this helpful
It seems to be pointing to a hardware combination issue, but it's hard to point to exactly which piece of hardware. I've set up two different configurations:
NUC > Denon AV receiver > Asus HDMI monitor
We see the problem in Netflix.
Same NUC > same Denon AV receiver > Phillips HDTV
We DON'T see the problem in Netflix.
Not sure why the different monitor would make a difference. Several other receiver and display combinations also don't exhibit the problem. Our graphics debug team believes this to be a Netflix app problem, since Dolby 5.1 works just fine outside of Netflix.
Denon's support website says the latest firmware (which mine has) fixed a known problem with Netflix and Dolby. I've got calls into both Denon and Netflix about this now.
Thanks for following up. The 'Pioneer Elite VSX-32 + Sony KDL46EX720 TV' combination also exhibits this problem.
The issue can also be recreated with XBMC. So, I don't think this is a 'Netflix app' issue (though Netflix app could try to use WASAPI and work around the issue).
For recreating on XBMC / Windows 8.1, try bitstreaming DD+ from any local file when the Audio device is set to default (make sure Audio properties are set to bitstreaming for DD+ and all other HD audio codecs). You can see the stuttering. Once you set XBMC Audio Device to WASAPI mode, the problem goes away.If you want a 'local file' DD+ sample, let me know and I can provide a link to one.
If it is a Netflix problem, please explain why it DOES WORK using the Microsoft Audio driver instead of the Intel driver?
Also, this issue isn't isolated to Denon AVR's, my NAD AVR has the same issue.
This issue is taking way too long to fix, it is know since October last year.
It doesn't matter if Netflix or Intel is at fault, as long as it doesn't get fixed it looks bad for both.
It looks like you need to have a look why the Microsoft driver is working and yours is not.
My conjecture is that it is due to PAP (protected audio path) checks - Note that the Microsoft driver doesn't enable HD audio bitstreaming (DTS-HD / TrueHD) while the Intel one does.
On the whole, I also believe this is not a Denon receiver issue that is causing the problem and Intel might be looking at the wrong angle in having tickets open with Denon / Netflix (just my opinion). It is also not restricted to Netflix only (can be recreated with XBMC). Pure and simple, it is an Intel Display Audio Driver problem.
I have a Yamaha AVR, so it's definitely not specific to Denon
I can't remember where I read this as I've been reading quite a few threads related to the same issue. Someone had a theory that it was something to do with wrong refresh rate which the TV couldn't handle? Maybe that explains why the Asus monitor works whereas the TV doesn't
I have a Onyo receiver Philips HDTV removed the Intel graphics and install Microsoft's graphics driver. Still same problem with Netflix 5.1:
NUC Hasswell and Netflix app on Windows 8.1: NUC Hasswell and Netfli x app on Windows 8.1 - YouTube
Oboy, lucky me, find my AppleTV 2 under my bed and use it to Netflix. Not the simplest way but when Intel cant fix the problem...
Today I tried the Microsoft Xbox video app.
Playing some previews Dolby Digital + works just fine using this Windows 8.1 metro app.
Which leads me to conclude that the Intel driver is not the main issue.
Apparently the Netlfix app does not work well together with the Intel driver.
I have just spent an hour chatting with Netflix support to explain them everything I have tested.
I hope they will fix this now in cooperation with the tech guys from Intel.