[wdmaudiodev] Re: Need help in "FAIL: Non-zero position is being reported, but the cursor is not moving!"
- From: Gaurav Khuntale <gauravkhuntale@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Thu, 23 Jan 2014 12:00:56 +0530
Hi,
Thanks for the help. I will try to understand my driver behavior and its
clients requirement to get all HCK test pass.
On Thu, Jan 23, 2014 at 11:49 AM, Tsai Tzung-Dar <tdtsai1973@xxxxxxxxxxxx>wrote:
> Hi
> Most of KS Position test failed is cause by your GetPosition function do
> not return right position. The Startup Latency failed means your
> GetPosition function return 0 for a long time(over 15ms) since ks state
> change to KSSTATE_RUN. You can reference to MSVAD sample code in WDK 7600.
> I have try it before is can pass KS Position test in DTM 1.6.
> By the way If you are working on a virtual audio driver, why do you need
> to pass HCK test? I means you can not get WHQL certification with you
> virtual audio driver, why you need to do it.
>
> ------------------------------
> *寄件者：* Gaurav Khuntale <gauravkhuntale@xxxxxxxxx>
> *收件者：* wdmaudiodev@xxxxxxxxxxxxx
> *寄件日期：* 2014/1/23 (週四) 1:57 PM
> *主旨：* [wdmaudiodev] Need help in "FAIL: Non-zero position is being
> reported, but the cursor is not moving!"
>
> Hello,
>
> I am working on a virtual audio driver which is based on WaveCyclic.During
> KS Position test my driver is failing with following error,
>
> FAIL: Non-zero position is being reported, but the cursor is not moving!.
>
> Test Case is: Standard Streaming\Rendering Performance Tests\Startup
> Latency (standard streaming).
>
> As per my understanding, KS Position test checks the behavior of
> GetPosition function. But in case of this failure, i am failed to
> understand what exactly this failure means and where should i look in my
> driver code to solve this failure.
>
> Can anyone please help me to understand this failure ?
>
> During investigation, i got to know that during the transition from
> KSSTATE_RUN to KSSTATE_PAUSE state, play position should get freeze and it
> should unfreeze when transition from KSSTATE_PAUSE to KSSTATE_RUN happens.
> But my driver was not doing like this, so i thought this might be reason
> behind failure and i made changes in my driver code according to this. But
> still failure remains.
>
> Thanks.
>
>
>
Other related posts:
