[sip-comm-dev] Sound and video issues with build 2773 on Linux


#1

Hello,

I have some roblems with build 2773 (Debian Squeeze 32-bit):

- My webcam doesnt work anymore in native v4l mode (it does work with civil though). It worked in 2772.
The webcam is: 0ac8:305b Z-Star Microelectronics Corp. ZC0305 Webcam
It works with "mplayer tv:// tv=driver:v4l2" command, but i did post that already in previous discussions.

- I have PulseAudio installed, but it is not set as the default sound route - i created a pulse plug in ALSA for it. If i select this plug in the PortAudio device chooser, the sound works, but it is cracking all the time - and if i launch pavucontrol, the Sip Communicator's sound playback stream flickers and cannot be interacted with to set its volume. I have seen this in older builds.
Also the CPU usage jumps over 100% sometimes (in cases when i use the "pulse" plug; i cannot reproduce it consistently though) and stays there until i terminate the call. This issue was present in older builds.
And sometimes when changing the sound devices the program stops responding and it grabs mouse+keyboard focus from the X server and i have to kill it from tty1. This issue was present in older builds too.

Using the default plug the sound works, but it is not routed through PulseAudio (only ALSA) and prevents the PulseAudio server of playing any sounds (at least some apps) + i dont have the means to change its volume separately.
So does using java sound + launching Sip Communicator with padsp - in this case i can change its volume in pavucontrol, the sound hears just fine but it has a 0.5-1 sec lag probably because its long trip through Java Sound+PulseAudio.

In the previous builds (pre 2772 and 2772 had these issues for a lesser extent) sound worked fine through the pulse plug.
Regards,

Kertesz Laszlo

···

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi Kertesz,

For the webcam related problem I have just forgot to compiled libavcodec (ffmpeg) with MJPEG support on Linux 32-bit. It should be fixed now.

Regards,

···

--
Seb

Le 05/07/2010 08:55, Kertesz Laszlo a écrit :

Hello,

I have some roblems with build 2773 (Debian Squeeze 32-bit):

- My webcam doesnt work anymore in native v4l mode (it does work with civil though). It worked in 2772.
The webcam is: 0ac8:305b Z-Star Microelectronics Corp. ZC0305 Webcam
It works with "mplayer tv:// tv=driver:v4l2" command, but i did post that already in previous discussions.

- I have PulseAudio installed, but it is not set as the default sound route - i created a pulse plug in ALSA for it. If i select this plug in the PortAudio device chooser, the sound works, but it is cracking all the time - and if i launch pavucontrol, the Sip Communicator's sound playback stream flickers and cannot be interacted with to set its volume. I have seen this in older builds.
Also the CPU usage jumps over 100% sometimes (in cases when i use the "pulse" plug; i cannot reproduce it consistently though) and stays there until i terminate the call. This issue was present in older builds.
And sometimes when changing the sound devices the program stops responding and it grabs mouse+keyboard focus from the X server and i have to kill it from tty1. This issue was present in older builds too.

Using the default plug the sound works, but it is not routed through PulseAudio (only ALSA) and prevents the PulseAudio server of playing any sounds (at least some apps) + i dont have the means to change its volume separately.
So does using java sound + launching Sip Communicator with padsp - in this case i can change its volume in pavucontrol, the sound hears just fine but it has a 0.5-1 sec lag probably because its long trip through Java Sound+PulseAudio.

In the previous builds (pre 2772 and 2772 had these issues for a lesser extent) sound worked fine through the pulse plug.
Regards,

Kertesz Laszlo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

- I have PulseAudio installed, but it is not set as the default sound route
- i created a pulse plug in ALSA for it. If i select this plug in the
PortAudio device chooser, the sound works, but it is cracking all the time -
and if i launch pavucontrol, the Sip Communicator's sound playback stream
flickers and cannot be interacted with to set its volume. I have seen this
in older builds.

We've been hearing minor cracks in the sound on Linux and Mac OS X but
we don't currently have an idea what's causing them. Besides, our
reports of the issue suggest that it doesn't happen very often.

As to the "flicker"-ing in pavucontrol, I'm not really sure what the
issue is - I'm looking at GNOME Sound Preferences > Applications on my
Ubuntu Lucid and I'm able to change the volume for the input and
output streams of SIP Communicator.

Also the CPU usage jumps over 100% sometimes (in cases when i use the
"pulse" plug; i cannot reproduce it consistently though) and stays there
until i terminate the call. This issue was present in older builds.

I'm afraid I'm unable to reproduce it. As I previously suggested to
you, you might be able to give us more information on the cause of the
issue by preparing a CPU sampling profile using OProfile.

