[Bug 29585] wineoss.drv audio renderer not on par with others

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=29585

--- Comment #44 from Jörg Höhle <hoehle at users.sourceforge.net> 2012-03-06 03:54:35 CST ---
>does that patch need to be applied with some other patches.
No.  You can add the one about audible 16bit sine in the render test.

Please summarize your current situation.
- Crackling with render tests? with/without vmix?
- What do the apps you name use? DSound? XAudio2? Winmm? Other?

DSound suffers from other issues and can cause crackling in scenarios with
small buffer sizes because it does not sync well with mmdevapi.  That's why
it's important to distinguish crackling from DSound vs. w7/XAudio2 apps.
One good news is that DSound doesn't care about missing floating point in
mmdevapi because DSound apps typically use 8 or 16bit output.

>underruns still occur.
Please be more precise.  Occasional or continuous?

The patch is no protection against clock skew.  I expect occasional underruns
in the XAudio2 scenario should the audio device consume frames faster that the
system's clock idea of 48000fps.  This should be visible in the logs as a slow
decrease of *average* padding in the buffer.

>Running mmdeavapi render tests produces audible sine waves, but when the
>vmix is disabled the output often becomes not clear.
My beliefs about your situation are:
- with vmix: render & XAudio & winmm app sound is ok, without crackling;
- w/o vmix: "output not clear" - origin unknown
- DSound apps can suffer from crackling (several per second).
What's right and what is wrong?

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.