3 ms·
I wrote a sound driver for BeOS, however I got strange glitches at what looked like random times. The driver tried to output samples at a fixed rate, however a
by ecpottinger 4y ago
I wrote a sound driver for BeOS, however I got strange glitches at what looked like random times.
The driver tried to output samples at a fixed rate, however after a lot of experimenting I found the glitches were caused when multiple interrupts conflicted (ie occurred at the same time) and the drivers was thrown off in it's Wait() timing call.
The answer was instead of waiting for a certain time to output a sample, to instead read what time it was and output the sample for that time-sample.
Worked perfectly, and also as important reduced the CPU load to only a faction of the first method.
- classichasclass 4y ago(author) Interesting. How did you know what was to transmit when, though?