Discussion:
[jitsi-users] no sound transmitting with opus audio codec
Hendrik Adler
2014-01-12 22:51:48 UTC
Permalink
Hi,

thank your for your effort in developing this great software. But there
seems to be a problem with the newest version 2.4.4997. The audio signal
is not transmitted in any direction with the standard settings. It's
only working if I unselect the opus audio codec, so jitsi uses silk. By
the way my operating system is debian wheezy, my partner uses jitsi
2.4.4997 under Windows 8.1.

Cheers
Hendrik
Lyubomir Marinov
2014-01-12 23:06:53 UTC
Permalink
Post by Hendrik Adler
The audio signal
is not transmitted in any direction with the standard settings.
How did you figure that out please? The call info window in Jitsi?
Post by Hendrik Adler
my operating system is debian wheezy, my partner uses jitsi
2.4.4997 under Windows 8.1.
Is your partner's Jitsi sending audio over the network (in case she/he made
that observation, of course, and regardless of whether you're receiving it)?
Emil Ivov
2014-01-12 23:36:59 UTC
Permalink
Also, what Jitsi version is your partner using?

--sent from my mobile
Post by Lyubomir Marinov
Post by Hendrik Adler
The audio signal
is not transmitted in any direction with the standard settings.
How did you figure that out please? The call info window in Jitsi?
Post by Hendrik Adler
my operating system is debian wheezy, my partner uses jitsi
2.4.4997 under Windows 8.1.
Is your partner's Jitsi sending audio over the network (in case she/he
made that observation, of course, and regardless of whether you're
receiving it)?
_______________________________________________
users mailing list
http://lists.jitsi.org/mailman/listinfo/users
oli
2014-01-15 15:10:22 UTC
Permalink
Hi,
I'd like to open a ticket concerning the absence of sound transmission with the opus codec in the stable release 2.4 build 4997, since multiple users reported the bug:

http://lists.jitsi.org/pipermail/users/2014-January/006006.html
http://lists.jitsi.org/pipermail/users/2014-January/005996.html
http://lists.jitsi.org/pipermail/users/2014-January/006007.html
http://lists.jitsi.org/pipermail/users/2014-January/005971.html
http://lists.jitsi.org/pipermail/users/2014-January/006010.html

AFAIK this bug is present at least on Debian 7.3 amd64.
More info are present on more than one thread in the users list, we can compile them into a single bug report.
Thanks for the effort.
Boris Grozev
2014-01-15 15:37:30 UTC
Permalink
Post by oli
Hi,
http://lists.jitsi.org/pipermail/users/2014-January/006006.html
http://lists.jitsi.org/pipermail/users/2014-January/005996.html
http://lists.jitsi.org/pipermail/users/2014-January/006007.html
http://lists.jitsi.org/pipermail/users/2014-January/005971.html
http://lists.jitsi.org/pipermail/users/2014-January/006010.html
AFAIK this bug is present at least on Debian 7.3 amd64.
More info are present on more than one thread in the users list, we can compile them into a single bug report.
Thanks for the effort.
Hello, oli

Thanks for collecting all these threads.

We fixed a problem with opus in the nightlies (build 5035) earlier today
(I think that my message to users@ must have gotten lost, I don't see it
in the archives). Our opus binary was using GLIBC_2.14, which isn't
available on Wheezy.

I think the fix should solve the problem in most of the above threads.

Regards,
Boris
oli
2014-01-16 21:06:39 UTC
Permalink
Hi, thanks to Boris for the update about the fix.
The issue should now be fixes in the nightlies, and I will test it with a live Debian system when i get the time.
Unfortunately it is available only on the nightly channel right now, still many people, including myself, would prefer to use a stable version of Jitsi on daily used computers.

The fact is that the default
installation of Jitsi 2.4 build 4997, the current 'stable' is broken on
Debian Wheezy. The audio is basic functionality and only advanced users
would disable a codec (it also seems that SILK has no echo cancelllation
in Jitsi 2.4, so this workaround is of limited use).

Maybe it is worth considering a rerelease for Debian only, sort of a 2.4.1?

Additionally, it would necessary to do this if, as asked by Daniel Pocock on the dev list, the mantainers would like to offer a backport for Debian Wheezy.
Thanks

Loading...