And here's Ghost Recon: Advanced Warfighter 2. This is with the "Extreme" audio quality preset, which is exclusive to X-Fi cards, as shown here.

In this screenshot, taken during the very first mission, it's using 127-2=125 simultaneous hardware voices! This is the most I've seen in any game that I've tested so far. And all that with just 7ms of latency. Incredible!

Just to confirm, you are using the Daniel K driver pack for Windows 7?

DrLucienSanchez wrote on Yesterday, 14:13:

Just to confirm, you are using the Daniel K driver pack for Windows 7?

Yes.

I'm using DanielK's latest X-Fi support pack under both Win7 and Win10. The only place where I don't use it is under WinXP.

I also wanted to check if games which utilize EAX via DirectSound3D could be tested when using Creative's ALchemy under Win7, and it looks like they can! Here's a screenshot from Halo: Combat Evolved, a game which is officially supported by ALchemy. For the record, this is the retail CD version + latest official patch. No mods or fan made fixes of any kind have been applied.

It's using 127-65=62 simultaneous hardware voices, so pretty much as expected of an EAX 3.0 game. Nice that Falcosoft's OpenAL Test tool can monitor this as well.

Joseph_Joestar wrote on Yesterday, 18:02:

I also wanted to check if games which utilize EAX via DirectSound3D could be tested when using Creative's ALchemy under Win7, and it looks like they can! Here's a screenshot from Halo: Combat Evolved, a game which is officially supported by ALchemy. For the record, this is the retail CD version + latest official patch. No mods or fan made fixes of any kind have been applied.

The attachment HaloCE_Test01.jpg is no longer available

It's using 127-65=62 simultaneous hardware voices, so pretty much as expected of an EAX 3.0 game. Nice that Falcosoft's OpenAL Test tool can monitor this as well.

Hi,
1. I have noticed on your screenshots that on your X-Fi the busy loop takes more time than on my Audigy 1 and Aidigy 2 ZS. So I have made some optimizations.
Namely instead of trying to allocate buffers/sources one by one version 1.5 uses the 'binary search' pattern so first it tries to allocate 128 buffers then 64, 32, 16, 8, 4, 2, 1. This way instead of 127 calls (as the worst case on X-Fi) it uses only maximum 8 calls. On Audigy 1 and Aidigy 2 ZS this new algorithm is about 1 ms faster but on X-Fi maybe it matters more.
The best way to test this is to start monitoring with the previous version first without running other OpenAL programs and notice what the 'Query Time' field shows.
Then close the previous version, start the new one and make the same monitoring test.

2.Also added the ability to manually select the EAX reverb preset during the live audio playback test.

Falcosoft wrote on Yesterday, 19:56:

The best way to test this is to start monitoring with the previous version first without running other OpenAL programs and notice what the 'Query Time' field shows.
Then close the previous version, start the new one and make the same monitoring test.

Cheers! I just tested it, and the difference it pretty big on my X-Fi Titanium. It went from 27ms in version 1.4 to only 3ms in version 1.5. Nice work!