Re: WaveIn notification methods
From: Chris P. [MVP] (msdn_at_chrisnet.net)
Date: 10/21/04
- Next message: Grant Schenck: "Re: WaveIn notification methods"
- Previous message: Chris P. [MVP]: "Re: ACM driver unique idendification"
- In reply to: lawrence: "Re: WaveIn notification methods"
- Next in thread: lawrence: "Re: WaveIn notification methods"
- Reply: lawrence: "Re: WaveIn notification methods"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 21 Oct 2004 10:50:05 -0400
lawrence wrote:
> The softphone genarally works fine and conversation can be done, but
> once in a while conversation become "dead air" or there would be a
> one-way audio. Grant mentioned something like the wavedrivers don't
> mark the waveheader flag to done. Is it possible that ciscowavedriver
> or the wavedriver of my headset (plantronics dsp500) sometimes dont
> change the flag to done?? And also when i do a waveInreset( ) after a
> "dead-air" or a oneway, my program hangs up. How can i work around
> with it?? thanks.
If the flag doesn't get changed then it's a driver bug, but if you're
application is locking up on waveInReset() that sometimes indicates that you
may be attempting to call waveInReset() from the wrong place at the wrong
time. What callback method are you currently using?
> p.s. and also where can i find some example code on how to implement
> the different callback modes?
I haven't seen any summaries but I'm sure if you google on each one
individually you will find sample code.
- Next message: Grant Schenck: "Re: WaveIn notification methods"
- Previous message: Chris P. [MVP]: "Re: ACM driver unique idendification"
- In reply to: lawrence: "Re: WaveIn notification methods"
- Next in thread: lawrence: "Re: WaveIn notification methods"
- Reply: lawrence: "Re: WaveIn notification methods"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|