I just installed jitsi 2.5.5194 on debian 7 Wheezy and very nearly jumped out of my skin because it turned up the volume to 100%.
1. This bug was identified two years ago: https://java.net/jira/browse/JITSI-1050
2. The way to fix the bug is also mentioned in the bug report
3. The last comment on the bug report is from Feb. 2014 (2 years since the bug was reported), requesting for the bug to be fixed
And STILL the bug is not fixed! What gives??
I have rather big speakers and having jitsi max out the volume every time a call begins/ends is extremely annoying. It made me mad enough to sign up to this mailing list and write this email
I've used Jitsi with PulseAudio on at least 4 releases of Ubuntu and
I've never seen this issue. Consequently, I'm moderately suspicious
that the "fix" proposed in https://java.net/jira/browse/JITSI-1050
will be appropriate. Besides, I seem to remember there was something
about flat and maxed volumes. Anyway, I'll try to look into it sooner
rather than later.
Commit 140f8b5eb86c1212a01f666efc846584e0416493 in jitsi/libjitsi and
commit ced46ddfb312caa6df6b563f0cad0da08411bc82 in jitsi/jitsi try to
remove the issue. These should be made available in Jitsi 2.5.5210.
Please try it out once it's baked and report back.
Thank you. I am willing to help in any way I can, which would mostly be testing of possible solutions.
Please let me know whenever you need assistance.
Regards,
Sagar
···
On 04/25/2014 10:23 AM, Lyubomir Marinov wrote:
I've used Jitsi with PulseAudio on at least 4 releases of Ubuntu and
I've never seen this issue. Consequently, I'm moderately suspicious
that the "fix" proposed in https://java.net/jira/browse/JITSI-1050
will be appropriate. Besides, I seem to remember there was something
about flat and maxed volumes. Anyway, I'll try to look into it sooner
rather than later.
and can confirm that the workaround suggested there works. But it would still be nice to not have to do it
Regards,
Sagar
···
On 04/25/2014 10:25 AM, Sagar Behere wrote:
On 04/25/2014 10:23 AM, Lyubomir Marinov wrote:
I've used Jitsi with PulseAudio on at least 4 releases of Ubuntu and
I've never seen this issue. Consequently, I'm moderately suspicious
that the "fix" proposed in https://java.net/jira/browse/JITSI-1050
will be appropriate. Besides, I seem to remember there was something
about flat and maxed volumes. Anyway, I'll try to look into it sooner
rather than later.
Thank you. I am willing to help in any way I can, which would mostly be
testing of possible solutions.
I've used Jitsi with PulseAudio on at least 4 releases of Ubuntu and
I've never seen this issue. Consequently, I'm moderately suspicious
that the "fix" proposed in https://java.net/jira/browse/JITSI-1050
will be appropriate. Besides, I seem to remember there was something
about flat and maxed volumes. Anyway, I'll try to look into it sooner
rather than later.
Is PulseAudio configured identically out-of-the-box on both Debian and
Ubuntu, though? i'm not sure it is ....
In any case, i'm on Debian Wheezy 32-bit, running Jitsi 2.5.5201,
and i don't experience this issue. i don't recall experiencing it with
any other nightly either, and i've been on nightlies for at least a
couple of months now.
Sagar, i notice you're on 2.5.5194; do you still get the problem on
later 2.5 builds?
Commit 140f8b5eb86c1212a01f666efc846584e0416493 in jitsi/libjitsi and
commit ced46ddfb312caa6df6b563f0cad0da08411bc82 in jitsi/jitsi try to
remove the issue. These should be made available in Jitsi 2.5.5210.
Please try it out once it's baked and report back.
Commit 140f8b5eb86c1212a01f666efc846584e0416493 in jitsi/libjitsi and
commit ced46ddfb312caa6df6b563f0cad0da08411bc82 in jitsi/jitsi try to
remove the issue. These should be made available in Jitsi 2.5.5210.
Please try it out once it's baked and report back.
Am Samstag, 26. April 2014, 23:40:18 schrieb Lyubomir Marinov:
Commit 140f8b5eb86c1212a01f666efc846584e0416493 in jitsi/libjitsi and
commit ced46ddfb312caa6df6b563f0cad0da08411bc82 in jitsi/jitsi try to
remove the issue. These should be made available in Jitsi 2.5.5210.
Please try it out once it's baked and report back.
I just downloaded the latest nightly, 2.5.5205 and tried it out. There is still a big jump in volume (although it does not go all the way to 100%). See here a 45 second screencast of the problem [HD video, you may need to view full-screen to make out the details]
I've used Jitsi with PulseAudio on at least 4 releases of Ubuntu and
I've never seen this issue. Consequently, I'm moderately suspicious
that the "fix" proposed in https://java.net/jira/browse/JITSI-1050
will be appropriate. Besides, I seem to remember there was something
about flat and maxed volumes. Anyway, I'll try to look into it sooner
rather than later.
Is PulseAudio configured identically out-of-the-box on both Debian and
Ubuntu, though? i'm not sure it is ....
In any case, i'm on Debian Wheezy 32-bit, running Jitsi 2.5.5201,
and i don't experience this issue. i don't recall experiencing it with
any other nightly either, and i've been on nightlies for at least a
couple of months now.
Sagar, i notice you're on 2.5.5194; do you still get the problem on
later 2.5 builds?
We haven't modified the PulseAudio integration in Jitsi for quite some
time so I don't expect functional differences with respect to it
between 2.5.5194 and subsequent 2.5 builds.
FWIW, we don't play with PulseAudio volumes at all. We just open the device! There might be ways for us to work around that issue but it still sounds to me as though this is primarly a PulseAudio problem that they may also want to resolve in PulseAudio itself.
I've used Jitsi with PulseAudio on at least 4 releases of Ubuntu and
I've never seen this issue. Consequently, I'm moderately suspicious
that the "fix" proposed in https://java.net/jira/browse/JITSI-1050
will be appropriate. Besides, I seem to remember there was something
about flat and maxed volumes. Anyway, I'll try to look into it sooner
rather than later.
Is PulseAudio configured identically out-of-the-box on both Debian and
Ubuntu, though? i'm not sure it is ....
In any case, i'm on Debian Wheezy 32-bit, running Jitsi 2.5.5201,
and i don't experience this issue. i don't recall experiencing it with
any other nightly either, and i've been on nightlies for at least a
couple of months now.
Sagar, i notice you're on 2.5.5194; do you still get the problem on
later 2.5 builds?
I just downloaded the latest nightly, 2.5.5205 and tried it out. There
is still a big jump in volume (although it does not go all the way to
100%). See here a 45 second screencast of the problem [HD video, you may
need to view full-screen to make out the details]
I've used Jitsi with PulseAudio on at least 4 releases of Ubuntu and
I've never seen this issue. Consequently, I'm moderately suspicious
that the "fix" proposed in https://java.net/jira/browse/JITSI-1050
will be appropriate. Besides, I seem to remember there was something
about flat and maxed volumes. Anyway, I'll try to look into it sooner
rather than later.
Is PulseAudio configured identically out-of-the-box on both Debian and
Ubuntu, though? i'm not sure it is ....
In any case, i'm on Debian Wheezy 32-bit, running Jitsi 2.5.5201,
and i don't experience this issue. i don't recall experiencing it with
any other nightly either, and i've been on nightlies for at least a
couple of months now.
Sagar, i notice you're on 2.5.5194; do you still get the problem on
later 2.5 builds?
I just downloaded the latest nightly, 2.5.5205 and tried it out. There
is still a big jump in volume (although it does not go all the way to
100%). See here a 45 second screencast of the problem [HD video, you may
need to view full-screen to make out the details]
As you can see, the volume was 24% before making the call. As soon as
the call is initiated, the volume jumps to 74%.
FWIW, we don't play with PulseAudio volumes at all. We just open the device! There might be ways for us to work around that issue but it still sounds to me as though this is primarly a PulseAudio problem that they may also want to resolve in PulseAudio itself.
As a data point, i just checked my own PulseAudio config:
* i have no ~/.pulse/daemon.conf file;
* The system-wide /etc/pulse/daemon.conf file has not been changed from
its default value of "flat-volumes = yes";
and yet i'm not experiencing the volume problem described. Which suggests
to me that the flat-volumes setting might be only part of the issue.
