* With the original 1282 build I was able to use OSS emulation in ALSA just fine, but with 12 I'm not able to use OSS emulation *or* native ALSA support. I played around with period_size, but 4500 seems to be right in that much more or less causes various errors - 4500 gives me no errors at all. I checked alsamixer and the "doom3 volume" is all the way up. asoundrc, I no longer get the "short write" message, which is good, but then I get *no* sound when I launch doom3. asoundrc has gotten me a lot further than before, thanks! However, I'm still not working. This is working fine with quake4 and doom3 on my box. No more hardware plugging to start gaming I fiddled a bit, 4096 is too less, 5000 too much. Is the way making idsoft happy with alsa. I have the feeling that this must be put into the Wiki. In pcm.doom3pcm, instead of what I wrote previously. If you think that having one more control degrades system performance to an unacceptable degree (after all, there is a reason for -fookin-fast-optimizations in CFLAGS ), use Code: It _should_ change only Doom3's volume, but it never worked here. When you start alsamixer, you should see a control named "Doom3 Volume". You need to restart alsa after creating /etc/nf I don't have Quake4, but since it uses the same engine, that should work for it too. It takes some guesswork to really nail it, but the plus side is that doom3 will use dmix and will get mixed along with everything else. If your sound pauses from time to time, decrease it. If your sound sounds metallic and you are getting ".short write."s, increase the period_size. Pay special attention to the period_size in d3dmixer. In your Doom3 config file (usually sits in ~/.doom3/base/DoomConfig.cfg) Put this in your /etc/nf or ~/.asoundrc, if you don't want everybody to have nice sound in Doom3 Code:Īnd put (meaning, replace the original values with) Code: The "problem" seemed to be that Doom3 needed a very specific period_size set for the card. Hopefully it's fixed in the next code release. I had a problem with lifts in Q4 and after some email he figured-out the problem was due to some GCC issues. If he feels it's a problem with the code, he will try to fix it. Hit the ALSA mailing list and ask about your problems with Quake4 and see if they can help.īounce your problem off of ttimo at id, the guy who's maintaining the Q4 port. Others have gotten around this by installing another sound card, which obviously you can't do with a laptop. Like others have said, it's probably some kind of bug with the ALSA drivers you are using. Mind you, I use ALSA for absolutely everything else without problem. The "fix" I used basically knocked Quake4 down to using OSS drivers, as best as I can tell from the Quake4 startup. I had the same sound issues you describe. If OSS sound doesn't work correctly on your system, then you have to fix that first.ĭoogman what do you mean? another aplications using OSS works well. If you are getting distorted sound with ALSA, all the tricks posted to fix that seem to make quake4 fall back to using OSS sound. I know - when it comes to the laptop - there is no choice My integrated soundcard worked well for all porpouses till now. Man invented language to satisfy his deep need to complain.Īnother soundcard is not a solution for me due to is a laptop computer. therefore quake-like games are always an issue for everybody. The most painfull is that none of the onboard sound solutions have a hw-mixing included. Thats why I had to use always some creative card. I had already 3 mainboards with onboard ac97 codecs and realtek sound chips - all the same shit. I'm afraid that all this on-board sound cotrollers are just piece of shit. Works well, drivers been in the kernel since ages. In 2 cases I was unhappy about motherboard audio so I bought SB Live pci cards. Gentoo Forums Forum Index Gamers & Players Gentoo Forums :: View topic - quake 4 sound issues
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |