Do we need to associate this property with any node? If so, which KSNODETYPE should we use? Thanks At 02:04 AM 2/27/2003 -0500, you wrote: >wdmaudiodev Digest Wed, 26 Feb 2003 Volume: 02 Issue: 031 > >In This Issue: > [wdmaudiodev] Re: SRB data block size > >---------------------------------------------------------------------- > >From: "John Brinkman" <john@xxxxxxxxx> >Subject: [wdmaudiodev] Re: SRB data block size >Date: Wed, 26 Feb 2003 11:01:12 -0800 > > >You might look at this property: KSPROPERTY_CONNECTION_ALLOCATORFRAMING >This property is used by a client to retrieve the framing requirements for >the pin. >I don't know if KMixer uses this property so treat this post as a "hint" > >My driver does not support this property. >I have noticed that the size of the buffers can varied depending on the >application >that is using my stream class driver. > >Regards, >John > > >----- Original Message ----- >From: "BlazeAudio Developer" <developer@xxxxxxxxxxxxxx> >To: <wdmaudiodev@xxxxxxxxxxxxx> >Sent: Tuesday, February 25, 2003 5:53 PM >Subject: [wdmaudiodev] SRB data block size > > > > > > Hi, > > > > We have a stream class minidriver (on Windows XP, for a firewire audio > > device) that works fine when the internal buffering is 10ms or below, but > > we run into problems (driver starved of data) when the buffer size is > > increased. The internal buffering indirectly controls how often the driver > > completes the "pending" SRBs. > > > > This is very similar to the problem that Windows 3.1 drivers (and Win95 as > > well as WinNT 4 drivers) experienced when the DMA buffer size was >increased > > beyond a certain point. But that was directly related to how applications > > queued up the buffers. > > > > Does anybody know what determines the amount of data that KMixer (or is it > > Sysaudio) sends to the driver before waiting for the blocks to be >completed? > > > > I tried providing the KSPROPERTY_AUDIO_LATENCY property, but nobody >(KMixer > > or Sysaudio) seem to be interested in it - no get property calls come for >it. > > > > Is there a recommended maximum buffer size that KMixer assumes? > > > > Thanks. > > Devendra. > > > > >------------------------------ > >End of wdmaudiodev Digest V2 #31 >******************************** >****************** > >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.de/ ****************** 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.de/