Dear Harry: I found out that DirectShow always issued PAUSE command after it received 3 ~ 5 data packets. Then it have rerun. The packet size is 1920 bytes (48KHz) in my driver. It seems there are some problems in my returned packet. DirectShow receives it and rejects it by issuing a temp PAUSE command. However, I don't know how to fix it. The problem is only happened on Audio Capture Source filter which is modified to support a smaller delay buffer. Many Thanks and Best Regards, H.P. ----- Original Message ----- From: Harry Graham To: wdmaudiodev@xxxxxxxxxxxxx Sent: Tuesday, November 01, 2005 4:12 AM Subject: [wdmaudiodev] Re: My God!! Pause -> Start -> Pause -> Start -> Pause -> ...... This behavior can be caused by failing the transition from the KSSTATE_PAUSE to KSSTATE_RUN. Harry ------------------------------------------------------------------------------ From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of H.P. LIN Sent: Saturday, October 29, 2005 8:59 PM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] My God!! Pause -> Start -> Pause -> Start -> Pause -> ...... Dear All: I have written an audio driver and registered it on Audio Capture Sources category. Then I wrote a simple application to test it. When I use the capture filter from Audio Capture Sources, there is a preview delay which is happened. To follow the DirectShow doc., I try to modify the default buffer by IAMBufferNegotiation interface. The delay is disappear. However, there is another strange problem is happened now. After the adjusting, the DirectShow continuously sends out the Start -> Pause -> Start -> ... commands to me. ( SetDeviceState: KSSTATE_PAUSE -> KSSTATE_RUN -> KSSTATE_PAUSE -> KSSTATE_RUN -> ... ) Why?? If I have not modify the default buffer, it is normal. Can you help me? Many Thanks and Best Regards, Hueng-Pei, Lin