KVR Audio

davidka · Post by **davidka** » Tue Jul 05, 2011 8:42 pm

Hey
Just downloaded Reaper 4 beta, and discovered this 'new' API. Seems like an unperfected gem to me. I'm on Win7 x64, so I used the 64bit version of R4 beta. I'm on an onboard Realtek soundcard, so I'm always looking for software improvements.

Aaltox64demo, sine patch
Asio4all, 96khz, buffer64, latency:5msec --> 8% CPU
WASAPI, 96khz, buffer64, latency: 3msec --> 6% CPU

Although I didn't do any intensive testing, therefore I won't make an universal statement, but I think WASAPI is a considerable new option for Win7 users. I think it is far from finished, so we should expect improvements. As far as I read, some people described that using WASAPI for a music player (ex. foobar2k) made their music sound a bit 'cleaner'.

Anyway, as it is a part of Windows, maybe it will allow the driver share in the future; eg. maybe we can watch youtube and listen to music, when using our DAW softwares.
So, I think I'm gonna keep using it when I fire up Reaper4, and keep reporting of new features/issues, as I can...

By that time, please share your experiences with WASAPI!

Cheers, David!

metamorphosis · Post by **metamorphosis** » Wed Jul 06, 2011 2:33 am

Some info on WASPAPI for everyone:
http://mark-dot-net.blogspot.com/2008/0 ... asapi.html

davidka · Post by **davidka** » Wed Jul 06, 2011 8:44 am

Thanks, that was a nice read!
I've tried 'shared' mode instead of exclusive, and it works! Despite it has a bit higher output latency (and I suppose only 16bits of depth), finally I can watch youtube, and listen to music, while I'm using my daw. Certainly, they need much more optimalization, but this is a huge step further! No need of workarounds!
And in exclusive mode, the performance and quality is slightly better than asio4all.
I think I'm going to stay with this new API for a while...

RunBeerRun · Post by **RunBeerRun** » Wed Jul 06, 2011 3:49 pm

Wow that's awesome so far, low latency, I guess the real test is how it handles over time and heavier cpu loads.

chokehold · Post by **chokehold** » Wed Jul 06, 2011 4:30 pm

Could this be more performant than manufacturer-developed ASIO drivers?
I'm not in performance trouble right now, but who knows, maybe I'll need to save some % of CPU sometime.

And what do I have to do to get this running? Is it integrated in Windows and programs have to support it (= install Reaper 4 and it works) or do I have to install some driver like with ASIO4All?

davidka · Post by **davidka** » Wed Jul 06, 2011 8:45 pm

It is embedded in Vista/Win7. You don't have to install anything new. It's just I only discovered this new api in Reaper4 beta. Maybe you can find extensions for your preferred software to support it.

Anyway, it seems stable, and perfectly suitable for guitar practising. I'll get my latest Synthmaster for some work, and test it more.

davidka · Post by **davidka** » Sun Jul 17, 2011 1:20 pm

bump
Still using WASAPI, without any specific problems...

RunBeerRun · Post by **RunBeerRun** » Mon Jul 18, 2011 1:52 am

I've tried it some, with only good results. I haven't recorded in the beta Reaper yet because I don't want to risk a crash.

RunBeerRun · Post by **RunBeerRun** » Tue Jul 19, 2011 11:39 pm

Ok there's no using Waspai with my M-Audio USB 1/4" input, so I'd have to use the computer's little built-in 1/8" thing.

Still good for MIDI though.

davidka · Post by **davidka** » Tue Jul 19, 2011 11:47 pm

Built-in audio stuff are much more noisy...

I'd say we should approach the WASAPI devs with a collected set of suggestions regarding compatibility and features. It'd be also great if the hardware manufacturers would appreciate this new API though...

C00kie · Post by **C00kie** » Wed Jul 20, 2011 9:49 am

davidka wrote:I'd say we should approach the WASAPI devs with a collected set of suggestions regarding compatibility and features. It'd be also great if the hardware manufacturers would appreciate this new API though...

Not to temper your outstanding enthousiasm, but I get the impression you don't have the faintest idea how development of stuff like this in Redmond really works, and the role of hardware manufacturers in the process...

davidka · Post by **davidka** » Wed Jul 20, 2011 2:20 pm

Well, how does it work?

C00kie · Post by **C00kie** » Wed Jul 20, 2011 3:56 pm

davidka wrote:Well, how does it work?

Your role is of the miserable end user, to use their inventions "as is" and be happy.

You can issue bug reports, but these will be never heard of again. You can issue requests for change (new or improved features) which go into the same black hole as bug reports.

Note: WASAPI was introduced several years ago with Vista. It remained basically unchanged afaik in Win7. Expect the same for next incarnations of Windows. Maybe WASAPI will be replaced by yet another driver model that is more sexy according to the geeky people in Redmond, but they won't change one bit in existing codebase if it can be avoided (hence the black hole mentioned before.)

robogone · Post by **robogone** » Wed Jul 20, 2011 4:07 pm

I tried it once. Made my nose feel like it's burning...

Stupid American Pig · Post by **Stupid American Pig** » Wed Jul 20, 2011 8:10 pm

Sonar has supported WASAPI since Version 8 I believe. I tried it then and found it to be ~the same as to slightly worse than ASIO with my Edirol UA-1000.

WASAPI. On Win7, it seems better than ASIO. Your thoughts and experiments?