Hi, Jeff, I am using CoolEdit Pro Special Edition 1.1. I don't know the build number. I tried another driver I wrote a while back that also uses WavePCI . It uses a totally different hardware architecture than the current card I work with. But, that driver has the same problem! In that case, that driver also passes WHQL, but this behaviour was not tested. It is very unlikely, but possible, that I have same bug in both drivers. I say unlikely because that code is substantially more complicated (and different) due to the architecture of the card. In that case, I am allowing the unused (and partially used) descriptors to be revoked. I am certain that WaveCyclic does not exhibit this behaviour. I knew about this problem when I went to WinHEC, but I thought it was just a bug I needed to fix. Now, I regret not bringing the issue up. Hmm...very strange that you don't use IPreFetchOffset. I will test it again without using IPreFetchOffset. Perhaps it is just the KMixer sample rate conversion that causes the problem. >From: "Jeff Pages" <jeff@xxxxxxxxxxxxxxxx> >Reply-To: wdmaudiodev@xxxxxxxxxxxxx >To: <wdmaudiodev@xxxxxxxxxxxxx> >Subject: [wdmaudiodev] Re: Update for Capture Problem on WavePCI >Date: Thu, 29 May 2003 13:06:56 +1000 > >I don't use IPreFetchOffset. > >I just tried setting the sampling rate to 6kHz (which my card doesn't >support in hardware) and the last buffer came back zero on XP, so it looks >like you're right about it happening when the SRC gets hooked in. > >I also tried the same thing on both the inbuilt soundport on the >motherboard >and a Soundblaster PCI card. The soundport returned 0 bytes in the last >buffer, but the Soundblaster returned it partially filled. I presume the >soundport uses WavePCI and the Soundblaster uses WaveCyclic. > >What version of CoolEdit are you running? I'm using CoolEdit 2000 version >1.1 Build 2418. > >The NT4 DDK provides a bit more information on the "correct" response to >wave input and output state changes. For WAVE_DD_RESET (which is equivalent >to KSSTATE_STOP) it says "cancels all input or output and sets the position >to zero, but may complete outstanding read/write requests for the wave >input/output devices". Looks like whether the last buffer gets anything in >it or not was left optional. > >Jeff > >----- Original Message ----- >From: "Martin Garcia" <doraemonx7@xxxxxxxxxxx> >To: <wdmaudiodev@xxxxxxxxxxxxx> >Sent: Thursday, May 29, 2003 12:23 PM >Subject: [wdmaudiodev] Re: Update for Capture Problem on WavePCI > > > > Hi, Jeff, > > > > Well, I think if under XP you do not use IPreFetchOffset and/or allow >KMixer > > to do sample rate conversion, you will also have the problem under XP. > > > > The fact you are also having the problem under 2000 really concerns me. > > > > I was hopeful that if I only accept entire "packets" as you call them, >that > > the problem would go away. I just tried that. But the problem does not >go > > away. I also tried limiting the number of packets, but that did not make >the > > problem go away. > > > > I know that WaveCyclic model does not exhibit this behaviour...And, I >know > > that Legacy Drivers do not exhibit this behaviour. > > > > I am starting to worry that this is a WavePCI problem. I can tell you >that >I > > have tried every possible way I can think of to get that last "big" > > application buffer to come back with some data, but no matter what I do > > (except using the IPreFetchOffset and disabling KMixer conversion under >XP), > > it will not come back with data. > > > > It is critical for us to run under Win2k because many of our customers >do > > so. We cannot use WaveCyclic (I don't want to get into that!) and many >of > > our customers are complaining about Legacy drivers. > > > > Amazingly, the driver passes WHQL tests...I am ready to go and certify >it! > > But, I need to use KMixer SRC and I need to run under 2k, and I really >need > > to get that last buffer!! > > > > At this point, it looks like I will have to live with the problem...but, >I > > guess I am surprised it has not come up before. > > > > Since there are now at least two people with the problem, I wonder if > > someone from Microsoft has any input on this issue. > > > > Anyway, Jeff, I really appreciate your time...it has been very helpful >in > > narrowing down the problem and at least I have tried several avenues I >had > > not explored before. > > >****************** > >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/ > _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ****************** 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/