From: David Olofson <audiality@swipnet.se>
To: linux-sound@vger.kernel.org
Subject: Re: Problems with X11Amp
Date: Thu, 13 Jan 2000 04:05:16 +0000 [thread overview]
Message-ID: <marc-linux-sound-94774998419683@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94767267915863@msgid-missing>
On Wed, 12 Jan 2000, Bryan Scaringe wrote:
> 2) It takes a lot of CPU cycles to decode MP3's. If you run a lot of
> stuff while listening to an MP3, it's going to sound horrible.
...unless you use Linux 2.2 + the lowlatency patch, and sets the mp3
player thead to SCHED_FIFO. That makes the player run as a true hard
real time task, ie it will never drop-out, and it'll just take the
CPU time it needs. (Provided your CPU is fast enough, obviously! :-)
In case you have missed it, see
http://matrix.crosswinds.net/~linuxmusic/lowlatency.html
It seems like a refined version of the lowlatency patch is going into
the mainstream 2.4 kernels... (Cutting scheduling latencies does
bring advantages in other areas than real time processing as well.)
//David
.- M u C o S -------------------. .- A u d i a l i t y ----------------.
| A Free/Open Multimedia | | Rock Solid, Hard Real Time, |
| Plugin & Integration Standard | | Low Latency Signal Processing |
`------> www.linuxdj.com/mucos -' `--> www.angelfire.com/or/audiality -'
.- D a v i d O l o f s o n ------------------------------------------.
| Audio Hacker, Linux Advocate, Open Source Advocate, Singer/Composer |
`----------------------------------------------> audiality@swipnet.se -'
prev parent reply other threads:[~2000-01-13 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-11 14:46 Problems with X11Amp
2000-01-12 19:25 ` Bryan Scaringe
2000-01-13 4:05 ` David Olofson [this message]
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=marc-linux-sound-94774998419683@msgid-missing \
--to=audiality@swipnet.se \
--cc=linux-sound@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox