Yet Another (WA)SAPI Output Plugin for Winamp (YASAPI)

The "Yet Another (WA)SAPI Output Plugin for Winamp" (YASAPI) utilizes the "Windows Audio Session API" (WASAPI). WASAPI's exclusive mode for rendering audio is a native way on Windows to render audio undisturbed, similar to Steinberg's "Audio Stream Input/Output" (ASIO). The YASAPI output plugin may serve as a replacement for any other Winamp output plugin.

Nanos gigantum humeris insidentes: This project is dedicated to my European heritage. It is strictly to be understood as a statement against the "sweet" liberal lie of "multiculturalism" which is going to destroy Europe as we know it, in particular against the Merkel regime selling out Europe for nothing as we watch.

PLEASE NOTE THAT THIS PROJECT IS AN EXPERIMENTAL RATHER THEN AN INDUSTRIAL STRENGTH EFFORT. THIS PROJECT IS NOT FOR YOU. IT IS FOR ME IN ORDER TO LEARN SOMETHING. IF THERE IS SOMETHING ALONG THE WAY I CAN DO FOR YOU THAT'S FINE.

Home:		http://out-yasapi.sourceforge.net/
Project:		http://sourceforge.net/projects/out-yasapi/
Download:		http://sourceforge.net/projects/out-yasapi/files/out-yasapi/out_yasapi-nt
Winamp Forum:		http://forums.winamp.com/showthread.php?t=380396 (discontinued)
Input Plugin:		http://in-ffsox.sourceforge.net/
Loudness Normalization:		http://bs1770gain.sourceforge.net/
		http://r128gain.sourceforge.net/
Keep HDD Awake:		http://gen-hdd.sourceforge.net/
Yet Another Shuffle:		http://gen-yas.sourceforge.net/

Content

1. History
2. Introduction
3. Implementation
4. Configuration
5. Debug
6. Compiling YASAPI from Source
7. Message silently disappearing from the Winamp forums
8. Some Additional Notes on Darren Owen ("DrO")

The Core Audio APIs were introduced in Windows Vista. This is a new set of user-mode audio components provides client applications with improved audio capabilities. These capabilities include the following:

• Low-latency, glitch-resilient audio streaming.
• Improved reliability (many audio functions have moved from kernel mode to user mode).
• Improved security (processing of protected audio content takes place in a secure, lower-privilege process).
• Assignment of particular system-wide roles (console, multimedia, and communications) to individual audio devices.
• Software abstraction of the audio endpoint devices (for example, speakers, headphones, and microphones) that the user manipulates directly.

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

Of special interest is that there is an exclusive mode for rendering audio, i.e. there is a mode where an application has exclusive access to the audio device without being disturbed by third parties.

The aim of the YASAPI plugin is to make the WASAPI exclusive mode for audio rendering available to the users of Winamp.

The name of the plugin was choosen because there are already at least two WASAPI output plugins for Winamp:

• Maiko WASAPI output plugin
• adionSoft Winamp WASAPI Output Plugin

The implementation on the WASAPI side follows along the lines of an example provided by Microsoft. The startegy shown in this example is not only applicable for shared mode streams but also for exclusive mode ones, i.e. not the share mode should be emphasized but what is known as the push model. There is also an example demonstrating the pull model in conjunction with the exclusive mode. In that sence there are four strategies:

• push exclusive,
• push shared,
• plull exclusive, and
• plull shared.

The YASAPI plugin implements the first two strategies, i.e. the ones based on the push model.

The push model, in principle, works as follows:

1. Query the size of the buffer shared with the audio device.
2. Fill in completety the buffer shared with the audio device.
3. Start playing.
4. Loop until the track is played:
   1. Sleep half of the time corresponding to the size of the buffer shared with the audio device.
   2. Into the buffer shared with the audio device, fill in the gap which was growing free by playing during sleep.
5. Sleep until the possibly remaining filled rest of the buffer shared with the audio device was played.
6. Stop playing.

The YASAPI plugin decouples the two sides by means of a ring or circular buffer. That way,

• Winamp can luckily write to the ring buffer whenever it likes without caring about WASAPI, and
• WASAPI can luckily read from the ring buffer and write to the audio device wehenever it likes without caring about Winamp.

According to step 2 of the push model sketched above, it shoud become clear that the ring buffer should be at least as large (or larger) as the buffer the plugin's WASAPI component shares with the audio device.

4. Configuration

The YASAPI plugin comes with a configuration dialog which is described in the following. The dialog's top region presents the two most important parameters "Mode" (exclusive or share) and "Strategy" (push or pull)

Below those two parameters you find a tab-control consisting of four pages,

• a page for setting general (i.e. non device dependent) parameters,
• a page for choosing the device, and
• two pages for setting per device parameters.

The tab-control's first page looks as follows:

It let's you configure

• whether mono should be treated as stereo (i.e. the one mono channel should be duplicated),
• whether Winamp's volume control should be enabled, and
• whether the IAudioClock interface (WASAPI) or the GetTickCount function (System) should be used for synchronizing with Winamp.

On the next page there are the following per device options:

• the share mode, either exlusive, shared or automatic (automatic is similar to exclusive, except in case exclusive fails it falls back to shared), in case shared or automatic mode is choosen
  • whether the audio should be automatically re-sampled,
  • whether a more accurate re-sampling algorithmen should be applied, and finally
• the strategy, either push or pull.

On the final page you can configure the following per device buffer sizes:

• the duration of the buffer shared with the audio device (device period),
• the size of the ring buffer which should be a (small) multiple of the buffer the plugin's WASAPI component shares with the audio device, and
• the number of samples which should be available in the ring buffer before playing starts.

From the above sketch of the push model it shold be clear that the following relation holds (which is enforced by the configuration dialog):

minimum size of the buffer shared with the device (provided by WASAPI) <= size of buffer shared with the device <= number of samples in the ring buffer before start playing <= size of ring buffer

Please note that no option takes effect before hitting the OK button.

5. Debug

In case something went wrong you may be interested in some more information. In order to utilize this there is a debug version of the plugin (distinguished by a lower case "d" at the and of the name, i.e. out_yasapid.dll) available from the download site.

Do the following:

1. Close Winamp.
2. Copy "out_yasapi-debug.dll" to Winamp's "Plugin" folder.
3. Start Winamp.
4. A console window should pop up tracing the initialiazation of the debug YASAPI plugin.
5. From Winamps's preferences dialog choose "out_yasapi-debug.dll" as output plugin.
6. When playing tracks in Winamp, the debug YASAPI plugin traces initialization and cleanup of each track.
7. When shutting down Winamp, the cleanup of the YASAPI debug plugin is traced.
8. After closing Winamp, the console window remains visible for another 5 s before vanishing.

The debug console.

You can get rid of the debug console by choosing the respective "Console" option from the debug YASAPI plugin's configuration dialog:

The following debug options can be configured:

• whether the debug console is switched Off or on and displaying a trace in Default or Verbose mode, and
• how long closing the debug console should be delayed from closing Winamp.

