Skip to main content

Topic: WASAPI plug-in version 3.0 beta [closed] (Read 133857 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • SoNic67
  • [*][*][*]
WASAPI plug-in version 3.0 beta [closed]
Reply #75
This beta 3.0 is working better with the VST plug-ins. More responsive but still "lock" the VST like it was happening sometimes before (pressing ctrl+alt+del to bring up the task manager will lock it).
Blue Cat FreqAnalyst x64...
DSD file play requires 49MB memory and 1-2% CPU (Core2Duo E7300).
  • Last Edit: 04 June, 2012, 06:18:15 PM by SoNic67

  • Jackal29a
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #76
beta 3 is working perfect with the Xonar ST!!! Not only I can finally play 88.2 and 176.4KHz, which wasn't possible with previous WASAPI versions, but also 32bit output works in either mode (push/pull), amazing job Peter. Did you do as Ceniza suggested and forced the otuput regardless of what the drvier reports?

32bit ouput is still a no go with the Musiland 02 and Foobar crashes and shuts down as soon as I hit play in either mode, but as it works with the Xonar I guess it is the Musiland drivers that don't want to play nice though it works in JRMC.

Thanks Peter, really appreciated.

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI plug-in version 3.0 beta [closed]
Reply #77
beta3 event-driven mode, it went wrong just like beta1 once been disturbed by another cpu-hog program and will not be able to recover.
Known, it is being looked into.
Quote
And the new beta3 event-driven mode is still not working well with the onboard sound-card of my laptop.
Event-driven mode apparently doesn't cooperate with lots of different hardware at all, there's no reason to use it if the other mode works for you.

32bit ouput is still a no go with the Musiland 02 and Foobar crashes and shuts down as soon as I hit play in either mode, but as it works with the Xonar I guess it is the Musiland drivers that don't want to play nice though it works in JRMC.
Do you get a "foobar2000 has crashed" dialog? I'm having trouble finding matching crash reports.

  • Jackal29a
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #78
Do you get a "foobar2000 has crashed" dialog? I'm having trouble finding matching crash reports.

Yes I do, here is the log (there is a dmp file too in the log folder):

Code: [Select]
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 01BB274Bh
Access violation, operation: read, address: 00000024h

Call path not available.

Code bytes (01BB274Bh):
01BB270Bh:  52 FF 50 0C 8B 4D D4 8B 01 FF 10 03 45 D8 D9 83
01BB271Bh:  90 00 00 00 51 D9 1C 24 50 8B 07 56 8B CF FF 10
01BB272Bh:  50 FF 15 74 51 BC 01 8D 75 E0 8D 83 B4 00 00 00
01BB273Bh:  E8 A0 0A 00 00 C6 45 FC 04 8B 08 83 C1 08 8B 01
01BB274Bh:  FF 50 24 8B 8B C0 00 00 00 03 4D E8 8B 75 E0 3B
01BB275Bh:  C8 1A C0 FE C0 88 45 0B 85 F6 74 08 E8 94 E8 FF
01BB276Bh:  FF 8A 45 0B 84 C0 74 30 8D 75 DC 8D 83 B4 00 00
01BB277Bh:  00 E8 5F 0A 00 00 8B 00 8D 8B B4 00 00 00 E8 90

Stack (0D84FC28h):
0D84FC08h:  02710C90 0D84FC58 0D84FCB4 01BB5682
0D84FC18h:  0B96CFEC 0D84FC94 01BB31EC 01BB2740
0D84FC28h:  02710D2C 02710C90 0B969708 00000000
0D84FC38h:  01BCB274 00000000 00000000 00000000
0D84FC48h:  00000000 00000000 00000000 00000000
0D84FC58h:  01BCB2C0 0B96CFE8 0000089D 02712DB8
0D84FC68h:  01BCB2A0 0B969B48 0000113A 0000113A
0D84FC78h:  0000AC44 00000002 00000003 01BCB2B0
0D84FC88h:  0D84FC68 00000000 77B7215C 0B96CFE8
0D84FC98h:  00000008 0000089D 00000000 0000089D
0D84FCA8h:  0D84FCCC 01BC4524 00000004 0D84FCD8
0D84FCB8h:  01BB292F 00000000 02710C94 75ED6A72
0D84FCC8h:  02710D2C 0D84FD0C 01BC43C7 00000000
0D84FCD8h:  0D84FD18 01BB23DD 00000000 00000000
0D84FCE8h:  0B969708 0D84FD68 77B5E115 000002A4
0D84FCF8h:  000002B0 77B96500 77B96536 00000000
0D84FD08h:  0B969708 0D84FD30 01BC455F 00000000
0D84FD18h:  0D84FD3C 01BB3A67 00000000 00000000
0D84FD28h:  0B969708 0D84FD20 0D84FD6C 01BC4354
0D84FD38h:  00000000 0D84FD44 01BB3A89 0D84FD7C

Registers:
EAX: 00000000, EBX: 02710C90, ECX: 0B96CFF0, EDX: 0B969B48
ESI: 0D84FC94, EDI: 0D84FC58, EBP: 0D84FCB4, ESP: 0D84FC28

Crash location:
Module: foo_out_wasapi
Offset: 274Bh

Loaded modules:
foobar2000                      loaded at 00A10000h - 00BC9000h
ntdll                            loaded at 77B40000h - 77C7C000h
kernel32                        loaded at 773B0000h - 77484000h
KERNELBASE                      loaded at 75ED0000h - 75F1A000h
COMCTL32                        loaded at 74C60000h - 74DFE000h
msvcrt                          loaded at 76DA0000h - 76E4C000h
GDI32                            loaded at 775F0000h - 7763E000h
USER32                          loaded at 774F0000h - 775B9000h
LPK                              loaded at 77C90000h - 77C9A000h
USP10                            loaded at 76F00000h - 76F9D000h
SHLWAPI                          loaded at 77490000h - 774E7000h
DSOUND                          loaded at 6CD60000h - 6CDD2000h
ADVAPI32                        loaded at 77CA0000h - 77D40000h
sechost                          loaded at 77D40000h - 77D59000h
RPCRT4                          loaded at 76E50000h - 76EF1000h
ole32                            loaded at 76FA0000h - 770FC000h
WINMM                            loaded at 72750000h - 72782000h
POWRPROF                        loaded at 74700000h - 74725000h
SETUPAPI                        loaded at 779A0000h - 77B3D000h
CFGMGR32                        loaded at 75D80000h - 75DA7000h
OLEAUT32                        loaded at 77720000h - 777AF000h
DEVOBJ                          loaded at 75F20000h - 75F32000h
UxTheme                          loaded at 74AE0000h - 74B20000h
SHELL32                          loaded at 75FF0000h - 76C3A000h
zlib1                            loaded at 5A4C0000h - 5A4D4000h
shared                          loaded at 6FB90000h - 6FBBB000h
imagehlp                        loaded at 775C0000h - 775EA000h
dbghelp                          loaded at 62DA0000h - 62E8B000h
COMDLG32                        loaded at 77100000h - 7717B000h
gdiplus                          loaded at 74950000h - 74AE0000h
Secur32                          loaded at 75A70000h - 75A78000h
SSPICLI                          loaded at 75BB0000h - 75BCB000h
CRYPT32                          loaded at 75DB0000h - 75ECD000h
MSASN1                          loaded at 75D40000h - 75D4C000h
WINHTTP                          loaded at 716E0000h - 71738000h
webio                            loaded at 71690000h - 716DF000h
IMM32                            loaded at 75FD0000h - 75FEF000h
MSCTF                            loaded at 777B0000h - 7787C000h
CRYPTBASE                        loaded at 75C20000h - 75C2C000h
foo_input_monkey                loaded at 10000000h - 10049000h
foo_dynamic_range                loaded at 008F0000h - 00958000h
foo_freedb2                      loaded at 69EB0000h - 69EF0000h
foo_dsp_xgeq                    loaded at 6FC60000h - 6FC9C000h
foo_rgscan                      loaded at 69E60000h - 69EAB000h
foo_dsp_std                      loaded at 69C80000h - 69CC8000h
foo_input_dvda                  loaded at 69C20000h - 69C7B000h
foo_input_sacd                  loaded at 69B70000h - 69C14000h
foo_ui_std                      loaded at 69A80000h - 69B65000h
MSIMG32                          loaded at 74240000h - 74245000h
foo_unpack                      loaded at 6FC30000h - 6FC5F000h
foo_fileops                      loaded at 69A30000h - 69A77000h
foo_out_asio                    loaded at 01AF0000h - 01B26000h
foo_abx                          loaded at 01B60000h - 01B92000h
foo_albumlist                    loaded at 699D0000h - 69A2C000h
foo_out_wasapi                  loaded at 01BB0000h - 01BD6000h
foo_converter                    loaded at 697F0000h - 6986C000h
foo_hdcd                        loaded at 68A80000h - 68AC3000h
foo_input_std                    loaded at 67510000h - 67670000h
foo_cdda                        loaded at 68A30000h - 68A7E000h
CLBCatQ                          loaded at 77690000h - 77713000h
sud                              loaded at 660B0000h - 6616B000h
ADVPACK                          loaded at 61340000h - 6136E000h
VERSION                          loaded at 751D0000h - 751D9000h
DUI70                            loaded at 74890000h - 74942000h
PROPSYS                          loaded at 74B20000h - 74C15000h
avrt                            loaded at 746C0000h - 746C7000h
MMDevApi                        loaded at 747D0000h - 74809000h
CRYPTSP                          loaded at 75730000h - 75746000h
rsaenh                          loaded at 754D0000h - 7550B000h
AUDIOSES                        loaded at 6F7D0000h - 6F806000h
audiokse                        loaded at 60E00000h - 60E72000h
WINTRUST                        loaded at 75D50000h - 75D7D000h
ksuser                          loaded at 6D2E0000h - 6D2E4000h
WindowsCodecs                    loaded at 745A0000h - 7469B000h
msxml3                          loaded at 67850000h - 67983000h
cmasiop                          loaded at 02620000h - 0266C000h

Stack dump analysis:
Address: 01BCB274h (foo_out_wasapi+1B274h), symbol: "foobar2000_get_interface" (+16554h)
Address: 01BCB2C0h (foo_out_wasapi+1B2C0h), symbol: "foobar2000_get_interface" (+165A0h)
Address: 01BCB2A0h (foo_out_wasapi+1B2A0h), symbol: "foobar2000_get_interface" (+16580h)
Address: 01BCB2B0h (foo_out_wasapi+1B2B0h), symbol: "foobar2000_get_interface" (+16590h)
Address: 77B7215Ch (ntdll+3215Ch), symbol: "EtwEventEnabled" (+D9h)
Address: 01BC4524h (foo_out_wasapi+14524h), symbol: "foobar2000_get_interface" (+F804h)
Address: 01BB292Fh (foo_out_wasapi+292Fh)
Address: 75ED6A72h (KERNELBASE+6A72h), symbol: "InterlockedCompareExchange" (+F8h)
Address: 01BC43C7h (foo_out_wasapi+143C7h), symbol: "foobar2000_get_interface" (+F6A7h)
Address: 01BB23DDh (foo_out_wasapi+23DDh)
Address: 77B5E115h (ntdll+1E115h), symbol: "RtlAddMandatoryAce" (+32Ch)
Address: 77B96500h (ntdll+56500h), symbol: "wcsnicmp" (+C74h)
Address: 77B96536h (ntdll+56536h), symbol: "wcsnicmp" (+CAAh)
Address: 01BC455Fh (foo_out_wasapi+1455Fh), symbol: "foobar2000_get_interface" (+F83Fh)
Address: 01BB3A67h (foo_out_wasapi+3A67h)
Address: 01BC4354h (foo_out_wasapi+14354h), symbol: "foobar2000_get_interface" (+F634h)
Address: 01BB3A89h (foo_out_wasapi+3A89h)
Address: 01BB7DA4h (foo_out_wasapi+7DA4h), symbol: "foobar2000_get_interface" (+3084h)
Address: 01BB8D40h (foo_out_wasapi+8D40h), symbol: "foobar2000_get_interface" (+4020h)
Address: 01BB7E2Eh (foo_out_wasapi+7E2Eh), symbol: "foobar2000_get_interface" (+310Eh)
Address: 773FED6Ch (kernel32+4ED6Ch), symbol: "BaseThreadInitThunk" (+12h)
Address: 77BA377Bh (ntdll+6377Bh), symbol: "RtlInitializeExceptionChain" (+EFh)
Address: 77410651h (kernel32+60651h), symbol: "UnhandledExceptionFilter" (+0h)
Address: 77410651h (kernel32+60651h), symbol: "UnhandledExceptionFilter" (+0h)
Address: 77B5E115h (ntdll+1E115h), symbol: "RtlAddMandatoryAce" (+32Ch)
Address: 77BA374Eh (ntdll+6374Eh), symbol: "RtlInitializeExceptionChain" (+C2h)
Address: 01BB7DCAh (foo_out_wasapi+7DCAh), symbol: "foobar2000_get_interface" (+30AAh)
Address: 01BB7DCAh (foo_out_wasapi+7DCAh), symbol: "foobar2000_get_interface" (+30AAh)
Address: 74616E72h (WindowsCodecs+76E72h), symbol: "WICConvertBitmapSource" (+BE06h)
Address: 74614420h (WindowsCodecs+74420h), symbol: "WICConvertBitmapSource" (+93B4h)
Address: 77772F2Fh (OLEAUT32+52F2Fh), symbol: "VarMonthName" (+B72h)
Address: 74642E30h (WindowsCodecs+A2E30h), symbol: "IWICColorContext_InitializeFromMemory_Proxy" (+1957h)
Address: 76207473h (SHELL32+217473h), symbol: "RunAsNewUser_RunDLLW" (+199Ah)
Address: 74657373h (WindowsCodecs+B7373h), symbol: "IWICColorContext_InitializeFromMemory_Proxy" (+15E9Ah)
Address: 76616C66h (SHELL32+626C66h), symbol: "StrStrW" (+27695Fh)
Address: 776C0000h (CLBCatQ+30000h), symbol: "OpenComponentLibraryOnMemEx" (+D83h)
Address: 76880000h (SHELL32+890000h), symbol: "StrStrW" (+4DFCF9h)
Address: 76860000h (SHELL32+870000h), symbol: "StrStrW" (+4BFCF9h)
Address: 74240000h (MSIMG32+0h)
Address: 74686769h (WindowsCodecs+E6769h), symbol: "IWICColorContext_InitializeFromMemory_Proxy" (+45290h)
Address: 74656C77h (WindowsCodecs+B6C77h), symbol: "IWICColorContext_InitializeFromMemory_Proxy" (+1579Eh)
Address: 00A26F00h (foobar2000+16F00h)
Address: 77772F2Fh (OLEAUT32+52F2Fh), symbol: "VarMonthName" (+B72h)
Address: 72756F6Ch (WINMM+6F6Ch), symbol: "CloseDriver" (+1AFh)
Address: 76000000h (SHELL32+10000h), symbol: "SHEnableServiceObject" (+1B27h)
Address: 008F0200h (foo_dynamic_range+200h)
Address: 0090008Bh (foo_dynamic_range+1008Bh)
Address: 00A4009Fh (foobar2000+3009Fh)
Address: 00AE00A9h (foobar2000+D00A9h)
Address: 00B700B2h (foobar2000+1600B2h)
Address: 01B101A9h (foo_out_asio+201A9h), symbol: "foobar2000_get_interface" (+15439h)

Environment:
App: foobar2000 v1.1.12a
UI: Default User Interface 0.9.5

Components:
Core (2012-05-26 22:31:52 UTC)
   foobar2000 core 1.1.12a
foo_abx.dll (2012-03-23 13:26:41 UTC)
   ABX Comparator 1.3.4
foo_albumlist.dll (2012-05-26 22:30:18 UTC)
   Album List 4.5
foo_cdda.dll (2012-05-26 22:30:02 UTC)
   CD Audio Decoder 3.0
foo_converter.dll (2012-05-26 22:29:44 UTC)
   Converter 1.5
foo_dsp_std.dll (2012-05-26 22:30:22 UTC)
   Standard DSP Array 1.0
foo_dsp_xgeq.dll (2012-05-06 23:32:08 UTC)
   Graphic Equalizer 0.3.7
foo_dynamic_range.dll (2012-03-23 13:22:33 UTC)
   Dynamic Range Meter 1.1.1
foo_fileops.dll (2012-05-26 22:28:54 UTC)
   File Operations 2.1.3
foo_freedb2.dll (2012-05-26 22:30:28 UTC)
   freedb Tagger 0.6.4
foo_hdcd.dll (2012-05-18 08:41:40 UTC)
   HDCD decoder 1.14
foo_input_dvda.dll (2012-03-23 13:22:46 UTC)
   DVD-Audio Decoder and Watermark Detector 0.4.11
foo_input_monkey.dll (2012-06-05 08:04:08 UTC)
   Monkey's Audio Decoder 2.1.6
foo_input_sacd.dll (2012-05-29 06:17:52 UTC)
   Super Audio CD Decoder 0.5.10
foo_input_std.dll (2012-05-26 22:29:50 UTC)
   Standard Input Array 1.0
foo_out_asio.dll (2012-03-31 06:27:28 UTC)
   ASIO support 1.2.7
foo_out_wasapi.dll (2012-06-05 06:31:55 UTC)
   WASAPI output support 3.0 beta 3
foo_rgscan.dll (2012-05-26 22:29:48 UTC)
   ReplayGain Scanner 2.1.2
foo_ui_std.dll (2012-05-26 22:30:12 UTC)
   Default User Interface 0.9.5
foo_unpack.dll (2012-05-26 22:29:16 UTC)
   ZIP/GZIP/RAR Reader 1.6

Machine specifications:
OS: Windows 6.1.7601 Service Pack 1 x86
CPU: Intel® Core™ i3-2100 CPU @ 3.10GHz, features: MMX SSE SSE2 SSE3 SSE4.1 SSE4.2
Audio: Altavoces (3- MUSILAND Monitor 02 US); Altavoces (ASUS Xonar Essence ST Audio Device)
  • Last Edit: 05 June, 2012, 05:28:29 AM by Peter

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI plug-in version 3.0 beta [closed]
Reply #79
Thanks for the log, but from now on please auto-submit your crash reports, it really makes my job easier this way. Any specific reason why you didn't auto-submit this one? (Or perhaps you did but it didn't come thru somehow?)

