From: "szonyi calin" <caszonyi@yahoo.com>
To: Rob Love <rml@ximian.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 sound output - wierd effects
Date: Sat, 27 Dec 2003 23:44:51 +0100 (CET) [thread overview]
Message-ID: <20031227224451.73330.qmail@web40612.mail.yahoo.com> (raw)
In-Reply-To: <1072501808.4136.6.camel@fur>
--- Rob Love <rml@ximian.com> a écrit : > On Sat, 2003-12-27 at
00:02, Martin J. Bligh wrote:
>
> > Because someone broke it ... that's what this thread is
> about ;-)
>
> Right, sorry :-)
>
> But what does that have to do with OSS remaining in the kernel
> and the
> guy I was responding to having to continue to use OSS?
>
> I mean, it is a bug, and we will fix it. Keeping OSS is
> orthogonal.
> That was my point.
>
The problem is that alsa is not stable. At least not like oss.
I switched from alsa to oss because i could compile oss
directly in my kernel
(that was a long time ago).
and when 2.6.0-test apeared i compiled alsa in the kernel but i
had
problems with it and came back to oss:
1. SOund was jerky compared to oss (almost inaudible)
with oss emulation.
2. doesn't have an btaudio driver and i wasn't been able to
compile alsa and oss btaudio driver in the same kernel
so i couldn't watch tv with the alsa kernel :-(
3. Many old sound applications require oss (even emulated)
And oss emulation is far from stable.
These are my opinions. I hope they will change soon :-)
> Rob Love
>
Calin
=====
--
A mouse is a device used to point at
the xterm you want to type in.
Kim Alm on a.s.r.
_________________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
next prev parent reply other threads:[~2003-12-27 22:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 21:55 Martin J. Bligh
2003-12-26 22:27 ` Sven-Haegar Koch
2003-12-27 16:14 ` Martin J. Bligh
2003-12-26 22:52 ` Martin Schlemmer
2003-12-26 23:00 ` Martin J. Bligh
2003-12-26 23:17 ` Martin Schlemmer
2003-12-26 23:24 ` Martin J. Bligh
2003-12-26 23:50 ` Martin Schlemmer
2003-12-26 23:59 ` Martin J. Bligh
2003-12-27 0:44 ` Martin Schlemmer
2003-12-27 0:53 ` Martin Schlemmer
2003-12-27 4:34 ` Martin J. Bligh
2003-12-27 11:12 ` Martin Schlemmer
2003-12-27 16:17 ` Martin J. Bligh
2003-12-27 4:48 ` Stan Bubrouski
2003-12-27 4:57 ` Rob Love
2003-12-27 5:02 ` Martin J. Bligh
2003-12-27 5:10 ` Rob Love
2003-12-27 5:45 ` Stan Bubrouski
2003-12-27 22:44 ` szonyi calin [this message]
2003-12-27 7:50 ` OSS sound emulation broken between 2.6.0-test2 and test3 Martin J. Bligh
2003-12-27 11:11 ` Martin Schlemmer
2003-12-27 11:44 ` Edward Tandi
2003-12-27 12:24 ` Martin Schlemmer
2003-12-27 13:08 ` Edward Tandi
2003-12-27 14:33 ` Martin Schlemmer
2003-12-27 16:55 ` Edward Tandi
2003-12-27 17:22 ` Martin Schlemmer
2003-12-27 21:56 ` Henrik Storner
2003-12-27 22:51 ` Edward Tandi
2003-12-27 18:35 ` Martin J. Bligh
2003-12-27 19:56 ` Jaroslav Kysela
2003-12-27 20:12 ` Martin J. Bligh
2003-12-27 20:25 ` Martin Schlemmer
2003-12-27 20:44 ` Martin Schlemmer
2003-12-28 0:27 ` Martin J. Bligh
2004-01-03 0:53 ` Chris Shafer
2004-01-03 22:23 ` Martin Schlemmer
2003-12-28 5:06 ` Joshua Schmidlkofer
2003-12-26 22:59 ` 2.6.0 sound output - wierd effects Sander Sweers
2003-12-26 23:02 ` Martin J. Bligh
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=20031227224451.73330.qmail@web40612.mail.yahoo.com \
--to=caszonyi@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@ximian.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
all inboxes | Powered by JetHome®