• Microsoft Visual C
• Microsoft Windows SDK
• You get both, Microsoft Visual C, and Microsoft Windows SDK, in one batch by installing Visual Studio Community 2013 (That's what I did: Please note that it is best to disable all options before installation. That may be not true for Visual Studio Community 2015, which seems to install by default all the "visual experience" bload, but not the traditional C stuff, which you first have to opt for.)
• The MSys2 environment: For installation refer to http://msys2.github.io/ and https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/)
• Inside Msys2:
  • wget (command for installation: pacman -S wget)
  • tar (command for installation: pacman -S tar)
  • make (command for installing: pacman -S make)
• The Winamp SDK: Refer to http://forums.winamp.com/showthread.php?t=252090.
• NSIS (in case you plan to run make release: Refer to https://sourceforge.net/projects/nsis/.

5.1 The Build Proceudure

After having installed the prerequites you can build YASAPI. In MSys2 proceed as follows:

1. By means of wget, download the source code from Sourceforge https://sourceforge.net/projects/out-yasapi/files/out-yasapi/1.7.25/out_yasapi-1.7.25-src.tar.gz/download and save it as out_yasapi-1.7.25-src.tar.gz (option -O to wget):

   $ wget -O out_yasapi-1.7.25-src.tar.gz 'https://sourceforge.net/projects/out-yasapi/files/out-yasapi/1.7.25/out_yasapi-1.7.25-src.tar.gz/download'
   --2016-08-06 11:08:31--  https://sourceforge.net/projects/out-yasapi/files/out-yasapi/1.7.25/out_yasapi-1.7.25-src.tar.gz/download
   Resolving sourceforge.net (sourceforge.net)... 216.34.181.60
   Connecting to sourceforge.net (sourceforge.net)|216.34.181.60|:443... connected.
   HTTP request sent, awaiting response... 302 Found
   Location: http://downloads.sourceforge.net/project/out-yasapi/out-yasapi/1.7.25/out_yasapi-1.7.25-src.tar.gz?r=&ts=1470474523&use_mirror=vorboss [following]
   --2016-08-06 11:08:32--  http://downloads.sourceforge.net/project/out-yasapi/out-yasapi/1.7.25/out_yasapi-1.7.25-src.tar.gz?r=&ts=1470474523&use_mirror=vorboss
   Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59
   Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80... connected.
   HTTP request sent, awaiting response... 302 Found
   Location: http://vorboss.dl.sourceforge.net/project/out-yasapi/out-yasapi/1.7.25/out_yasapi-1.7.25-src.tar.gz [following]
   --2016-08-06 11:08:32--  http://vorboss.dl.sourceforge.net/project/out-yasapi/out-yasapi/1.7.25/out_yasapi-1.7.25-src.tar.gz
   Resolving vorboss.dl.sourceforge.net (vorboss.dl.sourceforge.net)... 5.10.152.194
   Connecting to vorboss.dl.sourceforge.net (vorboss.dl.sourceforge.net)|5.10.152.194|:80... connected.
   HTTP request sent, awaiting response... 200 OK
   Length: 309772 (303K) [application/x-gzip]
   Saving to: 'out_yasapi-1.7.25-src.tar.gz'
   
   out_yasapi-1.7.25-src.tar.gz  100%[=================================================>] 302.51K  1.10MB/s    in 0.3s
   
   2016-08-06 11:08:33 (1.10 MB/s) - 'out_yasapi-1.7.25-src.tar.gz' saved [309772/309772]
   

2. By means of tar, extract the gzipped TAR archive:

   $ tar xfv out_yasapi-1.7.25-src.tar.gz
   out_yasapi-1.7.25/COPYING
   out_yasapi-1.7.25/bits
   out_yasapi-1.7.25/configure
   out_yasapi-1.7.25/Makefile
   out_yasapi-1.7.25/out_yasapi/
   out_yasapi-1.7.25/out_yasapi/configure
   out_yasapi-1.7.25/out_yasapi/COPYING
   out_yasapi-1.7.25/out_yasapi/doc/
   out_yasapi-1.7.25/out_yasapi/doc/css/
   out_yasapi-1.7.25/out_yasapi/doc/css/styles.css
   out_yasapi-1.7.25/out_yasapi/doc/images/
   out_yasapi-1.7.25/out_yasapi/doc/images/config-1.jpg
   out_yasapi-1.7.25/out_yasapi/doc/images/config-2.jpg
   out_yasapi-1.7.25/out_yasapi/doc/images/config-3.jpg
   out_yasapi-1.7.25/out_yasapi/doc/images/config-debug.jpg
   out_yasapi-1.7.25/out_yasapi/doc/images/debug.jpg
   out_yasapi-1.7.25/out_yasapi/doc/index.html
   out_yasapi-1.7.25/out_yasapi/guid.cpp
   out_yasapi-1.7.25/out_yasapi/Makefile
   out_yasapi-1.7.25/out_yasapi/model.c
   out_yasapi-1.7.25/out_yasapi/out_yasapi.c
   out_yasapi-1.7.25/out_yasapi/out_yasapi.nsi
   out_yasapi-1.7.25/out_yasapi/rc/
   out_yasapi-1.7.25/out_yasapi/rc/manifest.xml
   out_yasapi-1.7.25/out_yasapi/rc/resources.h
   out_yasapi-1.7.25/out_yasapi/rc/resources.rc
   out_yasapi-1.7.25/out_yasapi/version.mak
   out_yasapi-1.7.25/out_yasapi/yasapi.h
   out_yasapi-1.7.25/out_yasapi/yasapi_about.c
   out_yasapi-1.7.25/out_yasapi/yasapi_config.c
   out_yasapi-1.7.25/out_yasapi/yasapi_connect.c
   out_yasapi-1.7.25/out_yasapi/yasapi_control_list.c
   out_yasapi-1.7.25/out_yasapi/yasapi_device.c
   out_yasapi-1.7.25/out_yasapi/yasapi_disconnect.c
   out_yasapi-1.7.25/out_yasapi/yasapi_guid.c
   out_yasapi-1.7.25/out_yasapi/yasapi_guid.h
   out_yasapi-1.7.25/out_yasapi/yasapi_kill.c
   out_yasapi-1.7.25/out_yasapi/yasapi_notify.c
   out_yasapi-1.7.25/out_yasapi/yasapi_options_common.c
   out_yasapi-1.7.25/out_yasapi/yasapi_options_device.c
   out_yasapi-1.7.25/out_yasapi/yasapi_player.c
   out_yasapi-1.7.25/out_yasapi/yasapi_ring.c
   out_yasapi-1.7.25/out_yasapi/yasapi_strategy.c
   out_yasapi-1.7.25/out_yasapi/yasapi_time.c
   out_yasapi-1.7.25/out_yasapi/yasapi_util.c
   out_yasapi-1.7.25/libya/
   out_yasapi-1.7.25/libya/configure
   out_yasapi-1.7.25/libya/COPYING
   out_yasapi-1.7.25/libya/COPYING.LESSER
   out_yasapi-1.7.25/libya/Makefile
   out_yasapi-1.7.25/libya/rules.mak
   out_yasapi-1.7.25/libya/str2wcscpy.c
   out_yasapi-1.7.25/libya/wc2cscpy.c
   out_yasapi-1.7.25/libya/wc2csdup.c
   out_yasapi-1.7.25/libya/wchar2char.c
   out_yasapi-1.7.25/libya/wcs2strcpy.c
   out_yasapi-1.7.25/libya/wcs2strdup.c
   out_yasapi-1.7.25/libya/ya.h
   out_yasapi-1.7.25/libya/ya_control.c
   out_yasapi-1.7.25/libya/ya_debug.c
   out_yasapi-1.7.25/libya/ya_dump.c
   out_yasapi-1.7.25/libya/ya_player.c
   out_yasapi-1.7.25/libya/ya_player_stub.c
   out_yasapi-1.7.25/libya/ya_property.c
   out_yasapi-1.7.25/libya/ya_queue.c
   out_yasapi-1.7.25/libya/ya_queue_read.c
   out_yasapi-1.7.25/libya/ya_queue_write.c
   out_yasapi-1.7.25/libya/ya_result.c
   out_yasapi-1.7.25/libya/ya_store.c
   out_yasapi-1.7.25/libya/ya_trace.c
   out_yasapi-1.7.25/libya/ya_util.c
   out_yasapi-1.7.25/libya/ya_wfxx.c
   

3. change into the directory out_yasapi-1.7.25 created by tar:

   $ cd out_yasapi-1.7.25
   

4. By maens of the configure script, configure how YASAPI should be build:
    
   1. In order to get an overview on the build options, call the configure script with the --help option:

      $ ./configure --help
      usage: ./configure <options>
      
      options (selection):
        --help: display this message
        '--with-msvs=<path to ms visual studio installation>'
            default: "C:/Program Files (x86)/Microsoft Visual Studio 12.0"
        '--with-mssdk=<path to ms windows sdk installation>'
            default: "C:/Program Files (x86)/Microsoft SDKs/Windows/v7.1A"
        '--with-wasdk=<path to winamp sdk installation>'
            default: "C:/Program Files (x86)/Winamp SDK"
        '--with-nsis=<path to nsis installation>'
            default: "C:/Program Files (x86)/NSIS"
        CPPFLAGS=<CPPFLAGS> flags passed to the C pre-processor
            (and the resource compiler)
            default: "-D_USING_V110_SDK71_"
        CFLAGS=<CFLAGS> flags passed to the C compiler
            default: "-MT -WX -O2"
      

   2. configure the build process using the default options and a prefix relative to the current directory (option --prefix to configure):

      $ ./configure "--prefix=$(PWD)"
      

   3. If you want e.g. to overwrite where the MS Windows SDK is located on your machine, enter a command along the lines of the following (in the path, use forward slashs):

      $ ./configure "--prefix=$(PWD)" "--with-mssdk=C:/Program Files (x86)/Microsoft SDKs/Windows/v7.1A"
      

5. By means of the make utility, build the application as configured:

   $ make
   CONFIGURE
   CONFIGURE
   MAKE    all
   make[1]: Entering directory '/d/MSys2/home/libya/X/out_yasapi-1.7.25/build/libya'
   CL      ya_player_stub.obj
   LIB     libya.lib(ya_player_stub.obj)
   CL      ya_player.obj
   LIB     libya.lib(ya_player.obj)
   CL      ya_control.obj
   LIB     libya.lib(ya_control.obj)
   CL      ya_queue.obj
   LIB     libya.lib(ya_queue.obj)
   CL      ya_queue_write.obj
   LIB     libya.lib(ya_queue_write.obj)
   CL      ya_queue_read.obj
   LIB     libya.lib(ya_queue_read.obj)
   CL      ya_store.obj
   LIB     libya.lib(ya_store.obj)
   CL      ya_result.obj
   LIB     libya.lib(ya_result.obj)
   CL      ya_property.obj
   LIB     libya.lib(ya_property.obj)
   CL      ya_wfxx.obj
   LIB     libya.lib(ya_wfxx.obj)
   CL      str2wcscpy.obj
   LIB     libya.lib(str2wcscpy.obj)
   CL      wcs2strcpy.obj
   LIB     libya.lib(wcs2strcpy.obj)
   CL      wcs2strdup.obj
   LIB     libya.lib(wcs2strdup.obj)
   CL      ya_util.obj
   LIB     libya.lib(ya_util.obj)
   CL      ya_trace.obj
   LIB     libya.lib(ya_trace.obj)
   CL      ya_dump.obj
   LIB     libya.lib(ya_dump.obj)
   CL      ya_debug.obj
   LIB     libya.lib(ya_debug.obj)
   CL      ya_player_stub-debug.obj
   LIB     libya-debug.lib(ya_player_stub-debug.obj)
   CL      ya_player-debug.obj
   LIB     libya-debug.lib(ya_player-debug.obj)
   CL      ya_control-debug.obj
   LIB     libya-debug.lib(ya_control-debug.obj)
   CL      ya_queue-debug.obj
   LIB     libya-debug.lib(ya_queue-debug.obj)
   CL      ya_queue_write-debug.obj
   LIB     libya-debug.lib(ya_queue_write-debug.obj)
   CL      ya_queue_read-debug.obj
   LIB     libya-debug.lib(ya_queue_read-debug.obj)
   CL      ya_store-debug.obj
   LIB     libya-debug.lib(ya_store-debug.obj)
   CL      ya_result-debug.obj
   LIB     libya-debug.lib(ya_result-debug.obj)
   CL      ya_property-debug.obj
   LIB     libya-debug.lib(ya_property-debug.obj)
   CL      ya_wfxx-debug.obj
   LIB     libya-debug.lib(ya_wfxx-debug.obj)
   CL      str2wcscpy-debug.obj
   LIB     libya-debug.lib(str2wcscpy-debug.obj)
   CL      wcs2strcpy-debug.obj
   LIB     libya-debug.lib(wcs2strcpy-debug.obj)
   CL      wcs2strdup-debug.obj
   LIB     libya-debug.lib(wcs2strdup-debug.obj)
   CL      ya_util-debug.obj
   LIB     libya-debug.lib(ya_util-debug.obj)
   CL      ya_trace-debug.obj
   LIB     libya-debug.lib(ya_trace-debug.obj)
   CL      ya_dump-debug.obj
   LIB     libya-debug.lib(ya_dump-debug.obj)
   CL      ya_debug-debug.obj
   LIB     libya-debug.lib(ya_debug-debug.obj)
   rm ya_property.obj str2wcscpy-debug.obj str2wcscpy.obj ya_store-debug.obj wcs2strcpy-debug.obj ya_player_stub-debug.obj ya_store.obj wcs2strdup.obj ya_player_stub.obj ya_debug-debug.obj ya_dump-debug.obj ya_debug.obj ya_queue_write-debug.obj ya_util-debug.obj ya_queue.obj ya_wfxx-debug.obj ya_queue_read-debug.obj ya_result-debug.obj ya_queue_write.obj wcs2strcpy.obj ya_util.obj ya_wfxx.obj wcs2strdup-debug.obj ya_control-debug.obj ya_queue_read.obj ya_player-debug.obj ya_control.obj ya_trace-debug.obj ya_player.obj ya_result.obj ya_trace.obj ya_queue-debug.obj ya_dump.obj ya_property-debug.obj
   make[1]: Leaving directory '/d/MSys2/home/libya/X/out_yasapi-1.7.25/build/libya'
   MAKE    install
   make[1]: Entering directory '/d/MSys2/home/libya/X/out_yasapi-1.7.25/build/libya'
   mkdir -p /usr/local/lib
   cp libya.lib /usr/local/lib/libya.lib
   mkdir -p /usr/local/lib
   cp libya-debug.lib /usr/local/lib/libya-debug.lib
   make[1]: Leaving directory '/d/MSys2/home/libya/X/out_yasapi-1.7.25/build/libya'
   MAKE    all
   cp /d/MSys2/home/libya/X/out_yasapi-1.7.25/out_yasapi/rc/resources.h resources.h
   CL      out_yasapi.obj
   SED     resources.rc
   cp /d/MSys2/home/libya/X/out_yasapi-1.7.25/out_yasapi/rc/manifest.xml manifest.xml
   RC      resources.res
   CL      yasapi_about.obj
   LIB     libyasapi.lib(yasapi_about.obj)
   CL      yasapi_config.obj
   LIB     libyasapi.lib(yasapi_config.obj)
   CL      yasapi_control_list.obj
   LIB     libyasapi.lib(yasapi_control_list.obj)
   CL      yasapi_notify.obj
   LIB     libyasapi.lib(yasapi_notify.obj)
   CL      yasapi_player.obj
   LIB     libyasapi.lib(yasapi_player.obj)
   CL      yasapi_connect.obj
   LIB     libyasapi.lib(yasapi_connect.obj)
   CL      yasapi_device.obj
   LIB     libyasapi.lib(yasapi_device.obj)
   CL      yasapi_disconnect.obj
   LIB     libyasapi.lib(yasapi_disconnect.obj)
   CL      yasapi_strategy.obj
   LIB     libyasapi.lib(yasapi_strategy.obj)
   CL      yasapi_kill.obj
   LIB     libyasapi.lib(yasapi_kill.obj)
   CL      yasapi_time.obj
   LIB     libyasapi.lib(yasapi_time.obj)
   CL      yasapi_options_device.obj
   LIB     libyasapi.lib(yasapi_options_device.obj)
   CL      yasapi_options_common.obj
   LIB     libyasapi.lib(yasapi_options_common.obj)
   CL      yasapi_ring.obj
   LIB     libyasapi.lib(yasapi_ring.obj)
   CL      yasapi_util.obj
   LIB     libyasapi.lib(yasapi_util.obj)
   CL      yasapi_guid.obj
   LIB     libyasapi.lib(yasapi_guid.obj)
   LINK    out_yasapi.dll
   CL      out_yasapi-debug.obj
   CL      yasapi_about-debug.obj
   LIB     libyasapi-debug.lib(yasapi_about-debug.obj)
   CL      yasapi_config-debug.obj
   LIB     libyasapi-debug.lib(yasapi_config-debug.obj)
   CL      yasapi_control_list-debug.obj
   LIB     libyasapi-debug.lib(yasapi_control_list-debug.obj)
   CL      yasapi_notify-debug.obj
   LIB     libyasapi-debug.lib(yasapi_notify-debug.obj)
   CL      yasapi_player-debug.obj
   LIB     libyasapi-debug.lib(yasapi_player-debug.obj)
   CL      yasapi_connect-debug.obj
   LIB     libyasapi-debug.lib(yasapi_connect-debug.obj)
   CL      yasapi_device-debug.obj
   LIB     libyasapi-debug.lib(yasapi_device-debug.obj)
   CL      yasapi_disconnect-debug.obj
   LIB     libyasapi-debug.lib(yasapi_disconnect-debug.obj)
   CL      yasapi_strategy-debug.obj
   LIB     libyasapi-debug.lib(yasapi_strategy-debug.obj)
   CL      yasapi_kill-debug.obj
   LIB     libyasapi-debug.lib(yasapi_kill-debug.obj)
   CL      yasapi_time-debug.obj
   LIB     libyasapi-debug.lib(yasapi_time-debug.obj)
   CL      yasapi_options_device-debug.obj
   LIB     libyasapi-debug.lib(yasapi_options_device-debug.obj)
   CL      yasapi_options_common-debug.obj
   LIB     libyasapi-debug.lib(yasapi_options_common-debug.obj)
   CL      yasapi_ring-debug.obj
   LIB     libyasapi-debug.lib(yasapi_ring-debug.obj)
   CL      yasapi_util-debug.obj
   LIB     libyasapi-debug.lib(yasapi_util-debug.obj)
   CL      yasapi_guid-debug.obj
   LIB     libyasapi-debug.lib(yasapi_guid-debug.obj)
   LINK    out_yasapi-debug.dll
   CL      guid.obj
   LINK    guid.exe
   CL      model.obj
   LINK    model.exe
   rm yasapi_notify-debug.obj yasapi_guid.obj yasapi_notify.obj yasapi_options_common-debug.obj yasapi_connect-debug.obj yasapi_control_list-debug.obj yasapi_options_common.obj yasapi_options_device-debug.obj yasapi_strategy.obj yasapi_kill.obj yasapi_connect.obj yasapi_control_list.obj yasapi_options_device.obj yasapi_config-debug.obj yasapi_util-debug.obj yasapi_kill-debug.obj yasapi_config.obj yasapi_device-debug.obj yasapi_about-debug.obj yasapi_util.obj yasapi_time-debug.obj yasapi_device.obj yasapi_about.obj yasapi_disconnect-debug.obj yasapi_player-debug.obj yasapi_time.obj yasapi_disconnect.obj yasapi_player.obj yasapi_strategy-debug.obj yasapi_ring-debug.obj yasapi_ring.obj yasapi_guid-debug.obj
   MAKE    all
   make[1]: Nothing to be done for 'all'.
   SED     out_yasapi.nsi
   

6. Finally, the plug-ins can be found at their build locations:

   $ find ./ -name "*.dll"
   ./build/out_yasapi/out_yasapi-debug.dll
   ./build/out_yasapi/out_yasapi.dll
   

The following message posted by me to the top-level (sticky) thread Winamp News in forum the Winamp Discussion forum silently isappeared without any comment:

Dear DJ Egg,

I'm not certain whether you are the right person to address my reqest.. I'm not even certain about who rules this forum. My impression is that you are the only one "official" left (i.e. one with a contract to the owners of Winamp). All the rest including this forum's moderators seem to be volunteers.

As you may have noticed, since some time I have a conflict with some of the former contractors of Winamp, "DrO", regarding the question of intellectual property. As it turns out, this former contractor, "DrO", disrespects intellectual property. He advertises a product he calls "Not So YASAPI Output Plug-in v1.0 Beta" which is a close to 100% clone of YASAPI cf. here for details)

As it turns out that at the blog of "DrO" some of his fanboys comment we know by their nicknames are frequent posters of this forum, among them some Pawel:

Could you please investigate whether this Pawel is identical to this forum's moderator with the same nickname and in case it turns out to be true fire him from his job as a moderator?

Thank you in advance and best regards,

Peter

7. Some Additional Notes on Darren Owen ("DrO")

On his blog Darren Owen ("DrO") claims:

The YASAPI plug-in is released under a license which allows for anyone to take the code and do with it as they please as long as any code codes (be that new or based on the existing source) is also provided.

That's of course true. And I'm the last one to have ever told something different. But if doing so, changing just a few lines of code out of about 20.000 just in order to rectify putting his name on the product I consider a clear case of plagiarism:

For further details refer to the Winamp forum.

The further explanations by Darren Owen ("DrO") are simply laughable:

So I'm now in a position where if I were to make my own WASAPI output plug-in, I'm almost certain he'd claim I was just plagiarising his work even if it was written from scratch as I've said that I'd already had a look at the available source code for his plug-in.

Darren, it's not your WASAPI plug-in, it's mine. Even with that little changes you've made you've perfectly demonstrated that you don't have the slightest idea on how this (my) plug-in is supposed to work and you've managed introducing a major bug into the configuration.