If you cannot or don't want to auto-submit the reports, please share the minidump file (using the uploads forum).
  • Last Edit: 05 June, 2012, 05:32:44 AM by Peter

  • Jackal29a
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #80
Thanks for the log, but from now on please auto-submit your crash reports, it really makes my job easier this way. Any specific reason why you didn't auto-submit this one? (Or perhaps you did but it didn't come thru somehow?)

If you cannot or don't want to auto-submit the reports, please share the minidump file (using the uploads forum).


sorry for that, I'm not getting the Foobar error message that allows to send the files but Windows' one (it crashes hard) so I¡ll have to upload manually next time.

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI plug-in version 3.0 beta [closed]
Reply #81
If you still have the .dmp file you got along with the log that you posted, please upload this dmp file for me to look into.

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI plug-in version 3.0 beta [closed]
Reply #82
Bug fixed, thank you for your patience.

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI plug-in version 3.0 beta [closed]
Reply #83
Beta 4 posted, see the initial post for details.

  • Jackal29a
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #84
Beta 4 posted, see the initial post for details.


You nailed it with Event Mode, it works fine now I can get 32bit at any sample rate with the Musiland as well.
Something still wrong in push mode but no biggie by me, case closed.

  • sld
  • [*][*][*][*][*]
WASAPI plug-in version 3.0 beta [closed]
Reply #85
This is working great!

On a Go-vibe USB DAC that only accepts 16-bit, 44.1 kHz,

event-driven mode works fine with the software buffer set at any value, with isolated stutters when the CPU (Yonah) is placed on high load. SpeedStep/FID/VID switching in RMClock.

The usual mode works at software buffer values >= 100 ms. The audio file permanently pauses when this setting is too low (90 ms or less) until it is adjusted higher again.
  • Last Edit: 05 June, 2012, 06:42:01 PM by sld

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI plug-in version 3.0 beta [closed]
Reply #86
It seems low buffer values in the regular ("push") mode are non-functional regardless of your hardware right now due to certain assumptions in the code, please don't use less than 200ms as there's really no point in doing so.

  • Jackal29a
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #87
It seems low buffer values in the regular ("push") mode are non-functional regardless of your hardware right now due to certain assumptions in the code, please don't use less than 200ms as there's really no point in doing so.


Again, you hit the bull's eye once more. I increased the buffer to 500ms a works perfect.
Funny how some hardware is able to go well beyond its original specs. Neither of my sound cards is supposed to be doing what they are in fact doing (and extremely well actually), no that there is any real audible advantage to it but it cerntainly proves a point, never fully trust manufacturer's specs.

  • SoNic67
  • [*][*][*]
WASAPI plug-in version 3.0 beta [closed]
Reply #88
Actually the manufacturer specs are correct. The "32 bit" mode is a useless one, Windows trims those 32 bit to whatever your card supports (24 bit probably) - by trowing-away extra bits.
WASAPI event.
  • Last Edit: 06 June, 2012, 06:29:21 AM by SoNic67

  • Jackal29a
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #89
Actually the manufacturer specs are correct. The "32 bit" mode is a useless one, Windows trims those 32 bit to whatever your card supports (24 bit probably) - by trowing-away extra bits.
WASAPI event.


