Re: [LAD] ALSA POLLIN event problems

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-dev@...>
Date: Wednesday, January 26, 2011 - 7:59 pm

For some reason, gmail has stopped delivering my LAD messages, so
apologies if this reply isn't working correctly...

I'm attempting to run, in general, a 128 sample buffer (frames per
fragment). There is a lower latency mode though which is 64 samples.
I have two fragments. Maybe if I want to do this I should be using
three at least or make 128 the minimum.

But I'm a little confused at the lack of ins and outs being linked.
For a full duplex loop, I'd have to have the input before I can
process output for example, so I don't see how that works unless I
just ignore input requests from ALSA if I am not yet ready to receive.
I'm defining "ready to receive input" as the time after I run my
processing loop and then get a POLLOUT request. However, when I
ignore POLLINs like this, it seems like ALSA immediately POLLINs again
and I wind up with something like 50,000 polling requests handled in a
second, which drives the CPU usage through the roof.

>the in & out are not linked in any way as far as ALSA is concerned

Linux-audio-dev mailing list

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

This is the only confirmed message in this thread.
Possibly related messages: