[jitsi-dev] Audio on Linux


#1

Hi there,
I've been using Jitsi on Linux regularly for the past few month, with
PortAudio on my end and experienced regular issues (audio went dead
after a while, even had to reboot to make it work again).
Today I built PulseAudio in order to test it, and I had an audio
session of 4:40, longer than ever before, without issues.

So I wonder, what are the plans for audio on Linux?
PulseAudio is fairly common in the meanwhile but in my opinion it's not
the way to go. Since PulseAudio can act as a kitchen sink for alsa as
well, an alsa backend would cover more users than the PulseAudio
backend.
Do you plan to fix portaudio, or write a native alsa backend?

I'm not sure what benefit the native PulseAudio backend offers over an
alsa backend, maybe you can enlighten me on this.

Regards,
Philipp


#2

Hey Philipp,

PulseAudio is what one would commonly find on a majority of Linux
installations. Back when we implemented it pulse would also often block
access to alsa. Not sure if that's still the case. There were other
advantages too, like the promise of AEC ... although that didn't play out
as planned.

We may consider an alsa backend in the future, especially if a patch was to
materialize on this list or a pull request on github.

We are not currently planning on modifying portaudio in any way.

Cheers,
Emil

--sent from my mobile

···

On 10 Nov 2013 22:25, "Philipp Überbacher" <murks@tuxfamily.org> wrote:

Hi there,
I've been using Jitsi on Linux regularly for the past few month, with
PortAudio on my end and experienced regular issues (audio went dead
after a while, even had to reboot to make it work again).
Today I built PulseAudio in order to test it, and I had an audio
session of 4:40, longer than ever before, without issues.

So I wonder, what are the plans for audio on Linux?
PulseAudio is fairly common in the meanwhile but in my opinion it's not
the way to go. Since PulseAudio can act as a kitchen sink for alsa as
well, an alsa backend would cover more users than the PulseAudio
backend.
Do you plan to fix portaudio, or write a native alsa backend?

I'm not sure what benefit the native PulseAudio backend offers over an
alsa backend, maybe you can enlighten me on this.

Regards,
Philipp

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

OK, good to know that portaudio will stay for now.
I'm not a big fan of PulseAudio, maybe I'll find the motivation and try
to fix the portaudio issues or implement an alsa backend.

I've just seen that there are some binaries on github
(jitsi/lib/native/linux). So does this stuff even get built?

I read
(https://github.com/jitsi/jitsi/blob/8d60a758d0cc9122b8ac89f13601700de0f36a15/resources/install/debian/README.embedded-libraries)
that you use some fork of portaudio, but I couldn't find that fork, is
it still relevant?

Regards,
Philipp

···

On Mon, 11 Nov 2013 01:22:53 +0100 Emil Ivov <emcho@jitsi.org> wrote:

Hey Philipp,

PulseAudio is what one would commonly find on a majority of Linux
installations. Back when we implemented it pulse would also often
block access to alsa. Not sure if that's still the case. There were
other advantages too, like the promise of AEC ... although that
didn't play out as planned.

We may consider an alsa backend in the future, especially if a patch
was to materialize on this list or a pull request on github.

We are not currently planning on modifying portaudio in any way.

Cheers,
Emil


#4

Hi,

portaudio sources used can be found at https://github.com/jitsi/libsrc

Regards
damencho

···

On Mon, Nov 11, 2013 at 12:41 PM, Philipp Überbacher <murks@tuxfamily.org> wrote:

On Mon, 11 Nov 2013 01:22:53 +0100 > Emil Ivov <emcho@jitsi.org> wrote:

Hey Philipp,

PulseAudio is what one would commonly find on a majority of Linux
installations. Back when we implemented it pulse would also often
block access to alsa. Not sure if that's still the case. There were
other advantages too, like the promise of AEC ... although that
didn't play out as planned.

We may consider an alsa backend in the future, especially if a patch
was to materialize on this list or a pull request on github.

We are not currently planning on modifying portaudio in any way.

Cheers,
Emil

OK, good to know that portaudio will stay for now.
I'm not a big fan of PulseAudio, maybe I'll find the motivation and try
to fix the portaudio issues or implement an alsa backend.

I've just seen that there are some binaries on github
(jitsi/lib/native/linux). So does this stuff even get built?

I read
(https://github.com/jitsi/jitsi/blob/8d60a758d0cc9122b8ac89f13601700de0f36a15/resources/install/debian/README.embedded-libraries)
that you use some fork of portaudio, but I couldn't find that fork, is
it still relevant?

Regards,
Philipp

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

Thanks Damian,
can you tell me which version this is or where it comes from? According
to the Debian-Readme it is a hotplug fork, but I couldn't find this
fork yet.

Regards,
Philipp

···

On Mon, 11 Nov 2013 12:50:20 +0200 Damian Minkov <damencho@jitsi.org> wrote:

Hi,

portaudio sources used can be found at https://github.com/jitsi/libsrc

Regards
damencho


#6

I managed to answer some of those questions myself.
I managed to build the jitsi-version of portaudio, and pa_devs claims
to be version 1899, which I guess refers to the svn revision. If so,
then this comes from a snapshot after the last change to the
hotplug branch (1677) and after the latest stable release (1788).

I also found the hotplug-branch on assembla and downloaded the code
from there:
https://www.assembla.com/code/portaudio/subversion/nodes/1911/portaudio/branches/hotplug

However, comparing the zip files or the decompressed directories shows
that they are definitely not identical, the version from jitsi is
notably larger.

So the question remains, what codebase is this?

Regards,
Philipp

···

On Mon, 11 Nov 2013 13:17:16 +0100 Philipp Überbacher <murks@tuxfamily.org> wrote:

On Mon, 11 Nov 2013 12:50:20 +0200 > Damian Minkov <damencho@jitsi.org> wrote:

> Hi,
>
> portaudio sources used can be found at
> https://github.com/jitsi/libsrc
>
> Regards
> damencho

Thanks Damian,
can you tell me which version this is or where it comes from?
According to the Debian-Readme it is a hotplug fork, but I couldn't
find this fork yet.

Regards,
Philipp


#7

portaudio sources used can be found at
https://github.com/jitsi/libsrc

Regards
damencho

Thanks Damian,
can you tell me which version this is or where it comes from?
According to the Debian-Readme it is a hotplug fork, but I couldn't
find this fork yet.

Regards,
Philipp

I managed to answer some of those questions myself.
I managed to build the jitsi-version of portaudio, and pa_devs claims
to be version 1899, which I guess refers to the svn revision. If so,
then this comes from a snapshot after the last change to the
hotplug branch (1677) and after the latest stable release (1788).

I also found the hotplug-branch on assembla and downloaded the code from
there:
https://www.assembla.com/code/portaudio/subversion/nodes/1911/portaudio/b
ranc hes/hotplug

However, comparing the zip files or the decompressed directories shows
that they are definitely not identical, the version from jitsi is
notably larger.

So the question remains, what codebase is this?

Our own. We added hotplug support for more platforms, but this never went back into the PortAudio repository.

Regards,
Philipp

Ingo