[wdmaudiodev] Re: Windows 7 (only) WASAPI Exclusive Issue/Bug

  • From: "Matthew van Eerde" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "Matthew.van.Eerde" for DMARC)
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Mon, 30 Oct 2017 17:52:56 +0000

If you would like help with a Windows issue on versions prior to Windows 10, 
please contact Microsoft Support - https://support.microsoft.com/

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on 
behalf of HpW-Works Support <support@xxxxxxxxxxxxx>
Sent: Monday, October 30, 2017 10:50:28 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Windows 7 (only) WASAPI Exclusive Issue/Bug


Hi Matthew

Have this issue only on Win 7

. Lynx
. NVIDIA
. Reathek

But not on Win 10 using the equal Lynx driver, what me puzzles. This means 
within Win 7, since a while something is broken.

Will this be fixed on Win 7??

Best Regards
Hp. Widmer

HpW-Works Support

Mailto:support@xxxxxxxxxxxxx
Website:http://www.hpw-works.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hpw-works.com&data=02%7C01%7CMatthew.van.Eerde%40microsoft.com%7C4df8dc21f70b4b297fd008d51fbebcd6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636449826472476816&sdata=eE4rxSMQuFGdi%2Fm%2F%2FjyI%2F0gLfwnt1wHRaXp%2FFM7VOhY%3D&reserved=0>

Am 30. Oktober 2017 15:57:39 schrieb "Matthew van Eerde" 
<dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "Matthew.van.Eerde" for DMARC):
0x8007007a is HRESULT_FROM_WIN32(ERROR_INSUFFICIENT_BUFFER). It is likely that 
the driver is returning a failing NTSTATUS code from KsCreatePin which is being 
mapped to ERROR_INSUFFICIENT_BUFFER.

If you can get this to repro on Windows 10, please file a problem report in 
Feedback Hub with Audio Glitches tracing.
https://blogs.msdn.microsoft.com/matthew_van_eerde/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblogs.msdn.microsoft.com%2Fmatthew_van_eerde%2F2016%2F09%2F26%2Freport-problems-with-logs-and-suggest-features-with-the-feedback-hub%2F&data=02%7C01%7CMatthew.van.Eerde%40microsoft.com%7C4df8dc21f70b4b297fd008d51fbebcd6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636449826472633068&sdata=IcQDpiacP4hJH%2Fmh6to0hD8mnwaIhQZcXRcdHaPFDaE%3D&reserved=0>

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on 
behalf of Support HpW-Works.com <support@xxxxxxxxxxxxx>
Sent: Monday, October 30, 2017 3:52:14 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Windows 7 (only) WASAPI Exclusive Issue/Bug


On 19. Oct I reported issues on Win 7 & WASAPI Exclusive and do not have any 
lights on this issue/bug!

I tested with the given “Play-Exclusive” CPP example given form Matthew van 
Eerde with equal failed/buggy driver initialize result.

Test 1 fails:

play-exclusive.exe --device "Speakers (Lynx L22)" --file 4khz.wav
Opening .wav file "4khz.wav"...
The default period for this device is 30000 hundred-nanoseconds, or 132 frames.
IAudioClient::Initialize failed: hr = 0x8007007a
Thread returned failing HRESULT 0x8007007a

Test 2 with different HW/Driver works:

play-exclusive.exe --device "Speakers (RME Babyface)" --file 4khz.wav
Opening .wav file "4khz.wav"...
The default period for this device is 30000 hundred-nanoseconds, or 132 frames.
We ended up with a period of 29932 hns or 132 frames.
Successfully played all 44100 frames.

Any help on this … 😃

Best Regards
Hp. Widmer

HpW-Works Support

Mailto:support@xxxxxxxxxxxxx
Website: 
http://www.hpw-works.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hpw-works.com&data=02%7C01%7CMatthew.van.Eerde%40microsoft.com%7C0c7bc984a43e411cd65908d51f846a34%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636449575968183692&sdata=i8nb6rPrz5wDmLBbewnGqP%2FpaEvKza56aajr%2BU816u4%3D&reserved=0>


From: wdmaudiodev-bounce@xxxxxxxxxxxxx 
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Support HpW-Works.com
Sent: Donnerstag, 19. Oktober 2017 10:21
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Windows 7 (only) WASAPI Exclusive Issues


Well,

Have some issues on Windows 7 / 64 bit and may get here some light on this 
WASAPI issues:


  1.  Using a Lynx L22 PCI Card and latest drivers (also older drivers 
releases): on WASAPI initialization I get an Error x8007007A, what is not 
presented/listed on MS/WSAPAI initialize :

[cid:part1833.15f6e67f6a0.27af.9775a7808f3a7b7bf6cdb99725615b12@hpw-works.com]
The used sample size/hhns is always hold below the 500ms level…

BTW: No issue on Win10 & Win10 Creator update!!
  2.  I use on the Exclusive Events an 1 second timeout timer to control the 
message flow.
NOW using the RME ADI-2 Pro, the first event is given/fired approx. after 1.2 
.. 1.5 seconds … Follow on events (after the first event) are always within the 
1 second timeout.

The question rises is this a normal behavior on Win 7, while on Win 10 this has 
not be seen yet. This would mean, the first event timeout should be somewhat 
larger than the follow-on.


Best Regards
Hp. Widmer

HpW-Works Support

Mailto:support@xxxxxxxxxxxxx
Website: 
http://www.hpw-works.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hpw-works.com&data=02%7C01%7CMatthew.van.Eerde%40microsoft.com%7C0c7bc984a43e411cd65908d51f846a34%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636449575968183692&sdata=i8nb6rPrz5wDmLBbewnGqP%2FpaEvKza56aajr%2BU816u4%3D&reserved=0>

PNG image

Other related posts: