[jogal]

Video driver is the same:
https://www.intel.com/content/www/us/en/...8i7be.html

Although I am currently using Windows 11 and Kodi v20 alpha for every day use (at specific times I have also tested v19.3 to look for regressions and everything has gone well).

Network LAN drivers and MEI driver updated to latest Intel generic.
Wifi disabled from bios.

advancedsettings:

xml:
<advancedsettings version="1.0">

  <scanirserver>false</scanirserver>

</advancedsettings>

[Antilis]

Hi, It happens to me exactly the same as to SakuraKira, I have the Wasapi configured correctly in windows, the reproduction sometimes starts well, but sometimes not, others start without sound and soon the image is blocked, I use Wasapi and passtrough, the error that I see in the log it is "CAESinkWASAPI :: InitializeExclusive: Failed to initialize WASAPI in exclusive mode", and it is in exclusive mode.

My log in case someone who controls more than me can help us:

Mi Log

i use windows 10

Thank you.

[Antilis]

I forgot, it only happens to me in Wasapi, in DirectSound it works fine.

Thanks.

[PatK]

only happens to me in Wasapi, in DirectSound it works fine.

In that statement we have success, bludgeoning hardware into something it doesn't do with software seems futile.

[b1ggles]

only happens to me in Wasapi, in DirectSound it works fine.

In that statement we have success, bludgeoning hardware into something it doesn't do with software seems futile.

So are you saying Kodi is not a home cinema solution anymore, just useful for pirated media with low quality sound. WASAPI worked perfectly in every past version?

[PatK]

So are you saying Kodi is not a home cinema solution anymore, just useful for pirated media

Did I say that? I don't believe I said anything about piracy nor suggested direct sound was inferior. Follow along Windows audio (wiki) wasapi revolves around handshaking, and if all devices are not operational at launch, Kodi will default to direct sound as it doesn't see the correct handshake, ditto for shutdown; should the wasapi bridge be shut down, the default (direct sound) next launch will take place. I don't see your assumption that there is a degradation of the sound quality without wasapi. A few links that may help you out. https://forum.kodi.tv/showthread.php?tid=324931 and https://forum.kodi.tv/showthread.php?tid=331538

https://en.wikipedia.org/wiki/Technical_...chitecture

[Deam]

So are you saying Kodi is not a home cinema solution anymore, just useful for pirated media

Did I say that? I don't believe I said anything about piracy nor suggested direct sound was inferior. Follow along Windows audio (wiki) wasapi revolves around handshaking, and if all devices are not operational at launch, Kodi will default to direct sound as it doesn't see the correct handshake, ditto for shutdown; should the wasapi bridge be shut down, the default (direct sound) next launch will take place. I don't see your assumption that there is a degradation of the sound quality without wasapi. A few links that may help you out. https://forum.kodi.tv/showthread.php?tid=324931 and https://forum.kodi.tv/showthread.php?tid=331538

https://en.wikipedia.org/wiki/Technical_...chitecture

Can I ask though what you did mean by saying: "In that statement we have success, bludgeoning hardware into something it doesn't do with software seems futile"?

Wasapi is a requirement for Atmos passthrough, regardless of whether Direct Sound or Wasapi otherwise performs the same, so the requirement to use Wasapi may not really be a choice (hence the poster's reference to home theatre).  Sure they may have went a little far in suggesting the quality was worse.

Also, the way you phrased your comment made it seem like the hardware in question never worked or was not meant to work with Wasapi.  Except it seems that it was working for that user (and others, including myself).  

I'd just like a better understanding to the extent this is an issue that does have a solution.

[PatK]

what you did mean by saying: "In that statement we have success

It means you were successful, and Kodi is running in that mode. If wasapi can't be realized, then the suspect might be hardware and no amount of setting changes would change that.  Wasapi is the protocol to hand off audio to another device (if capable) and in this case it appears to be hit or miss and may be dependant on the information I left in post #52

the way you phrased your comment made it seem like the hardware in question never worked or

Reading back through the 50 odd posts to address issues, isn't appetizing considering there are many  pile on 'me-too' posts that may or may-not pertain to this issue or perhaps missed a few basic assumptions, so I try to infer all possible that I can think of within time constraints. The thread is owned by user 'SakuraKira'

few more links via the forum search re:  Atmos https://forum.kodi.tv/showthread.php?tid=319124 and https://forum.kodi.tv/showthread.php?tid=327207

[b1ggles]

Direct Sound doesn't passthrough HD Audio so totally useless for home cinema, my analogy regarding piracy was just highlighting the poor quality media a lot of pirates push out for which Direct Sound would be actually suitable and your implication Kodi is now only really meant to play low quality media.

[black_eagle]

your implication Kodi is now only really meant to play low quality media.

That's rubbish!  Kodi is perfectly capable of playing high quality media, both video and audio.  To do this though, it needs a platform that is capable of handling said high quality media - eg, Kodi can't play 10bit HEVC files with hardware decoding on my Linux setup, but it can on Windows (with the same hardware).

If you have an issue, please post a debug log (wiki) that captures it.  Simply saying X doesn't work, or Kodi can't do Y is not helpful - it just means that you have an issue with something and as there are a million variables to consider, it's impossible to say if your specific issue is the same (or even similar) to someone else's without a debug log (wiki) showing some specifics about your setup (and indeed, theirs).

Basically, however much you might want to rant and rave, complain that this or that isn't working, without a debug log (wiki), absolutely nothing will be done about it.

If WASAPI isn't working for you, then lets see a debug log (wiki) showing that and maybe someone then will be able to either offer you a solution, or make changes to the code or tell you that your hardware is at fault...... or something.  Without that log though, no-one here actually knows anything and no dev is going to jump in and alter code based on the report of one user who has an issue, versus hundreds of thousands who don't.  If you want us to help you, you need to help us to do so.

[jogal]

Here a Matrix test build that try/may fix these kind of issues (untested):
https://mirrors.kodi.tv/test-builds/wind...ix-x64.exe


Updated test build here: https://forum.kodi.tv/showthread.php?tid=366453

[Deam]

Here a Matrix test build that try/may fix these kind of issues (untested):
https://mirrors.kodi.tv/test-builds/wind...ix-x64.exe


Updated test build here: https://forum.kodi.tv/showthread.php?tid=366453

@jogal - thank you for your continued efforts, even when things can get prickly...and you are working for free.  To the extent it means anything, it is appreciated.

[iradrian]

I  think I have found a solution to this based on recommendations from @jogal  - thank you!

I have a NUC8i3BEK, installed fresh Windows 10 and fresh naked Kodi 19.4 Matrix and had the same problems OP described.

I have completed the following steps which seemingly resolved it (tried to switch back and forth between 4K HDR videos like 30 times, still no error):

1. I'm pretty sure this alone solves it: updated HDMI firmware - this one is tricky as it is hard (or impossible?) to find through normal support download pages, I had to specifically search for it. Guess what? This actually solves audio related HDMI issues: https://www.intel.com/content/www/us/en/...-kits.html
   
2. Disabled Wifi in BIOS
   
3. Updated to latest generic MEI driver
   

[jbinkley60]

I  think I have found a solution to this based on recommendations from @[b]jogal  [/b]- thank you!

I have a NUC8i3BEK, installed fresh Windows 10 and fresh naked Kodi 19.4 Matrix and had the same problems OP described.

I have completed the following steps which seemingly resolved it (tried to switch back and forth between 4K HDR videos like 30 times, still no error):

1. I'm pretty sure this alone solves it: updated HDMI firmware - this one is tricky as it is hard (or impossible?) to find through normal support download pages, I had to specifically search for it. Guess what? This actually solves audio related HDMI issues: https://www.intel.com/content/www/us/en/...-kits.html
   
   
2. Disabled Wifi in BIOS
   
   
3. Updated to latest generic MEI driver
   

I am running the Intel 1.78.4.0.4 HDMI firmware on my Intel NUC 8i7BEH with Kodi 19.4 and no similar issues of flickering or no sound.  I believe I was having issues like this on an earlier version of Intel NUC firmware.


Jeff

[SakuraKira]

I am trying new firmware. For anyone wondering, it seems the NUC8i BN Firmware is also suitable for the 7th gen NUC (BN Series)
So I am wondering if there are newer Versions possible than 1.78.4.0.4 on 8th gen (maybe the one from Nuc10 works?) Will try out later