All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Gareus <robin@gareus.org>
To: "Niccolò Belli" <darkbasic4@gmail.com>
Cc: Ng Oon-Ee <ngoonee@gmail.com>,
	Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel James <daniel@64studio.com>,
	Free Ekanayaka <free.ekanayaka@canonical.com>
Subject: Re: 2.6.3x-rty where x > 3 and y >= 1?
Date: Thu, 25 Nov 2010 01:29:52 +0100	[thread overview]
Message-ID: <4CEDAE00.1050800@gareus.org> (raw)
In-Reply-To: <4CE6E9B2.1040005@gmail.com>

On 11/19/10 22:18, Niccolò Belli wrote:
> Il 11/11/2010 23:49, Ng Oon-Ee ha scritto:
>>> Glad to hear that, I can't use 2.6.33-rt anymore because of problems
>>> with my intel video card and my band is starting to blame because of xruns.
>>>
>>> Darkbasic
>>
>> In the meantime, the -bfs kernel does improve the situation somewhat.
> 
> I just compiled 2.6.36-bfs, but unfortunately alsa git does not compile
> against it (I need alsa git because of M-Audio Fast Track Ultra support).
> 
Don't worry. It's not worth the hype it generated. I'm just back from
rolling a new kernel for 64studio. I tried a couple of candidates
including -bfs.

2.6.33.7-rt29 is _by far_ the best option for low-latency audio.
Well, actually it's the only option (not counting older rt-linux
releases) which provides reliable <=4 ms latency (16 or 32 audio-frames
per period) without any x-runs!

Vanilla 2.6.36 and -bfs kernel both perform quite well. If >=15 ms
latency is sufficient for your use-case and you can live with some
occasional x-run that is.

I'm looking forward to a new -rt patch.

Cheers!
robin

PS. Note that sound latency here is not calculated (eg. 32*2/48kHz) but
measured with jack_delay from http://www.kokkinizita.net/linuxaudio/
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-11-25  0:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 19:36 2.6.3x-rty where x > 3 and y >= 1? Fernando Lopez-Lezcano
2010-11-10 20:54 ` Thomas Gleixner
2010-11-11 14:56   ` Niccolò Belli
2010-11-11 22:49     ` Ng Oon-Ee
2010-11-11 22:49       ` Ng Oon-Ee
2010-11-11 23:44       ` Bernardo Barros
2010-11-11 23:44         ` Bernardo Barros
2010-11-12  0:05         ` jordan
2010-11-19 21:18       ` Niccolò Belli
2010-11-25  0:29         ` Robin Gareus [this message]
2010-11-27 17:20           ` Niccolò Belli
2010-11-25  0:29     ` Robin Gareus
2010-11-25 11:25       ` Niccolò Belli

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=4CEDAE00.1050800@gareus.org \
    --to=robin@gareus.org \
    --cc=daniel@64studio.com \
    --cc=darkbasic4@gmail.com \
    --cc=free.ekanayaka@canonical.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=ngoonee@gmail.com \
    --cc=tglx@linutronix.de \
    /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.