-----Original Message-----
From: Peter L Jones [mailto:peter@drealm.org.uk]
On Tuesday 22 Oct 2002 20:27, Patrick Shirkey wrote:
Peter wrote:
>All these things just make life _easier_. I want to get on with
>developing code, not wondering why my hardware isn't performing. I
>don't _want_ to have to learn _that_ part of the system.
Because
I'll
only need
to do it once:
when I spec the next machine. (The next time I spec a machine,
everything I found out last time will be out of date.)
This is a good idea to have this support and you've picked the right
thread for asking for it. Currently there are only a
handful of people
who have worked on the official ALSA docs. I have
done 90%
of the work
myself. It's great I'm learning heaps in
the process and
will definitely
think about how to make it possible to add the
info you require.
Unfortunately we don't often get success stories on the
ALSA lists so we
don't really know how well things work until
someone says that it's
broken :(
Heh. the life of a software developer. You only get fault
reports and feature
requests (that need to be delivered yesterday) :-).
actually I think it would be of great value to document the failures -
from alsa web site (and even reading alsa-user mailing list) you might be
under impression that sound blaster live platinum works fairly well, the
truth is that it doesn't work really well (for what I want to use it for -
external midi doesn't really work, rca connectors are dead (last time I
checked)).
erik