[wdmaudiodev] Re: Crash in Sysaudio.sys

  • From: "Daniel E. Germann" <deg@xxxxxxxx>
  • To: <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Thu, 14 Oct 2004 07:15:16 -0500

Hi, Tim.

Sounds like you've already got it fixed. Adding a dummy "sum" node was my workaround.

I did talk to Microsoft when I was trying to solve this problem (they were very helpful!), and they agreed it was a documentation bug that should be fixed. I also sent a "DDK feedback" report on the relevant page in the docs. Hopefully, a clarification will make it into the next DDK release.

Best regards,

----- Original Message -----
Date: Wed, 13 Oct 2004 17:43:43 -0700
From: Tim Roberts <timr@xxxxxxxxx>
Subject: [wdmaudiodev] Re: Crash in Sysaudio.sys

Tim Roberts wrote:

A year ago, Daniel Germann reported on this list that his WaveCyclic
driver was triggering a crash very early in
sysaudio.sys!AddPinToFilterNode.  My TV audio/video capture filter is
triggering the same crash at the same point in
sysaudio.sys!AddPinToGraphNode.  If Daniel is still watching, what was
the resolution of your problem?

The problem starts when I add KSCATEGORY_AUDIO to my filter category
list.  If I omit that, I can force an audio graph together in graphedt
and it works fine, but the audio doesn't render by default.

Found it.

Sysaudio.sys requires that the audio pins have some kind of topology.
Further, that topology must pass through at least one internal node (you
can't go straight from a KSFILTER_NODE pin to a KSFILTER_NODE pin, as I
tried to do).  Further, there must be some kind of node descriptor for
that internal path.  Disobey any of those rules, and Sysaudio throws a
friendly blue-screen fit.

After cleaning that up, my KSCATEGORY_AUDIO processing works.

<sarcasm>All of this is extraordinarily well-documented, of course.

- 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


Other related posts: