[wdmaudiodev] Re: GFX APO loading/debugging
- From: Preston Fick <pffick@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Thu, 2 May 2013 22:58:22 -0700
Thanks Matthew -
I looked and it was the debug ATL library that was causing it. I was
confused because the sample did the same thing as my source, and this is
why. Thanks for the help!
Kind Regards -
Preston
On Thu, May 2, 2013 at 1:26 PM, Matthew van Eerde <
Matthew.van.Eerde@xxxxxxxxxxxxx> wrote:
> Hmm… I wonder if the issue is that you’re dynamically linking a C
> runtime which is not present on your test machine, preventing your module
> from loading.****
>
> ** **
>
> *From:* wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:
> wdmaudiodev-bounce@xxxxxxxxxxxxx] *On Behalf Of *Preston Fick
> *Sent:* Thursday, May 2, 2013 1:19 PM
> *To:* wdmaudiodev@xxxxxxxxxxxxx
> *Subject:* [wdmaudiodev] Re: GFX APO loading/debugging****
>
> ** **
>
> Hi Matthew -****
>
> ** **
>
> It looks like this was an issue with a Debug vs Release version of the
> APO. I was able to load the Debug version on the development machine after
> I loaded the tools, and after further testing it looks like if I build a
> release version I can put it on a fresh machine.****
>
> ** **
>
> - Preston****
>
> ** **
>
> On Tue, Apr 30, 2013 at 1:00 AM, Preston Fick <pffick@xxxxxxxxx> wrote:***
> *
>
> Hi Matthew -****
>
> ** **
>
> Yes - that's the weird part. From the registry standpoint it looks like
> everything is loading fine and all the keys/values from the INF for the APO
> and it's properties are in their proper places.****
>
> ** **
>
> I spent a lot of time debugging this tonight, and the last thing I did was
> change the audio format on the stock HD Audio driver before updating with
> my custom APO. After this the APO loads, the property page came up as
> expected and everything works. I wouldn't expect that to be the root of a
> problem like this. I'm unsure if there was something going on with the
> system itself, or if the audio format had an effect. Unfortunately I can't
> get the machine back into a state where it won't load the APO.****
>
> ** **
>
> Once I get through development I have other fresh machines of the same
> type to use for final testing, so if I get a concrete answer I'll follow up
> to the group, but if anything stands out I'd appreciate any feedback.****
>
>
> Thanks!****
>
> Preston****
>
> ** **
>
> ** **
>
> On Mon, Apr 29, 2013 at 5:34 PM, Matthew van Eerde <
> Matthew.van.Eerde@xxxxxxxxxxxxx> wrote:****
>
> If you look under
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6994ad04-93ef-11d0-a3cc-00a0c9223196}
> (that’s KSCATEGORY_AUDIO), do you see your FX\0 properties which you’re
> setting in your .inf?****
>
> ****
>
> *From:* wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:
> wdmaudiodev-bounce@xxxxxxxxxxxxx] *On Behalf Of *Preston Fick
> *Sent:* Monday, April 29, 2013 3:24 PM
> *To:* wdmaudiodev@xxxxxxxxxxxxx
> *Cc:* pffick@xxxxxxxxx
> *Subject:* [wdmaudiodev] GFX APO loading/debugging****
>
> ****
>
> I am working on a GFX APO and I can load it on my development machine
> without issues (driver loads and property page loads).****
>
> ****
>
> However when I put it on my test machine the APO shows up in Device
> Manager with the standard Windows HD Audio driver without problem codes,
> but I cannot see my System Effects property page. I rolled back to the Swap
> sample and it does the same thing. I am using 64 bit for both platforms
> (compiling for Windows Vista, loading on Windows 8), but the audio devices
> for each platform is different.****
>
> ****
>
> It seems the key here is getting the endpoint correct - I'm pretty certain
> that ths is right (on my development machine it is eHeadphoneWave and
> eHeadphoneTopo, on the test machine it is eSpeakerWave and eSpeakerTopo).
> If I load it on other endpoints I can see the Enhancements audio tab, but
> when I load it on the eSpeakerXXX endpoint it shows no property page for
> effects at all. This tells me it's restricting the load of the generic APO,
> but is failing during my APO's loading process.****
>
> ****
>
> I've added debug messages to the APO and Property Page DLLs, and it looks
> like they might not even be loading at all.****
>
> ****
>
> I'm looking for some suggestions on where I might continue to debug this
> problem.****
>
>
> Thanks!****
>
> Preston****
>
> ** **
>
> ** **
>
Other related posts:
