[jitsi-dev] Moving away from PortAudio?


#1

Hi,

After going through some earlier mailing list posts, it looks like Jitsi was using PortAudio earlier across all platforms (Linux, Windows, MacOSX) and has been moving away from PortAudio to more "native" audio backends like WASAPI, PulseAudio etc.

I am just curious as to why, since it looks like one audio backend across multiple systems would be easier to maintain.

- Sandeep


#2

Hey Sandeep,

PA is a very complex and rich architecture. RTC is not its primary usecase
so we just found that having to optimize PA across the different OSes would
be much harder than just writing thin backends for those systems ourselves.

--sent from my mobile

···

On 27 Jun 2014 10:28 PM, "Sandeep Raghuraman" <sandy.8925@gmail.com> wrote:

Hi,

After going through some earlier mailing list posts, it looks like Jitsi
was using PortAudio earlier across all platforms (Linux, Windows, MacOSX)
and has been moving away from PortAudio to more "native" audio backends
like WASAPI, PulseAudio etc.

I am just curious as to why, since it looks like one audio backend across
multiple systems would be easier to maintain.

- Sandeep

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


#3

Ok, thank you for answering my question.

- Sandeep

···

On 27/06/14 12:34, Emil Ivov wrote:

Hey Sandeep,

PA is a very complex and rich architecture. RTC is not its primary
usecase so we just found that having to optimize PA across the different
OSes would be much harder than just writing thin backends for those
systems ourselves.

--sent from my mobile

On 27 Jun 2014 10:28 PM, "Sandeep Raghuraman" <sandy.8925@gmail.com > <mailto:sandy.8925@gmail.com>> wrote:

    Hi,

    After going through some earlier mailing list posts, it looks like
    Jitsi was using PortAudio earlier across all platforms (Linux,
    Windows, MacOSX) and has been moving away from PortAudio to more
    "native" audio backends like WASAPI, PulseAudio etc.

    I am just curious as to why, since it looks like one audio backend
    across multiple systems would be easier to maintain.

    - Sandeep

    _________________________________________________
    dev mailing list
    dev@jitsi.org <mailto:dev@jitsi.org>
    Unsubscribe instructions and other list options:
    http://lists.jitsi.org/__mailman/listinfo/dev
    <http://lists.jitsi.org/mailman/listinfo/dev>

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