Seems like the best way, to me, would be a check early on in the microphone sampling -- though to eliminate code replication I would think it would be best to have that happen not in the input device wrapper, but somewhere slightly upstream, or in the abstract MpInputDeviceDriver. On Wed, Jul 15, 2009 at 6:30 PM, Paulo Vicentini <vicentini.pa...@gmail.com>wrote:
> Hello, > Yes, > I mean that setting volume to 0 (just try setting mic volume to 0 ) does > not actually mute the mic and remote party is able to hear the quiet (and > not so quite indeed) sound from the muted mic. > I was thinking somehow to set audio samples to zero maybe in > MpidWinMM::waveInCallbackStatic > Microphone's volume = 0 but samples are not 0: > a quick test within that function: > char *buff= ((PWAVEHDR) dwParam1)->lpData; > int n; > for(n=0; n < ((PWAVEHDR) dwParam1)->dwBytesRecorded; n++) > { > printf("%02x",(unsigned char) *(buff+n) ); > } > > > ecffecffecffecffecffecffecffeeffecffecffeaffe8ffeaffeaffecffeefff0fff0fff0ffeeff > > ecffeaffe8ffe8ffe8ffeaffecffeeffeeffeeffeeffeeffeeffecffecffeaffe8ffe8ffeaffecff > > ecffecffeaffeaffeaffeefff0fff2fff2fff0ffeeffecffeaffeaffe8ffe8ffe8ffeaffecffecff > > ecffecffeeffeefff2fff2fff0ffecffe8ffe6ffe6ffe8ffecfff0fff4fff4fff4fff4fff2fff0ff > > ecffeaffe8ffe8ffe8ffeaffeefff0fff2fff6fff6fff8fff8fff6fff2ffeeffeaffeaffeaffecff > > eefff2fff4fff2fff0ffeeffecffeefff2fff6fff8fff6fff2ffeeffeaffeaffecffeefff0fff2ff > > f4fff4fff6fff8fff8fff6fff6fff4fff2fff0fff0ffeeffeeffeeffeefff2fff2fff2fff2fff2ff > > f4fff4fff6fff8fffafffafff8fff4fff2ffeeffeefff0fff2fff6fff6fff8fff8fffafffafffaff > > fafffafff8fff6fff4fff4fff6fff8fffafffcfffcfffcfff8fff6fff4fff2fff4fff6fff8fff8ff > > f8fff8fffafffcfffcfffcfff8fff6fff2fff4fff6fff8fffafffafffafffafffcfffeff00000200 > > 02000000fefffafff8fff8fff6fff6fff6fff8fffafffcfffeff00000000000000000000fefffcff > > fafffafffafffafffafff8fff8fff8fffafffeff000004000400040000000000feff000000000000 > > 0000000000000000040008000a0008000600020000000000000000000000fefffefffeff00000400 > > 0800080008000600040004000400020002000000fefffeff00000400080008000800060004000600 > > 0600080006000200000000000000040008000a000800040002000200060008000a0008000200feff > > fcff0000040008000800060004000200020004000800080004000000fefffeff0000000002000400 > > 060008000c000e000e000c00080004000000feff0000020006000a000c000e000e000c000a000600 > > 0400020002000400060008000c000e000e000c000a0008000600060008000a000c000c000a000800 > > 0600060008000c000c000e000c000a000a0008000800060006000600060006000600080008000800 > > 0a000a000c000c000a00060004000400040008000e0012001400120010000c000c000a000a000a00 > > 08000600040006000a0010001400160014000c00060002000200040008000c00100010000e000c00 > > 0a000c000c000e000c000a0006000400040006000a000c000e000c000a000a000a000c0010001200 > > 10000e000c0008000800060006000600080008000a000a000c000c000a000a000800080008000800 > > 06000600060008000a000c000c000c0008000600060006000600060006000400060008000a000e00 > > > Paulo > On Wed, Jul 15, 2009 at 12:27 AM, Alexander Chemeris < > alexander.cheme...@sipez.com> wrote: > >> Hi, Paulo, >> >> >> >> On Wed, Jul 15, 2009 at 05:33, Paulo Vicentini<vicentini.pa...@gmail.com> >> wrote: >> > Currently mute feature on sipXtapi is implemented by putting the gain of >> the >> > mic to 0 using mixerSetControlDetails (win32) in MpCodec.cpp >> > But even though Window's mic gain is set to zero (Mixer) the audio is >> not >> > mute indeed; remote endpoint is still able to hear incoming RTP audio. >> > I am thinking on another approach, for instance, after mute is enabled, >> a >> > constant RTP payload is sent: >> >> I'm not sure I'm getting your idea. You still propose to send outgoing >> rtp packets, as we do currently. What is the difference? >> Or, do you mean that setting volume to 0 does not actually mute >> the mic and remote party is able to hear the very quiet sound from >> the muted mic? >> >> >> -- >> Regards, >> Alexander Chemeris. >> >> SIPez LLC. >> SIP VoIP, IM and Presence Consulting >> http://www.SIPez.com >> tel: +1 (617) 273-4000 >> > > > _______________________________________________ > sipxtapi-dev mailing list > sipxtapi-dev@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/ >
_______________________________________________ sipxtapi-dev mailing list sipxtapi-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/