Re: [Opalvoip-devel] Crash in sound_directsound.cxx
Brought to you by:
csoutheren,
rjongbloed
From: Robert J. <ro...@vo...> - 2010-03-23 07:48:05
|
OK, thanks, so that code is all camera stuff not sound. Cool. I agree that just using Windows MultiMedia interface is the go, it is what I always use. It does the "right thing" for a VoIP applications in terms of blocking and scheduling. The little I saw of the Direct Sound years ago, when last I looked at it, is that it really was a step backward in that regard with software timing loops etc. That said, there is the potential to reduce latency by using it, as Simon said you have to set the buffers to 10 (200+ milliseconds) on Vista to get it to work reliably. That's a chunk of latency. If only we could get someone to adopt that code .... hint, hint .... Robert Jongbloed OPAL/OpenH323/PTLib Architect and Co-founder. > -----Original Message----- > From: Simon Horne [mailto:s....@pa...] > Sent: Tuesday, 23 March 2010 6:33 PM > To: 'Robert Jongbloed'; opa...@li... > Subject: RE: [Opalvoip-devel] Crash in sound_directsound.cxx > > > Robert > > There are two versions of directshow. The first (DirectShow) is dependent on > directsound and the second (DirectShow2) is not. However there is an issue > with some PSDK versions and hanging include which needs to be commented out > in the code. There is a message in the code saying "if you get this error go > comment out..". DirectShow2 also has support for camera controls and > detection of non webcam directshow devices like video devices which accept > RTSP type commands (still WIP). > > I find the directsound implementation troublesome. I use WMM with large > number of buffers (10 for vista/win7). > > Simon > > -----Original Message----- > From: Robert Jongbloed [mailto:ro...@vo...] > Sent: Tuesday, 23 March 2010 5:14 PM > To: opa...@li... > Subject: Re: [Opalvoip-devel] Crash in sound_directsound.cxx > > I am sorry, I really do not have time right now to pursue this issue. > > I do know the direct sound is an unutterable mess, mostly due to Microsoft > constantly changing the location of libraries and header files. There are > also two versions of it in the source tree and I have no idea what the > difference is between them, other than significantly different code! > > What we really need is someone to take over the care and feeding of that > sub-system. Any volunteers? > > > Robert Jongbloed > OPAL/OpenH323/PTLib Architect and Co-founder. > > > > -----Original Message----- > > From: dca...@ma... [mailto:dca...@ma...] > > Sent: Saturday, 20 March 2010 4:27 AM > > To: opa...@li... > > Subject: Re: [Opalvoip-devel] Crash in sound_directsound.cxx > > > > Re-built opal fixed the crashing. Seems to be related to enabling > DirectSound > > in opal, and choosing an audio device other than 'Default'. > > -- > > Regards, > > -Demetrius Cassidy > > > > ---- dca...@ma... wrote: > > > > ============= > > Sending again without attachment > > > > -- > > Regards, > > -Demetrius Cassidy > > > > ---- dca...@ma... wrote: > > > > ============= > > I can reproduce this crash using WinXP SP3 32bit, using OpenPhone. > > Seems > that > > if you choose an audio output device name other than 'Default' (My > > options are DirectSound: SoundMAX HD Audio and WindowsMultimedia: > > SoundMAX HD > Audio), > > you get garbled audio (some popping sounds, then dead air) and then a > crash > > once you release the call. > > > > This seems to have started happening within the last few revisions of > ptlib, > > specifically in the last 1~2months before you could see "DirectSound" > > and "WindowsMultimedia" under the sound card options in the Audio Tab > > of OpenPhone. I am using the latest opal version from svn. > > > > Line 410: mAudioPlaybackBuffer->GetCurrentPosition (&Tail, &Head); > > > > Crash > PTLibd.dll!PSoundChannelDirectSound::Write(const void * > > buf=0x039eb090, int len=0x00000140) Line 410 + 0x1a bytes > > opald.dll!OpalRawMediaStream::WriteData(const unsigned char * > > buffer=0x039eb090, int length=0x00000140, int & written=0x00000000) > > Line > 891 > > + 0x21 bytes > > opald.dll!OpalMediaStream::WritePacket(RTP_DataFrame & packet={...}) > > > Line 323 + 0x15 bytes > > opald.dll!OpalMediaPatch::Sink::WriteFrame(RTP_DataFrame & > > sourceFrame={...}) Line 791 + 0x28 bytes > > opald.dll!OpalMediaPatch::DispatchFrame(RTP_DataFrame & frame={...}) > > > Line 622 + 0x13 bytes > > opald.dll!OpalMediaPatch::Main() Line 530 + 0xc bytes > > opald.dll!OpalMediaPatch::Thread::Main() Line 298 + 0x21 bytes > > PTLibd.dll!PThread::MainFunction(void * threadPtr=0x03a0e958) Line > > 723 > > msvcr90d.dll!_callthreadstartex() Line 348 + 0xf bytes C > > msvcr90d.dll!_threadstartex(void * ptd=0x03a00530) Line 331 > > > > > > First-chance exception at 0x00d72ccc (PTLibd.dll) in OpenPhone.exe: > > 0xC0000005: Access violation reading location 0x00000000. > > Unhandled exception at 0x00d72ccc (PTLibd.dll) in OpenPhone.exe: > 0xC0000005: > > Access violation reading location 0x00000000. > > The program '[0xE300] OpenPhone.exe: Native' has exited with code 0 (0x0). > > > > > > -- > > Regards, > > -Demetrius Cassidy > > > > > ---------------------------------------------------------------------------- > - > > - > > Download Intel® Parallel Studio Eval Try the new software tools > > for yourself. Speed compiling, find bugs proactively, and fine-tune > > applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Opalvoip-devel mailing list > > Opa...@li... > > https://lists.sourceforge.net/lists/listinfo/opalvoip-devel > > > ---------------------------------------------------------------------------- > -- > Download Intel® Parallel Studio Eval Try the new software tools for > yourself. Speed compiling, find bugs proactively, and fine-tune applications > for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Opalvoip-devel mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-devel |