I'm think you are mixing apples and oranges. In WASAPI mode Windows throws nothing away, if Fooabgr sends 32bit that is exactly what the soundcard will receive, it works, full stop if it didn't you'll get an error and no sound. The soundcards as a DEVICE DO indeed accept 32bit input which they truncate before sending to the DAC IC. One thing is the PCI/PCIe/USB receiver and another the DAC chip itself, the fromer can accept 32bit and the second may or may not (ESS9016/18, AKM4399, PCM1795, etc.). The Musiland accepts the 32bit and, if enabled, proceeses it using its DSP in 32 bit before down coverting  tp 24 bit for its PCM1793 24bit DAC.
Anyway, this is OT so lets stop it here.

  • off&on
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #90
* MMCSS use for hopefully better glitch prevention.
* Event driven mode now recovers correctly after a glitch caused by high CPU usage.

Magic explained
Enjoy.

What an understatement, Peter! just opened a HydrogenAudio account to thank you for beta 4: it's like having one's earwax removed.  While people argue that bits are bits, miniscule dropouts are dropouts -- and (unlucky?) some hear them all.

Many thanks!
----
Win7/32, antiquated Merom laptop, FiiO E10, event mode, magic!


WASAPI plug-in version 3.0 beta [closed]
Reply #91
Well done Peter, well done...

Beta 4 is perfect!
Tested now for 6 hours without glitches or something other wrong things.
Soundcard: Creative X-Fi USB 5.1 Surround -> PAX USB 2.25 driver...

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
WASAPI plug-in version 3.0 beta [closed]
Reply #92
What an understatement, Peter! just opened a HydrogenAudio account to thank you for beta 4: it's like having one's earwax removed.

Without adjusting the volume slider in foobar2000, WASAPI output will be a lot louder than DirectSound (at least on my machine), and increases in loudness were found to be equal with a higher perceived audio quality.
  • Last Edit: 06 June, 2012, 09:03:32 AM by Kohlrabi
It's only audiophile if it's inconvenient.

  • MordredKLB
  • [*][*][*]
WASAPI plug-in version 3.0 beta [closed]
Reply #93
He claims he was having audio dropouts, which would be completely different than just loudness differences, and far more annoying.

  • db1989
  • [*][*][*][*][*]
  • Global Moderator
WASAPI plug-in version 3.0 beta [closed]
Reply #94
Either that or it’s some alternative way to describe the alleged presence of jitter, something that is unlikely to have been an issue without WASAPI anyway, and something (else) that is not compliant with TOS #8 unless substantiated.

Kohlrabi made a very good point that might explain the perception (if it actually exists), although I hadn’t heard about WASAPI being louder by default: is this another benefit of modern Windows’ audio system?

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
WASAPI plug-in version 3.0 beta [closed]
Reply #95
Kohlrabi made a very good point that might explain the perception (if it actually exists), although I hadn’t heard about WASAPI being louder by default: is this another benefit of modern Windows’ audio system?

There is probably no difference in volume if you have set your output device to 100% in Windows Mixer, now that I think of it. Which I haven't done.
It's only audiophile if it's inconvenient.

  • MordredKLB
  • [*][*][*]
WASAPI plug-in version 3.0 beta [closed]
Reply #96
Yeah, I never noticed a volume discrepancy when I was forced to use WASAPI over DS for a few years. Kholrabi's observation was probably all a result of volume mixer differences.

  • off&on
  • [*]
WASAPI plug-in version 3.0 beta [closed]
Reply #97
Sorry I wasn't clear, and thanks to the kind souls who took care of that:
He claims he was having audio dropouts, which would be completely different than just loudness differences, and far more annoying.

Exactly: WASAPI sounds ~10dB louder than DS here, but who cares?
Either that or it’s some alternative way to describe the alleged presence of jitter, something that is unlikely to have been an issue without WASAPI anyway, and something (else) that is not compliant with TOS #8 unless substantiated.

Indeed, it used to sound like (aperiodic) jitter  as if coming from last sample in buffer "latched" on DAC till the next buffer starts to clock out or - more likely - a PLL "smoothing" / dropping sync on data stream interruption. "Alleged" is very appropriate in front of the J-word here, as I took no direct or indirect measurements.

And now, thanks to Peter, we don't need any

  • SoNic67
  • [*][*][*]
