RE: [Audio-dev] RE: delay Resume for DSP Device
"Nguyen, Khanh V" <[email protected]>
| Newsgroups | gmane.comp.multimedia.helix.devel |
|---|---|
| Message-ID | <AD75107ECAEC4949991FB357E775D5C53353F5AA@orsmsx502.amr.corp.intel.com> |
>-----Original Message----- >From: Greg Wright [mailto:[email protected]] >Sent: Friday, May 01, 2009 6:42 AM >To: Nguyen, Khanh V >Cc: [email protected]; [email protected] >Subject: Re: [Audio-dev] RE: delay Resume for DSP Device > >Nguyen, Khanh V wrote: >> Let me rephrase this question. How do I make sure that I have enough >> data before Resume is being called? >> >> Does SetAudioPushdown guarantee that I have that much data (for the >> pushdown time) before Resume is being called? > >Let me see if I understand what you are asking. > >You have replaced the audio device that the platform uses with one >of your own correct, as outlined in the DSP Integration document? Yes >You are asking when will resume() be called on your device implementation? Sort of, my question is what factors affect when resume() be called? if my device's granularity and pushdown value for encoded data is different than audio service, how can I make sure resume() won't be called until my own device's pushdown value is reached. Will calling SetAudioPushdown() passing my pushdown value guaranteed that resume won't be called until my pushdown value is reached? Eric has confirmed that from the other email. Thanks, --Khanh