From: Steve K. <st...@st...> - 2004-01-12 20:28:53
|
Steven Sokol wrote: >My client seems to be experiencing errors when I force it to switch the >Audio Output/Input devices while a call is active. I do this for >intercom calls if the client is configured with different ring and audio >out devices (to force the intercom over the main PC speaker). However, >the audio becomes terribly choppy and remains that way for all >subsequent calls until the client is closed and re-opened. > >The client also dies a terrible death on closing, popping several memory >exception error messages before finally falling into the bit bucket. > >Has anybody run into this before? My client is using the internal PA >audio interface. Is anybody out there using a different (i.e. the >external or the Windows native) audio interface? Do they work better? > > I'll answer your questions in reverse order :) 1) Nobody as far as I know is using any other audio driver than portaudio; The audio driver interface is modular, but the only "working" drivers are the portaudio and the file drivers. The file driver was just a hack I wrote for testing. The "windows" driver was written before things were really modularized, and it has not been maintained. 2) As far as the trouble you're reporting, the two issues may not be related. What happens when you change audio devices is that you end up calling pa_select_devices in audio_portaudio.c. This stops and then starts the devices, which should do the right thing, but there's a possibility that there's some subtle problems in the underlying libraries which make this not work properly. I'm not sure what that would be, though. -SteveK |