On Friday 03 March 2006 02:38, Lee Revell wrote:
> On Wed, 2006-03-01 at 21:40 -0500, Paul Davis wrote:
> > its presentation of a multiplicity of programming models
>
> How would you solve this? Make people who insist on a
> read()/write()
> interface go through the OSS emulation layer? Would y
On Wed, 2006-03-01 at 21:40 -0500, Paul Davis wrote:
> its presentation of a multiplicity of programming models
How would you solve this? Make people who insist on a read()/write()
interface go through the OSS emulation layer? Would you remove
everything but the mmap() interface? The callback i
"Richard Spindler" <[EMAIL PROTECTED]> writes:
> 2006/3/2, David Kastrup <[EMAIL PROTECTED]>:
>> No, that's not what we are arguing, at least how I understood it. The
>> topic was not complexity but accessibility. If it is impossible to
>> find explanations, stuff is hard to do. A well-document
2006/3/2, David Kastrup <[EMAIL PROTECTED]>:
> No, that's not what we are arguing, at least how I understood it. The
> topic was not complexity but accessibility. If it is impossible to
> find explanations, stuff is hard to do. A well-documented crummy
> interface can be easier to work with than
Jussi Laako <[EMAIL PROTECTED]> writes:
> I somehow find this a bit funny. OSS has been dealing with these
> things at driver level and hiding the complexity pretty well. And it
> also works for pro cards like my Delta1010. First it was argued that
> there wasn't enough control and ALSA was better
On Thu, 2006-03-02 at 09:17 -0500, Paul Davis wrote:
> the framebuffer") was remarkably complex to do. ALSA strikes me as much
> the same way, at every level, from the kernel API, to libasound, to user
> space utilities.
> one could argue, as Lee has done, that people (programmers, users)
> should
> > no, it would provide names like
> >
> > MOTU 828 mkII channel 1+2
> > RME HDSP (#1)
> > Builtin Audio
> >
> > to the user.
> >
> > it would also fix a myriad of other problems in ALSA, such as its
> > reliance on interrupts that occur at regular sample-based intervals,
> >
> Can
On Thu, Mar 02, 2006 at 12:59:12PM +, James Courtier-Dutton wrote:
> If you don't like the current documentation, you are welcome to improve it.
> Just update the wiki.
I'd be happy to, if only I could just be a bit more confident
about my own knowledge. Currently I'm really in no position to
Alfons Adriaensen wrote:
On Wed, Mar 01, 2006 at 11:07:17PM +0100, David Kastrup wrote:
I am not asking for a solution. I am asking for a clue. The man page
to aplay does not mention what a PCM actually is. It just tells you
to list them with -L.
This is my main gripe with ALSA doc
Paul Davis wrote:
On Wed, 2006-03-01 at 17:28 -0500, Lee Revell wrote:
On Wed, 2006-03-01 at 17:18 -0500, Paul Davis wrote:
now that's what i call a sick joke.
if only i had more time, i'd be writing CoreAudio for linux right this
very second.
Which would magically make 5 zill
Paul Davis wrote:
aplay -D spdif:1 -f cdr /tmp/mnt/wo1.dat
ALSA lib confmisc.c:990:(snd_func_refer) Unable to find definition
'cards.USB-Audio.pcm.iec958.0:CARD=1,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_refer returned
error: No such file or d
On Wed, Mar 01, 2006 at 11:07:17PM +0100, David Kastrup wrote:
> I am not asking for a solution. I am asking for a clue. The man page
> to aplay does not mention what a PCM actually is. It just tells you
> to list them with -L.
This is my main gripe with ALSA documentation: it often uses terms
Hi,
On Wed, 2006-03-01 at 17:04 -0500, Lee Revell wrote:
> On Wed, 2006-03-01 at 22:48 +0100, Christoph Eckert wrote:
> > * alsaconf has done a really great job in the past, but meanwhile I see
> > the need for a replacement which can handle more than one card, support
> > USB (and in the future
13 matches
Mail list logo