22 Oct
2002
22 Oct
'02
5:32 p.m.
Peter wrote:
On Tuesday 22 Oct 2002 17:42, Paul Winkler wrote:
I'd much rather have a list of current cards that work _well_ than a
lists of cards that don't.
The current ALSA card list just says whether or not a card has a
driver >(and
the state of that driver). It doesn't indicate how well the
card >is going to work.
On Tue, Oct 22, 2002 at 11:14:52AM +0100, Steve
Harris wrote:
> I can't answer this properly, but there is some issue to with mmap
mode
I
believe.
It is a very small number of cards that dont work.
We should compile a list of them, and maybe put
it in the JACK FAQ.
--PW
I don't want to have to learn about DSPs and stuff to be able to
identify a _good_ sound card. I've currently got a shortlist for my
next machine:
* MidiMan Delta Audiophile 2496 (Envy24)
* VideoLogic SonicFury OEM (CS4360)
* Creative SB PCI 128 (ES1371)
I've read the specs and looked around various review sites. Nothing
anywhere tells me how well they're going to work. Or does it? Am I
failing to find some secret source of information?
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 :(
As it is I have tried to provide a feedback inteface via the notes
additions in the docs. So far it is being used but not as much as it
could be. I guess it will just take time. You can lead a horse to water...
Do you have a specific idea envisioned for how we could present the info
more effectively or a way to make more people contribute their results?
I'm listening.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
22 Oct
22 Oct
7:40 p.m.
New subject: [linux-audio-dev] Re: image problem [was Re: [Alsa-devel] help for a levelmeter]
On Tuesday 22 Oct 2002 20:27, Patrick Shirkey wrote:
Peter wrote:
Heh. the life of a software developer. You only get fault reports and feature
requests (that need to be delivered yesterday) :-).
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 :(
As it is I have tried to provide a feedback inteface via the notes
additions in the docs. So far it is being used but not as much as it
could be. I guess it will just take time. You can lead a horse to water...
Ah, yes... I ought to post a report on my Evolution 249 USB keyboard. Works a
treat (well, Clemens latest change isn't in my alsa driver yet...).
Do you have a specific idea envisioned for how we could present the info
more effectively or a way to make more people contribute their results?
I'm listening.
I think the new website is a _huge_ improvement over the old, static, one.
Like I said elsewhere - I still don't really know enough about the hardware
side of audio to know _what_ I'm missing :-(
And getting the positive feedback ... maybe we could convince one of the large
PC mags to do a soundcard comparison on Linux/ALSA... :-)
If I knew enough to do a decent job, I'd happily nag everyone posting here,
individually, into submitting details of their hardware setup and how they
feel about their audio experience under Linux... :-)
-- Peter
23 Oct
23 Oct
11:10 a.m.
New subject: [linux-audio-dev] Re: image problem [was Re: [Alsa-devel] help for a levelmeter]
Paul Winkler wrote:
I can certainly sympathize with that one. Supposedly
there is some work
being done on supporting USB audio devices under ALSA; that may be our
best hope. (Yes, I know USB has potentiall horrible latency. )
I have just this morning been able to get a pure ecasound sine wave
through jack using my quattro.
The midiman quattro already performs perfectly with native alsa. I
haven't had a chance to really stress it yet but now that I have a new
vestax dj console it won't take me long I think.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
8059
days inactive
8060
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
2 participants
participants (2)
-
Patrick Shirkey -
Peter L Jones