Doom 3 Sound Issues


Recommended Posts

I was having this same problem and I have an Audigy Platinum. I hopped onto creatives web site, got the latest drivers and the EAX 4 support pack and that seemed to fix everything. Hopefully this will help you.

As has been said a couple times, but which I will repeat: Doom3 does not use the hardware-acceleration on any sound cards. It doesn't use EAX, it doesn't use DirectSound hardware acceleration. It is purely processed in software by the Doom3 engine on the CPU. So this problem is obviously a bug in Doom3 which will have to be fixed with a patch. Whatever made the sound start working again on your computer was probably either a coincidence, or Creative has some software running the the background that was interfering and the new driver changed what was happening (but I doubt that happens at all).

What's ironic is id used a software-only solution to ensure this exact scenario would not take place, that the amazing surround sound would work no matter what your configuration (as long as your configurations supported 4.1/5.1+), heh.

I've done some more research on stuttering sound. It turns out it's related to disk access using DMA. This is why it occurs most at the start of the levels while files are still being precached.

I'm using a VIA IDE chipset, and I've tried turning DMA off on all controllers but this just makes it worse as PIO is too slow to load the files.

This is some crazy schzit that is going on here and basically it means im SOL because there is no updated VIA drivers apart from the ones that ship with XP, I've tried 2 sound cards (cmedia onboard and creative soundblaster live value).

Crimson: I belive you are wrong with the no DirectSound. Turning off all hardware acceleration means that I get no sound, so it's gotta be using basic directsound access.

I agree however that it's very ironic. The sound problems people have had on this game way outnumber any on other games that I've heard of.

You can restart the sound system in the game easily by binding a key to s_restart. For example, bring down the console (ctrl+alt+~) and type "bind m s_restart" so that hitting m will restart the sound system in-game quickly.

Anyway, I'm using an Audigy 2 and I too notice some scratchy, intermittent sound sometimes on my 2.1 setup. To be honest I don't think it's a bug but rather a result of the CPU being stressed by video rendering to the point where it doesn't have enough juice to process the sound properly (so I suppose if you have a really high-end system you might not experience any sound problems). Also, in most games I get great surround simulation but with Doom 3 it kind of sucks to be honest, not to mention that the weapon sounds really lack bass and so feel weak.

Yes, I should of posted my computer specs. Sorry.

The readme just says get latest drivers and put hardware accelaration down. I've tried that, and it don't work.

My CPU is an AthlonXP 1800+ Palimino, 768MB PC2100 RAM, MSI KT400 mobo, GF4Ti4200 128MB. I'm using the latest drivers from NVidia.com - 61.77 I think. I don't think it's a driver/hardware related issue.

I've got same motherboard/video card as you, except I'm running a 2100+ with 1GB 2700 DDR.

Anyway, on newer games (FarCry, NFS:U) I have a different kind of problem, and I'm pretty sure it's sound related, although it COULD be video related. I can play Doom3 for about 2-3 minutes then all of a sudden my video freezes but the sounds keep playing. After about 10 seconds, it goes right back to normal...then it does it again after a said amount of time. On FarCry, I can't play more than 40 seconds without this happening. It doesn't matter what graphic settings I have in any of the games, it eventually happens.

I guess this isn't what is happening with the rest of you, but just thought I'd post it in case someone else has a fix or a similar issue.

BTW, I'm running Dets 45.23. With the 61.77, I had an instance in Doom3 where all lighting disappeared. If I turned on the flashlight it wouldn't illuminate anything. I've had no problems with the 45.23s though.

I am starting to think 100% that the IDE controller is at fault here.

Can you just check that you have a VIA IDE controller with a driver date of 7/2001? (sometime in 2001).

The worrying thing is that I think that ID actually know this is a problem as it's in the readme and the only people who have stuttering problems are on a VIA chipset mobo. This probably means they couldn't fix it and it's an external driver issue :/

restarting the sound works for me (when the sound just stops working), though it is still a pain in the butt (in the options menu of course, I haven't tried binding a key or anything yet). Im hoping its just a problem with the cracked exe and not the real game. I guess I will find out tomorrow morning :). I bet ID will have some patches out soon either way, their usually pretty good about things like that.

I've tried a different sound card (SBLive Value) and it's the same problem. Seems like it's a doom3 bug :(.

I had some problems with SBLive Value but changing the drivers to Windows XP default drivers seemed to fix the problem. My problem was that after (maybe) 10 minutes of play, the game/computer froze and the sound went into a very fast loop, sounding more like a machine gun :huh:

And I'm also considering if I should buy the required cable and try the onboard 5.1 digital sound output (AC'97 on Shuttle SB61G2), but I'm not sure if it eats much CPU compared to using the SBLive Value. Any ideas on this?

Thank god for this! i thought i would be the only one with this problem..

I have an Audigy 1 Platinum, and i'm having the sound cut off problem. Everything works fine, superb sound etc, then suddenly, silence... I was using the menu/surround off/on method to bring the sound back, but that basically ruined the game. Here's my findings:

1.I tried lowering the Hardware Accelleration settings on the audio device one notch. The problem still occurred..BUT... 90% of the time pressing ESC and returning to the menu would result in the sound coming back without having to unset/reset the surround sound option. However, this method is still pretty useless as it ruins the whole flow of the game.

2.I tried disabling the surround option (with Hardware Accelleration set to full). Again, the sound cut out randomly

3. I set the keybind to restart the sound.... this works well, but it's still damn annoying.

4.I switched to my motherboard's onboard sound, which is c-media 5.1. I now have uninterupted 5.1 surround sound, albeit slightly poorer quality than the Audigy puts out but still excellent. Occassionally, there is the odd crackle, which seems to be when accessing the disc, but i can live with that.

So, luckily, i have onboard sound to fall back on.. If you have onboard sound and you havent tried it yet, give it a go, it might give you a quick fix until the problem has been addressed via patch etc. It's interesting that I had this exact problem with Far Cry and Joint Operations. As far as I know, all 3 of these games have their own sound handling and dont use the actual card support?! (i could be wrong here).. until today I suspected that this issue was the audigy... and I was thinking of replacing it... now i just don't know.. is this soundcard related, motherboard, drivers, bad coding? ....it's definately damn annoying, and seems to be happening more and more with new titles.

restarting the sound works for me (when the sound just stops working), though it is still a pain in the butt (in the options menu of course, I haven't tried binding a key or anything yet). Im hoping its just a problem with the cracked exe and not the real game. I guess I will find out tomorrow morning :). I bet ID will have some patches out soon either way, their usually pretty good about things like that.

i dont have a cracked exe and its doing it for me, so i think you will experience the same problems with the retail :unsure:

I had some problems with SBLive Value but changing the drivers to Windows XP default drivers seemed to fix the problem. My problem was that after (maybe) 10 minutes of play, the game/computer froze and the sound went into a very fast loop, sounding more like a machine gun :huh:

And I'm also considering if I should buy the required cable and try the onboard 5.1 digital sound output (AC'97 on Shuttle SB61G2), but I'm not sure if it eats much CPU compared to using the SBLive Value. Any ideas on this?

I'm using the default Windows drivers...

I am starting to think 100% that the IDE controller is at fault here.

Can you just check that you have a VIA IDE controller with a driver date of 7/2001? (sometime in 2001).

The worrying thing is that I think that ID actually know this is a problem as it's in the readme and the only people who have stuttering problems are on a VIA chipset mobo. This probably means they couldn't fix it and it's an external driver issue :/

Aldo - I'm at work but I'll get back to you when I get home. But, I can almost assure you that it is 07/2001. I saw that date a bunch of times earlier today when I was trying to find a fix for my problem. I've tried a bunch of different Hyperion drivers, and unfortunately, the on-board sound drivers for CMedia go back to like 2001/2002. If it is a IDE Controller issue, I think you're right and we're going to be looking for a new mobo soon.

What BIOS version do you have for your KT400? I doubt it will fix anything, but I'm just curious. I have the 1.3 dated 01/2003.

you are aware of the ongoing issue relating to the via southbridge/PCI conflict issue?

i was plagued by this about 2 years ago... there were big problems with the controller I had on my board, which seemed to have issues with creative cards.. there was much arguing between via and creative, and i think it was creative who ended up with the blame. It was dubbed the 686 Southbridge issue or something like that? :blink:

The problems caused crackling and popping when the controller was being used. I got so fed up with it that I ditched VIA altogether, and instead tried another chipset manufacturer. I'm sure they will have fixed the problem that i was having back then, but this does sound very similar to what was happening back then. Check out www.viaarena.com and see if there are any issues with your board/controller. That site was very useful for me back in the day [;)]

best fix currently for the sound just cutting off is pulling down the console and binding a key to restart the sound. still sucks, but it will have to do.

Open up the DoomConfig.cfg file (which can be found in the .\base folder of Doom3's main install folder) and add the following line somewhere in the bind section at the top...

bind "x" "s_restart"

...but replace the letter x with a key of your choice. Once you're in the game and the sounds starts fugging up just tap the key you chose and everything should be fixed. No need to go into options and toggle surround or bind it manually everytime you play the game :)

Aldo - I can confirm now that the VIA Bus drivers I have are 07/01/2001.

I guess it's just time to upgrade, which I was planning on doing anyway.

That's what I thought :/. I'm using default BIOS that came with my board, and it's probably something like early 2003. I'm actually gonig to get a new rig anyway, but this is a real pain.

The only problem is that I am going to get a NForce2 board to replace this - either the MSI Delta something or the ASUS one - do you know if this will pose a problem with all these reports of problems :(

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • They aren't going to want to. Most would just go with the 17 Pro and save money. Why would they want to spend $300 for basically the same thing? It's not worth it if there are hardly any changes from year to year.
    • 24H2 rolled out to the Release Preview Channel in early June 2024, so this coming a bit later in the Experimental Channel (formerly Dev) doesn't really say much more than earlier H2 releases that came out in October. I am not sure what the thinking is here by putting it in Experimental, one would think that the 26H2 stamp means features are locked down and it's now bug tested until October? I don't even pretend to understand Microsoft's strategy for Windows Insider Program though
    • Nothing Ear (a) and CMF Buds Pro 2 with active noise cancellation drop to lowest price ever by Fiza Ali With Prime Day 2026 scheduled to run from Tuesday 23 to Friday 26 June, Amazon has already begun rolling out early access offers ahead of the main event. Particularly, Nothing Ear (a) and CMF Buds Pro 2 wireless earbuds have dropped to their lowest price ever with limited Prime deal offering 33% and 24% discounts, respectively. Nothing Ear (a) are equipped with 11mm dynamic drivers featuring a PM1 + TPU diaphragm. For noise control, the earbuds offer active noise cancellation (ANC) of up to 45dB across frequencies reaching 5,000Hz. The smart ANC algorithm adapts to surrounding noise levels, while a Transparency Mode allows users to remain aware of their environment when needed. Connectivity is handled via Bluetooth 5.3, with support for AAC, SBC, and LDAC audio codecs. Additional features include IP54-rated earbuds for dust and splash resistance, paired with an IPX2-rated charging case. Furthermore, users also benefit from pinch controls, in-ear detection, Google Fast Pair, Microsoft Swift Pair, dual-device connectivity, and a low-latency mode designed for gaming and video playback. The Nothing X app unlocks a range of customisation options, including a personalised equaliser, bass enhancement, control remapping, ear tip fit testing, firmware updates, dual-device management, a Find My Earbuds feature, and low-latency mode settings. When it comes to the battery, the earbuds house a 46mAh lithium-ion battery, while the charging case contains a 500mAh cell. With ANC disabled, users can expect up to 9.5 hours of playback from the earbuds and up to 42.5 hours in total with the charging case. With ANC enabled, battery life is rated at up to 5.5 hours per charge and up to 24.5 hours combined with the case. Finally, fast charging is also supported that should provide up to 10 hours of playback from a 10-minute charge with ANC turned off. Nothing Ear (a) Wireless Earbuds (Black): $53.20 (Amazon US) - 33% The CMF Buds Pro 2 feature a dual-driver audio system consisting of an 11mm bass driver and a 6mm micro-planar tweeter. The earbuds use PU (polyurethane) and PET (polyethylene terephthalate) titanium-coated diaphragms and are tuned by Nothing to deliver balanced audio performance. They further support active noise cancellation of up to 50dB across a frequency range of up to 5,000Hz, and noise control features include a Smart ANC algorithm, Adaptive ANC, Transparency Mode, and Clear Voice Technology 2.0. For calls, the CMF Buds Pro 2 use a total of six microphones and feature an environmental noise-cancelling algorithm, Clear Voice Technology 3.0, and Wind Noise Reduction 3.0 that should improve voice clarity during conversations. Furthermore, when it comes to the connectivity, it is provided through Bluetooth 5.4. Additional features include an IP55 rating for dust and water resistance, Google Fast Pair, Microsoft Swift Pair, in-ear detection, a low-latency mode, and a Find My Earbuds function. Moreover, through the Nothing X app for Android and iOS, users can access custom EQ settings, a bass enhancement algorithm, customisable controls, Find My Earbuds, low-latency mode, dual-device connectivity, an ear tip fit test, and firmware updates. The earbuds contain a 60mAh rechargeable lithium-ion battery, while the charging case houses a 460mAh battery. A full charge of the earbuds and case via USB-C should take approximately 85 minutes, while the earbuds alone should be fully recharged in the case in around 60 minutes. Battery life is rated at up to 11 hours of playback on a single charge and up to 43 hours with the charging case when ANC is turned off. With ANC enabled, playback time is reduced to up to 6.5 hours on the earbuds and up to 26 hours with the charging case. Talk time is rated at up to 6 hours on the earbuds and 25 hours with the case with ANC disabled, or up to 4.8 hours and 18.6 hours, respectively, with ANC enabled. CMF Buds Pro 2 Wireless Earbuds (Dark Grey): $37.05 (Amazon US) - 24% Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • The entire world moved to the vastly superior and now universally supported Dolby Atmos technology a very long time ago, mate.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      544
    2. 2
      +Edouard
      187
    3. 3
      Michael Scrip
      77
    4. 4
      PsYcHoKiLLa
      75
    5. 5
      Steven P.
      71
  • Tell a friend

    Love Neowin? Tell a friend!