Sound bug, GUS & select ()

Sound bug, GUS & select ()

Post by Rolf Fokken » Tue, 21 Oct 1997 04:00:00



Some additional information: a conclusion.

The fact that select () says the sound-device wants data, but ioctl ()
saying it doet not, creates very CPU-consuming programs!

I suspect a bug! That is a bug in the kernel or in my software.

Help!

 
 
 

Sound bug, GUS & select ()

Post by Rolf Fokken » Tue, 21 Oct 1997 04:00:00


I wrote a piece of software that uses select () to write data to the
sounddevice.

With a SB this works Okay: whenever it's the time to write some data to
the Sound Device the select () moves on, allowing the write to be done.

According to the OSS web-manual, before writing the data, the software
should query the device about the amount of space that's available
(ioctl SNDCTL_DSP_GETOSPACE), so the software knows what's the maximum
amount of data that can be written.

Well, what happens with GUS? After select () the kernel sometimes claims
that there's 0 bytes space for new data.

The kernel is version 2.0.30.

What am I doing wrong?

 
 
 

1. Bug in select() and/or sound drivers in Kernel 2.0.36?

I'm running R.H. 5.2 with an ISA AWE SB card. This works well enough.
However, when opening /dev/audio for read and issuing a select call,
the call eventually times out. Of course, there are always plenty of
data when reading from /dev/audio.

Is this corrected somewhere?

Thanks,

--
Jon Haugsand
  Norwegian Computing Center, <http://www.nr.no/engelsk/>

  Fax: +47 22697660, Pb 114 Blindern, N-0314 OSLO, Norway

2. Computer media need ethical overhaul

3. GUS-MAX & Teac SuperQuad 4x Cd-ROM & Linux

4. Linux with new PC with Windows 95

5. RH 7.2 && ISA Sound Blaster 16, no sound

6. ssh/sshd X forwarding question

7. Simultaneous recordng and playback on GUS 3.7 (no GUS MAX)

8. thread library

9. pmod, GUS, Voxware and /dev/gus

10. 1.1.21 kernel bugs GUS

11. Multiple & vs. && and | vs. || bugs in 2.4 and 2.5

12. Multiple & vs. && and | vs. || bugs in 2.5.63

13. Multiple & vs. && and | vs. || bugs in 2.4.20