From: "Ivica Bukvic" <ico@fuse.net>
To: 'Dan Hollis' <goemon@anime.net>
Cc: alsa-devel@alsa-project.org, alsa-user@alsa-project.org
Subject: RE: question regarding latest CS4205 laptop soundcard driver
Date: Wed, 27 Feb 2002 01:00:01 -0500 [thread overview]
Message-ID: <a5hsv1$fpm$1@quimby2.netfonds.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0202261906010.21337-100000@sasami.anime.net>
> > *There is esd, which is outdated and simply crappy.
> > *There is artsd, which is better, but not good enough, and again,
the
> > app must be made to be aware of it in order to utilize it.
> > *There is JACK project which has a huge potential but none of its
> > effects are again universal, nor backwards-compatible with already
> > released software.
> > *There is Gstreamer, but I do not honestly know enough about it.
>
> Then make them better.
While I would like to thank you for your prompt response, I want to
point out that I find your above statement rather discouraging. Not
everyone is a low-level programmer, and not everyone should be one. Yet,
with such statement you are implying exactly that: "for one to use Linux
for multimedia, one has to be prepared to be able to do low-level coding
in an environment that inherently suffers from lack of documentation."
Although I've provided my humble coding contributions to the Linux
community, I am by no means an adept programmer who is capable of
dealing with the low-level stuff such as this (needless to say I have no
clue where to start since documentation is less than sparse). Besides, I
would love to help any of these projects to reach their "ripeness," but
find most of them to be focused on things that need less urgent
attention (i.e. JACK, as I understand it, focuses on inter-app audio
communication in a highly efficient manner, requiring app-side
implementation for any kind of dsp resource sharing, thus meaning there
is currently no planned backwards-compatibility, unless the older apps
are adapted to its architecture, which in itself is a rather far-fetched
assumption that the other application developers will be willing to
adapt their apps to this yet-and-if-to-be-established-standard).
Majority of the older, but still maintained apps, access the /dev/dsp
resources in an OSS fashion. Since my understanding is that Alsa is
already capable of fooling these through its OSS emulation (that, if I
am not mistaken, already transparently exists between the actual dsp
resource and the app), wouldn't it be a rather easy step to make it also
be capable of accepting multiple queries and down-mixing them before
sending them to the actual dsp?
Finally, why not merge the efforts of all these different
groups/projects into one concise solution, rather than a dozen
half-working ones?
Sincerely,
Ico
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next parent reply other threads:[~2002-02-27 6:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0202261906010.21337-100000@sasami.anime.net>
2002-02-27 6:00 ` Ivica Bukvic [this message]
[not found] <200202271510.KAA11571@renoir.op.net>
2002-02-27 19:11 ` question regarding latest CS4205 laptop soundcard driver Ivica Bukvic
2002-02-28 3:09 ` Paul Davis
2002-02-28 5:32 ` Ivica Bukvic
2002-02-28 14:12 ` Steve Harris
2002-02-27 9:02 Patrick Shirkey
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 8:48 Patrick Shirkey
[not found] <Pine.LNX.4.44.0202261636480.19581-100000@sasami.anime.net>
2002-02-27 2:26 ` Ivica Bukvic
[not found] ` <000001c1bf36$280ec3c0$ac1f830a@ico>
2002-02-27 3:09 ` Dan Hollis
2002-02-27 3:31 ` Andy Wingo
2002-02-27 15:10 ` Paul Davis
[not found] <20020226072437.47ED22756@sitemail.everyone.net>
2002-02-26 22:49 ` Ivica Bukvic
2002-02-27 0:41 ` Dan Hollis
2002-02-26 0:11 Ivica Bukvic
2002-02-26 10:59 ` Steve Harris
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='a5hsv1$fpm$1@quimby2.netfonds.no' \
--to=ico@fuse.net \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@alsa-project.org \
--cc=goemon@anime.net \
/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.