On 6/17/2010 11:29 AM, e-t172 wrote: > On 17/06/2010 20:15, Tim Roberts wrote: >> It's actually possible to install >> a GFX APO on your own, but you can't release such a thing unless you >> also supply the audio card driver. > > Why? The Microsoft philosophy is that APOs are an extension of the hardware, and hence should only be installed with the driver. This is all part of the "who's in charge" issue. They believe there should be nothing in the audio path that wasn't either installed by the hardware vendor or requested by an application. Whether I agree with it or not, I do understand the motivation. Perhaps the trickiest part of the GFX APO is installation. Normally, the name you assign to your APO becomes the name of the audio device in the control panel. > I implemented this solution using Virtual Audio Cable and WASAPI > Exclusive mode. It works well, but there are some catches: > > - it won't be glitch-free if the system is under heavy load (even if > the process priority is set to Realtime and MSCSS is used) > - this solution is quite convoluted, and will add a non-negligible > amount of latency to the audio path > > That's why I'm currently rewriting my filter as a GFX sAPO. > I will be curious to hear of your experience with this. It's certainly something that a lot of people want to do. -- Tim Roberts, timr@xxxxxxxxx Providenza & Boekelheide, Inc. ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/