-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inaudible speech during first minutes of Pidgin calls #107
Comments
I am affected still as well (peers are keep on telling me that my voice is distorted), though I haven't yet had taken any measures. Compared to before it doesn't seem to bother my peers as much as before, so it has definitely improved. |
Please make some logs with |
Attached are the requested logs and dpkg_list.txt |
Perhaps there are some pointers in the packets. RTCP-packets might carry useful information https://en.wikipedia.org/wiki/RTP_Control_Protocol Either it is the packets, or it is an issue with the codec. |
Is here anyone who has these audio issues and uses something else than Ubuntu 14.04? @rbordelo is on 14.04 according to his logs, and if I remember correctly the same is true for @tmuehlhoff. Might be an issue with old GStreamer... |
I'm on 16.04 and have issues. |
I am on 16.04 and have experienced complete silence for 1-2 minutes during the beginning of a call that usually ends up with the other party hanging up. Once this happens, I can't connect back to them and they just hear a couple of fast beeps before it hangs up. Most of the people I engage with are running 'real' Skype for Business on Windows PCs. |
@rbeldin Sounds like a different issue to me. I also wouldn't claim that this issue is "inaudible" as the headline suggest, but definitely a "cracking" noise whenever your counterpart speaks. During moments of silence there is no background noise. It seems like a decoder issue, because the other party (who is on MS Lync) can hear everything just perfectly. The cracking noise is only on the Pidgin client. Also if both TX and RX uses similar routes, that perhaps also cancel out the possibility of a bandwidth issue (latency) or packet loss. |
Finding from one of our users: "If it helps, see below something experienced in last few days:
The above happened on 2 occasions already, coincidence?" |
@xnandersson That doesn't have to be so far-fetched a coincidence as it may look since Evolution might connect to pulseaudio server in order to e.g. play notification sounds. I've seen something similar under unrelated circumstances - if I recall correctly, when I would launch a QEMU virtual machine (with a configured sound card) using libvirt, the volume of my media player would suddenly decrease, and after turning the VM off, it would return to the original level. Sound quality wasn't affected though, just the volume. The user could try to collect some potentially useful piece of data should the situation you described happen again:
|
Looks like one can "fix" the problem by opening some other applications. If I start and close Thunderbird for example a few times it seems like it can fix the sound. No idea how this correlates though.... So perhaps it is just a matter of kicking pulse-audio a few times? |
I got bad received Audio, either I got no audio at all or there is audio with static noise in it. |
@joakim-tjernlund Does the noise go away after a while or is it persistent? The former would be consistent with this bug report. |
@xhaakon In this one off test I had noisy received audio to begin with and after a minute or two received audio died and we ended the test shortly after that. |
@joakim-tjernlund Try next time to let the call go on for longer. Preferably 10-20 minutes. Also try and open/close some other programs at the same time. |
I just hit another odd thing, I tested an Audio call with a coworker and while he could hear me fine, I just |
You can use Lync's integrated test call bot for checking your audio configuration. In Pidgin, go to |
Ahh, news to me. Test Call works fine for me. |
Anyone compared ALSA vs. Pulseaudio? |
No. But reportedly Debian is not tainted with this problem... |
And debian uses ALSA? |
Tried again a few times and now I got choppy sound using ALSA. |
On another machine I get choppy audio and GST_DEBUG=4 pidgin gives me
Any chance this is related? |
Which H264 impl. fits SIPE best, openh264 or x264 ? Minimum version of there? |
Are people using srtp 1.5.4/2.0.0 yet? |
Sipe uses x264 through GStreamer encoder and decoder plugins from the "ugly" set. We don't prescribe any minimal required version, but best choose something less ancient than what Ubuntu 14.04 has (our oldest supported system). The exact version number is a bit complex 2:0.142.2389+git956c8d8-2 - that upstream commit ID it includes is probably your best guide. We'd also like to take advantage of hardware accelerated H264 encoding & decoding through VAAPI, but its support in Farstream isn't quite there yet and causes crashes.
They use libsrtp that ships with their distro. I see Ubuntu 16.04 still has 1.4.5, so the versions you mentioned aren't in widespread use yet. |
On another machine I get choppy audio when doing a test call and GST_DEBUG=3 pidgin gives me
Is this normal? |
Using Pulseaudio I get lots of distortions and this is logged:
I have the feeling that these audio issues are latency based. This test machine has |
Here is a somewhat better data point, using http://repo.or.cz/siplcs.git/shortlog/refs/heads/mob I
while using pidgin-sipe 1.21.1 I get almost no distortion(if any) |
I there a way to play the Test Call with gst-play(or similar)? That would present a great way to |
Hi, |
@tmuehlhoff The sample sounds to me as if some very low-quality encoding was used. Could you please provide a Pidgin log from a conference call? I'd be interested in the codec being selected. Does your sound improve after a while as @xnandersson describes in the original post, or keeps being distorted for the whole duration of the call? Also what's the Ubuntu version you're currently using?
Lync conference servers usually support somewhat limited range of codecs compared to the desktop clients themselves, so this observation would support the theory that Sipe selects some low-bandwidth encoder although better options should be available on your system. There still remains the question why only some users experience this sound quality problem... |
Hi, thanks for answering. What kind of logs are you referring to ? the Pidgin "System log" remains empty even though I checked all 3 log boxes in preferences/logging. |
@tmuehlhoff I mean the terminal output when running Pidgin from shell with debug parameter:
|
I did a capture, I'm a bit hesitating to attach the whole log here since it contains company data. I'll snip out what I think is relevant. I can send you the full file via E-Mail. grep -i codec pidgin-debug.txt -A 10 -B 10 |
I would appreciate a list of codecs supported by SIPE, it is a jungle out there and for an amateur like me it is hard to keep up. |
I would assume G.729 would do fine... |
Just FYI, my audio became much better when I upgraded to ALSA 1.1.3 |
seems the PPA doesn't support trusty anymore in which I am still... |
Is there anything I can do about my bad uplink audio in multiparty calls ? One2one is usually ok! |
Got a similar issue now, doing a test call or one2one my microphon stops working for
|
with GST_DEBUG=4 I see when microphone is silent lost of:
|
BTW, pidgin-sipe specificall disables SIREN during conference claiming it doesn't work:
I took that out and tested conference and that worked fine(using SIREN codec) |
I will confirm that removing the SIREN treatment helped, I also had to greatly reduce volume on the mic in my case. |
@xnandersson, any comment on the exclusion of SIREN? Seems to work these days. Also, this commit, https://bitbucket.org/pidgin/main/commits/08a29966cee99dedfc266e79e8fba31ecc08aa37 ,might help the original audio issue. |
@joakim-tjernlund @xhaakon Thanks for the heads-up Joakim. Could be time to revisit this issue then. |
Sorry for if offtopic but I got this audio prolem where the microphone stops working and the last thing I see using GST_DEBUG=3 is:
And that comes from:
Got no idea if this func should try handle EAGAIN or if readfunc should do that. I cannot even |
The value of the optional "lastActive" attribute in a presence notification is now parsed and passed down as seconds since epoch timestamp to the backend. User visible changes in the Pidgin UI: * idle users are now "greyed out" like offline users * idle timers now work when "Show" -> "Idle Times" is enabled
Still an issue. Several reports. Can it be something else but the codec?
"Audio (both sent and received) is distorted and full of static -- basically unusable -- at the beginning of a call or meeting, but after anywhere between 1 and 10 minutes, it suddenly clears up. This happens regardless of whether I'm using the office Ethernet, the office WiFi, or connected via the VPN."
The text was updated successfully, but these errors were encountered: