Clemens Ladisch wrote:
Carlo Florendo wrote:
Clemens Ladisch wrote:
However, I wish to be able to make the sequencer or player work without the
use of the ALSA queue nor the workaround in (2).
Why?
Because the queue output and draining, AFAICS, is implemented in a blocking
manner.
When
Clemens Ladisch wrote:
Carlo Florendo wrote:
Clemens Ladisch wrote:
However, I wish to be able to make the sequencer or player work without the
use of the ALSA queue nor the workaround in (2).
Why?
Because the queue output and draining, AFAICS, is implemented in a blocking
manner.
When
Florian Schmidt wrote:
Another approach, that works very well in my experience, is to not sleep the
total required time until the next event, but rather regularly sleep for very
short amounts of time ( 1ms), wakeup, measure the current time and if any
event time now lies in the past, simply
Carlo Florendo wrote:
How could I get the app to u|nanosleep() in the most accurate way in
userspace
clock_nanosleep() - see also
http://linuxaudio.org/pipermail/linux-audio-dev/2007-March/018691.html
robin
___
Linux-audio-dev mailing list
On Tuesday 24 July 2007, Carlo Florendo wrote:
Hi,
(1) I've written a command line MIDI sequencer for lightweight systems and
am successful in making it work using the ALSA queue API. However, one
drawback of the API is its lack of callback functions. I wish to be able
to track events as
