From: eagle99 <ea...@se...> - 2003-04-06 04:37:22
|
Silvan wrote: The first thing to try is to make sure ALSA is actually working. My = usual=20 test for this is aplay -l My results : card 0: card0 [ESS ES1938 (Solo-1)], device 0: es-1938-1946 [ESS Solo-1] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Do an lsmod and see what you've got. I no longer remember what the OSS=20 modules are called, but if you have something that looks sound-related = and=20 doesn't have an "snd" in it, with the exception of "soundcore," then you = may=20 have trouble. My ALSA stuff looks like: How do I do this? I'm fairly new to linux. If you have the modules loaded, and you're getting something useful = looking=20 from aplay -l, then the next trick is to check that the mixer isn't set = at 0. =20 Try turning up the volume with alsamixer, aumix, KMix, etc. Both alsamixer and Kmix show volumes at 85. Once you're certain the volume is up, try to aplay -l a .wav file. If you pass all of those tests, then sound is working, and your problem = lies=20 elsewhere. Let's establish that you've gotten this far before I get into ways that = other=20 stuff might be misbehaving. If I play an audio file (mp3) the system sound is very good--but midis = are terrible. What=20 suggestions do you have for improving midi sound? Midi is what I'm most = interested in. Thanks for your help. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003 |