I use the alsa sound server and have a problem some other people already pointed: The sound server is blocking on the alsa device and stop responding, in the end, the client also freez because communication pipe is full. Le Jeudi 10 Février 2005 08:35, Mark Wedel a écrit : Is anyone actually using alsa 1.0.x with the client sound server? It compiles just fine, but doesn't play sounds correctly (to be specific, I'm using alsa library 1.0.6). It compiles as alsa 0.9 support, but it looks like that should be compatible. This isn't a problem with the underlying drivers or alsa library, because if I use aplay on the sound file, it plays just fine. Looking at the code, it appears that the alsa 0.9 driver is significantly different enough that it may in fact make more sense to have its own file and not really try to use much of the existing logic (all the other sound drivers open the device and thus have a file descriptor they use). (as an aside, having different programs/executables for different sound systems may make sense - right now for example it is impossible to compile both the OSS and ALSA driver without re-running configure - it'd actually make sense to compile for all the sound systems that are supported) But before digging more into getting sound working with alsa 1.0, thought I'd ask here to see if other people have it working correctly. _______________________________________________ crossfire mailing list crossfire at metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire -- -- Tchize (David Delbecq) tchize at myrealbox.com Public PGP KEY FINGERPRINT: F4BC EF69 54CC F2B5 4621 8DAF 1C71 8E6B 5436 C17C Public PGP KEY location: http://wwwkeys.pgp.net/pgpnet/wwwkeys.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://shadowknight.real-time.com/pipermail/crossfire/attachments/20050210/e98214ad/attachment.pgp