And sometimes when changing the sound devices the program stops responding
and it grabs mouse+keyboard focus from the X server and i have to kill it
from tty1. This issue was present in older builds too.

I haven't been able to reproduce the issue on my Ubuntu Lucid.
Admittedly, I don't have that many devices to choose from and some of
them seem to point to one and the same device anyway. Please give us
more details on the steps to reproduce the issue.

So does using java sound + launching Sip Communicator with padsp - in this
case i can change its volume in pavucontrol, the sound hears just fine but
it has a 0.5-1 sec lag probably because its long trip through Java
Sound+PulseAudio.

PortAudio was introduced in order to resolve issues with latency
(among many other issues).

In the previous builds (pre 2772 and 2772 had these issues for a lesser
extent) sound worked fine through the pulse plug.

The PortAudio functionality in SIP Communicator received some
non-trivial rewriting in order to enable wideband support so the
differences in quality are not surprising. I hope we'll manage to iron
out the newly-introduced issues.

At the end of the day, I'm not really sure when I'd personally be able
to focus on any of these issues but I'd suggest that you enter them in
our issue tracker so that they don't get forgotten and we can start
gathering the issue information in one place instead of spreading over
multiple e-mail messages.

···

On Mon, Jul 5, 2010 at 9:55 AM, Kertesz Laszlo <laszlo.kertesz@gmail.com> wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Thanks for the answer.

You are right, these issues cannot be reproduced consistently. The high CPU usage is random, sometimes it is sometimes it isnt. The flickering stream is 90% of the time. And i did download the profiler once but it seems its a bit too much for me :slight_smile:

I just recompiled PulseAudio from source, the sound quality is better (as it was in the older builds + the stream never flickers) and it seems that the high CPU spikes dont happen that often. I have to test it on my other 2 computers.
Maybe it was an issue related to the Debians PulseAudio package..?

Thanks for listening.

Regards,
Kertesz Laszlo

···

On Mon, 26 Jul 2010 20:11:39 +0300, Lubomir Marinov <lubo@sip-communicator.org> wrote:

On Mon, Jul 5, 2010 at 9:55 AM, Kertesz Laszlo > <laszlo.kertesz@gmail.com> wrote:

- I have PulseAudio installed, but it is not set as the default sound route
- i created a pulse plug in ALSA for it. If i select this plug in the
PortAudio device chooser, the sound works, but it is cracking all the time -
and if i launch pavucontrol, the Sip Communicator's sound playback stream
flickers and cannot be interacted with to set its volume. I have seen this
in older builds.

We've been hearing minor cracks in the sound on Linux and Mac OS X but
we don't currently have an idea what's causing them. Besides, our
reports of the issue suggest that it doesn't happen very often.

As to the "flicker"-ing in pavucontrol, I'm not really sure what the
issue is - I'm looking at GNOME Sound Preferences > Applications on my
Ubuntu Lucid and I'm able to change the volume for the input and
output streams of SIP Communicator.

Also the CPU usage jumps over 100% sometimes (in cases when i use the
"pulse" plug; i cannot reproduce it consistently though) and stays there
until i terminate the call. This issue was present in older builds.

I'm afraid I'm unable to reproduce it. As I previously suggested to
you, you might be able to give us more information on the cause of the
issue by preparing a CPU sampling profile using OProfile.

And sometimes when changing the sound devices the program stops responding
and it grabs mouse+keyboard focus from the X server and i have to kill it
from tty1. This issue was present in older builds too.

I haven't been able to reproduce the issue on my Ubuntu Lucid.
Admittedly, I don't have that many devices to choose from and some of
them seem to point to one and the same device anyway. Please give us
more details on the steps to reproduce the issue.

So does using java sound + launching Sip Communicator with padsp - in this
case i can change its volume in pavucontrol, the sound hears just fine but
it has a 0.5-1 sec lag probably because its long trip through Java
Sound+PulseAudio.

PortAudio was introduced in order to resolve issues with latency
(among many other issues).

In the previous builds (pre 2772 and 2772 had these issues for a lesser
extent) sound worked fine through the pulse plug.

The PortAudio functionality in SIP Communicator received some
non-trivial rewriting in order to enable wideband support so the
differences in quality are not surprising. I hope we'll manage to iron
out the newly-introduced issues.

At the end of the day, I'm not really sure when I'd personally be able
to focus on any of these issues but I'd suggest that you enter them in
our issue tracker so that they don't get forgotten and we can start
gathering the issue information in one place instead of spreading over
multiple e-mail messages.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net