From: Daniel James <daniel@64studio.com>
To: John Kacur <jkacur@redhat.com>
Cc: jordan <triplesquarednine@gmail.com>,
Gautam Thaker <gautam.h.thaker@lmco.com>,
linux-rt-users@vger.kernel.org
Subject: Re: "yum install ...." based instruction on building a RT kernel.
Date: Fri, 17 Sep 2010 13:38:42 +0100 [thread overview]
Message-ID: <4C936152.5000505@64studio.com> (raw)
In-Reply-To: <AANLkTi=GbDU7fKh9LvCEpjhSSMFF0syCqJVuqUERVBEJ@mail.gmail.com>
Hi John,
> There is something called Planet CCRMA, which is a set of
> repositories for audio packages that run on RedHat, Fedora and CentOS.
> They also package the real-time kernel in rpm form.
Ready-packaged RT kernels make sense for JACK users with generic PCs,
who may not be all that interested in optimisation (at first). They just
want to be able to install a program like Ardour and have it run
glitch-free.
Being a release or two behind the bleeding edge is no bad thing for that
type of user either - if (for instance) 2.6.31-rt works fine in a
production audio system, there's no big hurry to change it and
potentially break stuff. For that sort of user, high availability is
much more important than squeezing every last drop of performance out of
the hardware.
In audio recording, we're potentially capturing once-in-a-lifetime or
one-time-ever events, particularly since the industry focus has shifted
from the studio to the live stage - whether TV, stadium or festival,
that's where the artists are making their living these days. Even
festivals run to tight schedules, with only 15 minutes allowed to switch
between acts, including moving all the gear and repatching it. You can't
ask the band to go and get a beer while you recompile your kernel :-)
Cheers!
Daniel
next prev parent reply other threads:[~2010-09-17 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 22:54 "yum install ...." based instruction on building a RT kernel Gautam Thaker
2010-09-17 6:08 ` jordan
2010-09-17 7:08 ` John Kacur
2010-09-17 12:38 ` Daniel James [this message]
2010-09-17 13:06 ` Bernardo Barros
2010-09-17 15:25 ` EXTERNAL: " Gautam Thaker
2010-09-18 19:34 ` jordan
2010-09-17 13:10 ` John Kacur
2010-09-18 19:24 ` jordan
2010-09-19 15:49 ` Clark Williams
2010-09-19 17:23 ` jordan
2010-09-19 19:20 ` Bernardo Barros
2010-09-19 20:00 ` jordan
2010-10-17 15:20 ` jordan
2010-10-18 6:16 ` John Kacur
2010-10-18 7:12 ` jordan
2010-09-18 19:15 ` jordan
2010-09-18 20:06 ` jordan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C936152.5000505@64studio.com \
--to=daniel@64studio.com \
--cc=gautam.h.thaker@lmco.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=triplesquarednine@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).