Audio Backend Woes: OpenAL vs. DSound

[ViRGE]

When it comes to the audio backend for Dolphin, there are two choices: DirectSound and OpenAL. Unfortunately I can't seem to make either one work satisfactorily and I could use some insights if anyone has any to offer.

I'm currently trying to play NSMB on the R51xx/R52xx builds of Dolphin, and thanks to a bug between the frame limiter and idle skipping, I have to turn idle skipping off to keep the frame limiter working. However the issue I'm running in to is that if I do this, the OpenAL backend for Dolphin will crash. Basically I'm finding it unusable: I either have to take a major frame rate hit, or it crashes on me.

However if I use the DirectSound backend, there's a very noticeable delay in the audio; I'd guess 100ms or so. So while DSound works the audio latency is really ghastly on a precision game like NSMB.

So is there something I'm missing here such as a setting? It seems like there's currently no good audio backend for Dolphin based on my experiences.

System Specs:
Core i7 950
4GB RAM
Radeon 5870
Creative SoundBlaster X-Fi XtremeMusic
Win7 Ultimate 64bit

[thaCASHdude]

try ticking "Enable audio throttle"

[ViRGE]

(04-06-2010, 05:59 AM)thaCASHdude Wrote: try ticking "Enable audio throttle"

Audio throttle is only so-so. It certainly works, but then it's not as smooth as the frame limiter. It tends to come in at 57-58 FPS, which leads to NSMB being oddly jerky at times.

[skid]

I had a look into this area of the code recently and can give you a couple tips if you are able to compile your own builds of Dolphin. Neither of the settings are changeable via the GUI.

The first change (and the one I think will most make the most difference is in a file called "DSoundStream.cpp" in the "Source/Core/AudioCommon/Src" directory.

Within this file is a function named "void DSound::SoundLoop()". Within this function is a line:

Code:

if (numBytesToRender >= 256)

Change the 256 to a lower number (but keep it a positive whole number) to reduce the latency of the DSound backend. The trade-off is that you'll get higher CPU usage - but your PC specs are more than capable of handling it.




The second setting which is less likely to fix the latency and more likely to cause crashes is in a file named, "SystemTimers.cpp" in the directory "Source/Core/Core/Src/HW". This file has two lines (one for the GC and the other is for Wii) that look like this:

Code:

DSP_PERIOD = (int)(GetTicksPerSecond() * 0.003f);
DSP_PERIOD = (int)(GetTicksPerSecond() * 0.005f);

Change the 0.003 or the 0.005 to a lower number, but again a positive number.

[ViRGE]

(04-06-2010, 10:59 AM)skid Wrote: I had a look into this area of the code recently and can give you a couple tips if you are able to compile your own builds of Dolphin. Neither of the settings are changeable via the GUI.

I have all the compile tools I need, so I should be able to roll my own build. I'll look in to that when I get the chance, thanks.

[ViRGE]

Well I tried dinking with numBytesToRender, but it didn't significantly change things even at very small values. There must be something else about the DSound backend that gives it such a high latency.

While I was at it, I took at look at OpenALStream.h and changed OAL_NUM_BUFFERS from 16 to 8 for the heck of it. Strangely enough it stopped the OpenAL crashing, although there are still pops in the audio. I don't know if Dolphin was creating too many buffers for the X-Fi to handle or what.

[skid]

Did you try the second adjustment above (DSP_PERIOD)?

Apart from that, I do not see any other settings that can be adjusted in the emulator for this area. Maybe there is inherent latency in the DirectX driver/library itself.

The OAL_NUM_BUFFERS change is your best bet so far. Pops in the audio are pretty unavoidable without introducing latency at this stage. This is because Dolphin does not contain code that smooths out the audio output.

[ViRGE]

(04-07-2010, 12:39 PM)skid Wrote: Did you try the second adjustment above (DSP_PERIOD)?

Yes, I did. You were right about one thing: it's the fastest way to get to a crash.

[ViRGE]

Just to respond to myself, I finally found the cause of my OpenAL issues: I had Lock Threads To Cores enabled.

Since I'm on an i7 system this ended up being a terrible thing since Dolphin locks to virtual cores 0 and 1, which happen to be Hyperthreading pairs that are sharing the same execution resources. For whatever reason OpenAL suffered greatly for this, and this is what caused my popping and instability. Once I disabled Lock Threads To Cores, all of my OpenAL problems stopped. It's improved my Dolphin experience immensely.

[FloW3184]

just turn off this stupid "hyperthreading" in your bios and dolphin will run with an extra-speed that should be even higher than the speedup you already noticed by now.
you would not need any framskipping at all anymore.
(fullspeed with sound)

this also happens to most normal games on your mashine.
you will have a speedup and higher min-fps.