Re: jack2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Nov 5, 2009 at 5:23 PM, Andy Shevchenko
<andy.shevchenko@xxxxxxxxx> wrote:
> Hello.
>
> Nowadays the jack project has two branches - old jack (1) branch with
> version 0.116.2 and new one called jack2 version 1.9.3.
> I'd like to gather opinions and suggestions about applying new version for F13.
> Please, share your thoughts!
> Thank you.

Recently I have received following letters:


---------- message ----------
From: Adrian Knoth <adi@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, Mar 31, 2010 at 2:55 PM
Subject: Coordinated jackd upgrade
To: andy.shevchenko@xxxxxxxxx


Hi Andy!

I'm the Debian maintainer for jackd, ardour, ffado, qjackctl and some
more packages related to pro-audio.

After a long discussion, the Debian Multimedia Team decided to switch to
jackd2 in squeeze, our upcoming release.

We already coordinated with Ubuntu, they'll also switch ASAP, though
it's too late for their soon to be released Lucid.

We also contacted Opensuse (yesterday, answer pending), and now Fedora.
The idea is to have all major Linux distros using the same jackd
version, so users don't experience different levels of functionality
depending on the distro they use, non-applicable recipes from the
Internet, missing features and so on.

The rationale for our switch to jackd2:

  * ABI-compatible drop-in replacement for jackd1, so no need to change
    or recompile any application

  * SMP support. jackd1 can only use one processor/core

  * soundcard reservation. jackd2 can talk to pulseaudio via DBUS to
    acquire the soundcard, so no need to manually shutdown or rip off
    PA when a user wants to start jackd.

  * support for ladish session manager (http://ladish.org)


In general: more features, more everything. The Fedora-derived pro-audio
CCRMA distro uses jackd2, the Gentoo pro-audio overlay uses jackd2,
Ubuntu-Studio64 uses it and so on and so on...


We have our jackd2 package almost ready, so if you like, we can send you
a tarball if this helps.

How do you feel about this coordinated approach?


Cheerio


---------- message ----------
From: Adrian Knoth <adi@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, Mar 31, 2010 at 4:16 PM
Subject: Re: Coordinated jackd upgrade
To: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>


On Wed, Mar 31, 2010 at 03:02:08PM +0200, Andy Shevchenko wrote:

Hi!

> > Hi Andy!
> Because this is private message I would like to ask about possibility
> to forward this mail to the fedora-devel@ mailing list.

Of course, feel free to forward and if need be CC me, just in case you
want me to reply to something... this also holds true for this mail.


I see you've been discussing the very same problems. ;) Here are some
decisions we made:

  * only one package, that is, we ship jackd2, not jackd1+jackd2.
    There's no need for two packages, jackd1<->jackd2 are drop-in
    replacements to each other. Consequently, we avoid virtual packages.

  * Realtime permissions: our jackd package creates the file
    /etc/security/limits.d/audio.conf with the following content:

    @audio   -  rtprio     95
    @audio   -  memlock    unlimited


The jackd2 package is missing manpages. For a start, we'll simply copy
them from jackd1, but let me talk to upstream. This needs to be solved
in jackd2 anyway.




-- 
With Best Regards,
Andy Shevchenko
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux