From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: debian 8 rt kernel
Date: Fri, 13 Jan 2017 11:36:14 +0100 [thread overview]
Message-ID: <20170113113614.0f7db08a@archlinux.localdomain> (raw)
In-Reply-To: <20170113075215.GF2532@falbala.home.lespocky.de>
On Fri, 13 Jan 2017 08:52:15 +0100, Alexander Dahl wrote:
>Ubuntu Studio
Hi,
I'm an Arch Linux user, but I'm helping users with Ubuntu flavours,
including Ubuntu Studio.
The Ubuntu repositories provide a so called "lowlatency" kernel,
without the rt patch. I doubt that this is much better than a vanilla
kernel with threadirqs as boot option. It's easy to build the linux-rt
packages for Ubuntu flavours, but Ubuntu Studio has got other pitfalls,
too.
Ubuntu Studio is a distro for artists, it's not optimised for
musicians. The default is a jackdbus-pulseaudio mix/mess. While I'm an
Arch user, I anyway set up a tailored Ubuntu install, based upon a
minimal install from a server image.
The Ubuntu policy is to start all services provided by package, so the
user needs to disable all unwanted services, even when starting with a
minimal install, but at least such an install doesn't come with
pulseaudio and you could chose jackd instead of jackdbus.
I recommend against Ubuntu Studio, if a user should be unwilling to
check everything on her own and unwilling to set up everything on her
own. You even can't be sure that somebody really cares that rtirq and
the used kernel fit to each other.
Btw. there's nothing wrong with even using a vanilla kernel with
threadirqs as boot option. In regards to audio latency and MIDI jitter
there are a lot of things to consider, e.g. unbinding USB ports that
share unfavourable IRQs, caring about the CPU frequency handling ...
In my more than a decade of Linux audio experiences IMO the best
approach is to set up everything on your own, by optimizing several
settings. Without knowing all "audio distros" I anyway recommend
against just installing an "audio distro". In my experiences the work
that has to be done by the user is the same for "normal" distros and
"audio distros".
YMMV!
Regards,
Ralf
next prev parent reply other threads:[~2017-01-13 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 9:01 debian 8 rt kernel luca paganotti
2017-01-13 7:52 ` Alexander Dahl
2017-01-13 8:20 ` Robert Schwebel
2017-01-13 10:36 ` Ralf Mardorf [this message]
2017-01-14 9:12 ` Daniel Vidal
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=20170113113614.0f7db08a@archlinux.localdomain \
--to=ralf.mardorf@alice-dsl.net \
--cc=linux-rt-users@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.