Clemens Ladisch wrote:
state: PREPARED
The pcm isn't (yet) running.
avail : 5
And the buffer is almost full. snd_pcm_writei blocks because it
cannot write more data to the buffer, probably because the transfer
threshold is too high.
?! See below...
How do you start the pcm? If
Jaroslav Kysela wrote:
alsa_buffer_size = snd_pcm_hw_params_get_buffer_size(params);
err = snd_pcm_hw_params_set_period_time_near(handle, params,
alsa_period_time, dir);
alsa_period_size = snd_pcm_hw_params_get_period_size(params, dir);
...
err =
Jaroslav Kysela wrote:
Which gives threshold = 6552 from buffer=6553, period=3276...
exactly the same value as the code I was already using gives! What
else am I missing from the garish red and yellow blocks of WinDiff?
Then it really appears like a bug. Could you add snd_pcm_dump() call
Despite the indifference to this issue, I thought it only fair to say that
switching to mmap seems to have stopped the problem from occuring.
- Tom.
Tom Browne wrote:
Hi all,
I am having serious trouble with ALSA using the poll method as shown
in the pcm.c test app...
Under certain
Clemens Ladisch wrote:
Tom Browne wrote:
Under certain conditions (yet to be established properly - it doesn't
happen every single time) with this ICE1712 card (DSP24),
snd_pcm_writei doesn't just block... it never comes back.
What is the state of the PCM device when this happens?
(see
sound at all in Linux with it
enabled...
Cheers,
Tom Browne.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals
Hi all,
After upgrading to Mandrake 9 (2.4.19, gcc3.2), and putting rc6 on, I am
unable to get any sound from any native ALSA app, which report write error:
File Descriptor in bad state. Info under /proc/asound all looks normal,
and the card seems to be initialised correctly. Even my own app,
Hiya,
The 1010LT uses different codecs to the normal 1010... they may well need
initialising in a different way...
- Tom.
- Original Message -
From: Jean-Marc Valin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, April 13, 2002 5:59 PM
Subject:
Er... do you mean...
ftp://ftp.alsa-project.org/pub/manuals/
?
- Tom.
- Original Message -
From: Paul Davis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 29, 2001 6:01 PM
Subject: [Alsa-devel] where are the reference files we have?
there's a hidden link
Well, well...
Looks like things might be alright after all. Swapping out the Savage4 for
the TNT2 fixed the X11 latency problems, and the LL patch fixed the
remaining glitches on the write test which the pre-empt+lockbreak combo
failed to solve.
Here's the results (Celeron-II 1.2 @ 1.5,
let me reiterate: you cannot safely call functions in alsa-lib from
the SIGIO handler, because alsa lib makes repeated calls to functions
that are not async safe. i also do not know the extent to which linux
POSIX compliance ensures that even those functions that are supposed
to async safe
11 matches
Mail list logo
