25 Jan
2009
25 Jan
'09
5:27 p.m.
Hiho,
just a note.
It does seem to behave properly on a Debian kernel 2.6.26, whereas it failed
on 2.6.24
sincerely,
Marije
On Sunday 11 January 2009 11:16:54 nescivi wrote:
On Sunday 11 January 2009 03:45:34 Fons Adriaensen
wrote:
On Sun, Jan 11, 2009 at 12:38:01AM -0500, nescivi
wrote:
yes, I did.
I tried it with:
snd_seq_event_output(mHandle, evt);
snd_seq_drain_output();
sincerely,
Marije
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev It is really strange. Sometimes it just works for
a while, and then it
just takes minutes before any event comes out.
The values print out fine, just something weird seems to be happening
in the actual scheduling.
Since you are using snd_seq_output_direct(), I *assume* you
don't need snd_seq_drain_output(). But have you ever tried
snd_seq_write();
snd_seq_drain_output();
instead of
snd_seq_write_direct(); ?