Something is hogging the bus, and issuing NMI's with long intervals preventing other INT driven devices from getting their time intervals for things like playback etc.
This prevents other sound events from occuring when the program(s) expect them to. Bus mastering devices sharing IRQ's, bad drivers, etc. are normally to blame, and/or under Linux, some process hogging CPU time. -JMS |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]] On Behalf Of Jason Guidry |Sent: Tuesday, November 27, 2001 8:32 PM |To: [EMAIL PROTECTED] |Subject: Re: [expert] santa cruz turtle beach [slight OT] | | | |> Also if you get the sound working, it won't be instantaneous. That |> means with some programs like xmms, and most games (tuxracer, |> chromium, etc) there can be up to a two second delay from when an |> object does something to when the sound for that event gets played |> through your speakers (but that | |I'd love to hear an explaination for this. My home box has a |MSI KT7-266Pro |Mobo with the AC97 onboard audio. this chip had the same |problems you've |described above, under windows, with the packaged drivers. I |thought it |might be memory, but at the time I had 256MB. | |i kind of expected this behavior from a low end chip, but not |from a mid |range card like TB Santa cruz. | |
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