WASAPI plug-in version 3.0 beta [closed]
Reply #98
I'm think you are mixing apples and oranges. In WASAPI mode Windows throws nothing away, if Fooabgr sends 32bit that is exactly what the soundcard will receive, it works, full stop if it didn't you'll get an error and no sound. The soundcards as a DEVICE DO indeed accept 32bit input which they truncate before sending to the DAC IC. One thing is the PCI/PCIe/USB receiver and another the DAC chip itself, the fromer can accept 32bit and the second may or may not (ESS9016/18, AKM4399, PCM1795, etc.). The Musiland accepts the 32bit and, if enabled, proceeses it using its DSP in 32 bit before down coverting  tp 24 bit for its PCM1793 24bit DAC.
Anyway, this is OT so lets stop it here.

The DRIVER throws away the extra bits that DAC cannot use. You rely on driver to handle that "conversion" properly instead of feeding it the right signal... Musiland doesn't have any "32 bit DSP" like you stated:
http://www.musiland.com.cn/index.php/Product/show/id/137
"Monitor02 US sound card supports a maximum audio processing of 24Bit/192KHz and adopts D/A conversion chip with SNR and dynamic range as high as 113dB to provide HI-FI sound effect of analog output."
They know that they use PCM1793 that is only 24 bit capable.
But probably you think that the manufacturers of both DAC and sound card are stupid.
And no, is not OT, is related strictly of the 32 bit send to the cards that don't have the physical capabilities for that.

PS: My E-MU 1820m accepts the 32 bit, but I know that the whole hardware is a 24 bit pathway.
  • Last Edit: 06 June, 2012, 07:00:37 PM by SoNic67

WASAPI plug-in version 3.0 beta [closed]
Reply #99
Wow. Beta 4 event mode works really well with my HRT Music Streamer II USB DAC at almost any hardware buffer setting. The clicking glitches have been eliminated. After listening to music for a few hours I did notice a momentary pause in the music once in a while.
  • Last Edit: 06 June, 2012, 07:28:25 PM by jologsmaster