>I use kernel 2.6 with Alsa (2.6 kernel internal ALSA). And some program is
>freezee or going to zombie.
>Example KDE artsd use alsa and some program want to acces it (example
>MozillaFirebird flash plugin) the accessing program going to zombie. (I try
>to desable artsD because if I use mplayer
when the state is OPEN, these values are bogus, since snd_pcm_status()
returns immediately without putting the values.
So, alsa writes bogus data to the proc entries? Maybe it shouldn't
write bad data, just leave the spots blank, initilize with 0's or
something else?
-
hw_ptr : 2694290
>I am working on a voice over IP application. We would like delays from
>the write to soundcard to the actual playout lower than 50ms. Do you
>think it is impossible with ALSA ? With OSS free the delay we got were
>quite good, without any tweaking. But ALSA is said to have better
>support for full-
At Tue, 21 Oct 2003 13:32:10 +0200 (CEST),
Jaroslav wrote:
>
> > very short while a write will block for more than one second. Are those
> > ALSA related problems, or hardware ones ?
>
> You said that you're using an USB device. It might be a problem with our
> USB driver. Also, USB devices are w
Hallo,
There really something wrong.
718, max jitter = 8192): wrong interrupt acknowledge?
ALSA sound/core/pcm_lib.c:157: Unexpected hw_pointer value (stream = 0,
delta: -297, max jitter = 1024): wrong interrupt acknowledge?
ALSA sound/core/pcm_lib.c:157: Unexpected hw_pointer value (stream = 0,
At Mon, 20 Oct 2003 09:35:57 +0200,
Svante Eriksson wrote:
>
> Hi all,
>
> What would be an appropriate ALSA way of implementing a two-way
> digital crossover PCM output? What I would like is for an ALSA PCM
> device to provide two SPDIF outputs with high- and low-band audio for
> the left and r
On Tue, Oct 21, 2003 at 11:38:36AM +0200, Werner Schweer wrote:
> On Monday 20 October 2003 22:31, you wrote:
> >
> > Nevertheless I will invite other us122 owners: Please try it out!
> >
> > The Tascam US-122 driver v0.12 is available here:
> > http://www.langerland.de/us122/driver.html
>
> funkt
At Tue, 21 Oct 2003 19:24:04 +0200 (CEST),
Jaroslav wrote:
>
> On Tue, 21 Oct 2003, Takashi Iwai wrote:
>
> > At Tue, 21 Oct 2003 17:37:30 +0200,
> > Tobias Peters wrote:
> > >
> > > I'm using linux-2.4.22 with alsa drivers 0.9.7c. Sound card driver in
> > > use was intel 8x0 (but I doubt it's re
At Tue, 21 Oct 2003 10:05:26 -0700,
Steve deRosier wrote:
>
> >
> > when the state is OPEN, these values are bogus, since snd_pcm_status()
> > returns immediately without putting the values.
> >
>
> So, alsa writes bogus data to the proc entries? Maybe it shouldn't
> write bad data, just leav
On Tue, 21 Oct 2003, Takashi Iwai wrote:
> At Tue, 21 Oct 2003 17:37:30 +0200,
> Tobias Peters wrote:
> >
> > I'm using linux-2.4.22 with alsa drivers 0.9.7c. Sound card driver in
> > use was intel 8x0 (but I doubt it's responsible in this case).
> >
> > ALSA ../alsa-kernel/core/pcm_lib.c:216: Une
OK, I discovered one of my problems (a dumb one, at that); I'd
aparently broken part of my build script and wasn't updating the
alsa-kernel subtree properly. I backed out the change in init.c and
updated/rebuilt. I still get an kernel oops, but was left running and
was able to get kysmoops to gi
At 21 Oct 2003 13:18:39 +0930,
Richard Lemon wrote:
>
>
> Hi Guys,
>
> I have been using the alsa api for a while working on some multimedia
> stuff.
>
> I believe I have found a bug with the intel8x0 driver when running the
> nforce chip-set.
>
> The problem appears to be an uninitialized var
>The left front channel is always mute when the M-Audio Revolution
>(ice1724) driver is started/restarted with all mixer settings saved
>on exit. The other channels are fine.
>Moving the DAC volume slider in alsamixer unmutes this channel.
I should add:
1) This bug does not exist in version 0.9.
At Tue, 21 Oct 2003 17:37:30 +0200,
Tobias Peters wrote:
>
> I'm using linux-2.4.22 with alsa drivers 0.9.7c. Sound card driver in
> use was intel 8x0 (but I doubt it's responsible in this case).
>
> ALSA ../alsa-kernel/core/pcm_lib.c:216: Unexpected hw_pointer value
> (stream = 0, delta: -255,
I'm using linux-2.4.22 with alsa drivers 0.9.7c. Sound card driver in
use was intel 8x0 (but I doubt it's responsible in this case).
ALSA ../alsa-kernel/core/pcm_lib.c:216: Unexpected hw_pointer value
(stream = 0, delta: -255, max jitter = 256): wrong interrupt acknowledge?
If I understand the re
On Tue, Oct 21, 2003, Jaroslav Kysela wrote:
> For a voice IP applications, it probably make sense to work without over
> and underrun detection (yes, if CPU is busy, there will be some scratches,
> but you'll avoid resyncing). Simply set stop_threshold to boundary for
> the no-xrun detection.
Tha
Hallo Takashi!
> >
> > > ~/.asoundrc. simply add
> > >
> > > pcm.dsp0 pcm.default
> >
> > Thanks! It helped one step more!
> > Now:
> > ***
> > hfkernel[1488]: hfkernel 0.4.2 starting...
> > hfkernel[1488]: Your soundcard is full duplex capable.
> > Good; the reference time will be
> > derived f
On Tue, 21 Oct 2003, Johan Bilien wrote:
> On Mon, Oct 20, 2003, Paul Davis wrote:
> > the output latency is always roughly the size of the hardware
> > buffer. there is no way to avoid this. the best you could ever do
> > would be one period, where there are two periods per buffer (i.e half
> > t
At Tue, 21 Oct 2003 16:38:44 +0800,
Bill Gou wrote:
>
> [1 ]
> Takashi Iwai wrote:
> > At Mon, 20 Oct 2003 15:48:55 +0800,
> > Gou Zhuang wrote:
> >
> >>I'm running kernel 2.4.22 and alsa-0.9.7c on a Dell laptop. I have problem on
> >>suspend/resume when alsa modules loaded. I have done a few te
>My second idea was to have a rather big hw buffer (500ms), and then set
>the start_threshold to a low value (32 frames for instance). But whatever
>my parameters were, I always got a playout delay of about the hw buffer
>size.
the output latency is always roughly the size of the hardware
buffer.
On Mon, Oct 20, 2003, Paul Davis wrote:
> the output latency is always roughly the size of the hardware
> buffer. there is no way to avoid this. the best you could ever do
> would be one period, where there are two periods per buffer (i.e half
> the buffer size). when i say "the best you could do",
> and I want to know where I find some documnent to know
> how to use these alsa lib api,namely,I want a
> specification of these api,thanks a lots .
http://www.alsa-project.org/alsa-doc/alsa-lib/
Tommi
---
This SF.net email is sponsored by OS
At Mon, 20 Oct 2003 11:05:29 -0700,
Steve deRosier wrote:
>
> All,
>
> We've noticed a problem with the newest version of Alsa while doing some
> stress testing of our devices. Basically, the scenerio is we're playing
> through a large library of .ogg files over the weekend. When we checked
At Mon, 20 Oct 2003 19:47:43 +0900,
Patrick Shirkey wrote:
>
> Anyone know the ETA for this driver?
it should work as well as nforce1, since nforce2 is compatible.
Takashi
>
> --
> Patrick Shirkey - Boost Hardware Ltd.
> Http://www.boosthardware.com
> Http://www.djcj.org - The Linux Audio Us
At Mon, 20 Oct 2003 11:12:08 +0200 (METDST),
Clemens Ladisch wrote:
>
> snd_pcm_playback_drain() holds card->power_lock until the substream
> has been drained completely. This prevents any other stream on that
> card from preparing during this time (which is very annoying if one is
> playing sever
At Mon, 20 Oct 2003 15:32:29 +0200,
Bernhard Gerlach wrote:
>
>
> Hello,
>
> Question 1:
>
> How do create a pointer and allocate memory to variables of type
> snd_seq_event to generate events by software? The function
> snd_seq_create_event doesn't exist anymore...
simply use malloc. it's
Bernhard Gerlach wrote:
> How do create a pointer and allocate memory to variables of type
> snd_seq_event to generate events by software? The function
> snd_seq_create_event doesn't exist anymore...
Use a standard pointer, and malloc/calloc/whateveralloc.
You can allocate events directly on the s
27 matches
Mail list logo
