I had to do this to fix the crackling while using googletalk plugin in firefox: replace /opt/google/talkplugin/GoogleTalkPlugin with: #!/bin/sh # Define current dir as a variable CURRENT_DIR=`dirname $0` # Execute the Google Talk Plugin BIN file with the right PULSE environment exec env PULSE_LATENCY_MSEC=60 $CURRENT_DIR/GoogleTalkPlugin.bin
(In reply to Vladi from comment #0) > I had to do this to fix the crackling while using googletalk plugin in > firefox: > > replace /opt/google/talkplugin/GoogleTalkPlugin with: > > #!/bin/sh > # Define current dir as a variable > CURRENT_DIR=`dirname $0` > # Execute the Google Talk Plugin BIN file with the right PULSE environment > exec env PULSE_LATENCY_MSEC=60 $CURRENT_DIR/GoogleTalkPlugin.bin I see, exporting PULSE_LATENCY_MSEC is the trick. But this seems more to be a hack for media-sound/pulseaudio than for www-plugins/google-talkplugin, CCing sound.
Looks like the way to go would be to fix it in googletalk side: http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/
(In reply to Pacho Ramos from comment #2) > Looks like the way to go would be to fix it in googletalk side: > http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/ I meant if we have to do the export for net-im/skype and www-plugins/google-talkplugin would it be cleaner to have media-sound/pulseaudio export it.
I disagree as looks like a bug in both and, then, I see not much sense on forcing PULSE_LATENCY_MSEC to all the apps that are running properly already
with recent www-plugins/google-talkplugin-5.41.3.0::gentoo and pulseaudio-13, is this issue still valid? Can be closed, if everything works correctly?
Non issue any more, Thanks.
