From: yodaiken@chelm.cs.nmt.edu
To: linux-sound@vger.kernel.org
Subject: Re: [alsa-devel] Re: [rtl] Low-latency patches working GREAT (<2.9ms audio latency), see testresults
Date: Sun, 29 Aug 1999 16:01:21 +0000 [thread overview]
Message-ID: <marc-linux-sound-93594564914404@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93591224029231@msgid-missing>
On Sun, Aug 29, 1999 at 03:34:41AM -0400, Paul Barton-Davis wrote:
> BeOS is unique in that its the first vaguely stable OS to be designed
> with multimedia in mind from the ground up. there are those of us who
What does that really mean? MacOS is pretty good for multimedia
if that is all you want to do and you have simple multimedia.
Can you drive a robotic system, sampling sensors, driving a display,
operating a feedback control loop, and pulling data from a large
scale data base using Beos? I doubt it. Beos offers low latency for
simple tasks, but DOS does that too.
> see computing technology as either currently or very soon delivering
> the power to do things with audio and video that have been hard to do
> without special purpose hardware as little as two years ago. right
> now, linux is not the right platform for doing this, and BeOS is, and
I never see any published data on BeOS benchmarks so it's hard to evaluate.
But there are some obvious problems with the OS in terms of
(A) hard rt response (none) (B) high speed networking (not) (C) high
bandwidth disk io ...
> there is persistent denial on l-k and elsewhere that an OS designed to
> effectively support "traditional" computer usage (compilation, number
> crunching, data serving) has any fundamental differences from one
> based around, say, real-time audio generation & manipulation.
Specifics would be useful. We need a
multimedia component of lmbench.
next prev parent reply other threads:[~1999-08-29 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-29 7:34 [alsa-devel] Re: [rtl] Low-latency patches working GREAT (<2.9ms audio latency), see testresults Paul Barton-Davis
1999-08-29 16:01 ` yodaiken [this message]
1999-08-30 2:24 ` Paul Barton-Davis
1999-08-30 5:17 ` yodaiken
1999-08-30 18:34 ` Paul Barton-Davis
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-93594564914404@msgid-missing \
--to=yodaiken@chelm.cs.nmt.edu \
--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