[Wine] RFC: New dependency on FFmpeg?

Andrew Eikum aeikum at codeweavers.com
Thu Aug 20 14:47:06 CDT 2015

I have a working implementation of the new xaudio2 API in my tree.
Microsoft is treating it as a replacement for dsound[1], and as a
result, this new API is used by lots of recent games; see Bug
26808[2] for some examples.

Most games that use the xaudio2 API use a version of Microsoft's WMA
codec. Wine doesn't currently have the ability to decode this audio
for playback. In order for the xaudio2 implementation to be useful for
most games, we'll need some way to convert it. I chose to use the
FFmpeg library to decode WMA audio.

This means for most games, Wine's built-in xaudio2 will require that
the 32-bit FFmpeg library be available on the system to successfully
play audio.

The new code only uses the audio decoding features of FFmpeg,
specifically linking only against libavcodec and libavutil. The newest
APIs that we use were introduced in 2013. Most of the rest date from
2011 and a few from 2002. FFmpeg's API isn't stable, but I don't
expect much maintenance burden from the small piece that we're using.

An additional complication is the libav fork. The APIs that we're
using are currently unchanged between FFmpeg and libav, so libav
should function as a drop-in replacement. Further, distros seem to be
migrating back to FFmpeg, if they ever changed. So again, I don't
expect this to be a barrier.

Wine packagers and developers, do you have any thoughts or objections
to depending on FFmpeg/libav's libavutils and libavcodec for xaudio2

[1] https://msdn.microsoft.com/en-us/library/windows/desktop/ee415813%28v=vs.85%29.aspx

[2] https://bugs.winehq.org/show_bug.cgi?id=26808


More information about the wine-users mailing list