On Thu, Mar 21, 2002 at 07:47:56PM +0100, Rickard Lind wrote:
> I think ALSA likes to use "other" interrupts to drive it's timer in many
> cases... In my old computer I had one SB16 and one GUS. I had my MT-32
> attached to the SB16 and HZ=100. When I programmed the MT-32 it was
> horribly slow until started playing wave files on the GUS, suddenly there
> was a timer to drive the midi output. Is your buffer driven from a que
> triggered by some timer system or is it triggered directly by a hardware
> interrupt?
Hey, ASLA is supposed to be taking care of that stuff! :)
I'm using ALSA's async callack mechanism. So its trigger mechanism is
completely out of my hands. However, the callback is being triggered
like clockwork. That isn't hte problem -- the insane thing is that the
buffer gets filled with blank data, and doesn't get filled sanely unless
you hold down the aforementioned key.
Try running it; you'll see what I mean.
(Or more to the point, it's like the adlib outbuffer is getting
clobbered with 0x00)
- Pizza
--
Solomon Peachy pizzaATfucktheusers.org
I ain't broke, but I'm badly bent. ICQ# 1318344
Patience comes to those who wait.
...It's not "Beanbag Love", it's a "Transanimate Relationship"...
-- Attached file included as plaintext by Listar --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8mjrUysXuytMhc5ERAukpAJ9mtJaPqZbzzNkvwgGDqHNTaNh/twCfdgy2
wCaK+UxPiGeqWlQls2+02/c=
=jlVC
-----END PGP SIGNATURE-----
