On Fri, 2001-10-05 at 03:29, Takashi Iwai wrote:
At 04 Oct 2001 19:21:35 -0700,
Josh Green wrote:
Aggh.. I just ran a whole bunch of ALSA latencytests with various
drivers/kernels, all with fairly bad results :( I even went back to my
older kernel (2.4.5 with Andrew Morton's patch)
Not sure if you saw my question about whether there is some way to
determine where in the kernel a hold up occurs. How does Andrew Morton
check those things? Seems like a tool to determine what driver, program
or kernel routine is causing latency spikes would be a useful tool.
andrew himself
On Fri, 5 Oct 2001, Takashi Iwai wrote:
At Fri, 05 Oct 2001 10:24:26 -0400,
Paul Davis wrote:
A good news: after several tries and hacks, I got 1msec latency.
from what card? or is this using the h/w pointer location directly,
and not relying on interrupts ? i don't know any cards that can
Hi,
snd_pcm_resume is being implicitly declared in alsa-tools/ac3dec.
_J
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[EMAIL PROTECTED] (Jeremy Hall) writes:
snd_pcm_resume is being implicitly declared in alsa-tools/ac3dec.
ac3dec is obsolete, check out liba52.sourceforge.net
(They changed the name due to complaints from Dolby.)
The current version works fine in OSS emulation mode, but if you want
native
On Fri, 2001-10-05 at 14:27, James Courtier-Dutton wrote:
Hello
When I open device default with alsa09 and a emu10k1 card.
The volume control for this output in alsamixer is Wave Sur
I think that this should be PCM instead.
Which is the correct way to control volume of a PCM stream with
The pcm now comes out of the front line out again but has stopped coming
out of the rear. I see you have enabled the synth channel now. I look
forward to testing that out ;-]
I'm using the cvs from the 1/10 because I can't get the latest to
compile here.
Also the sound quality has degraded
