• The purpose of this β-release is to provide a re-organized YASAP/NT buffer more suitable for gapless playback.
• Now just non-destructive operations are performed while writing to YASAPI/NT's buffer, i.e.
  • the bit depth is always extended to 32 bit by padding 0 bits, and
  • channel duplication when Mono2Stereo is enabled.
• All potential destructive operations such as
  • reducing bit depth, or
  • volume control
  are performed while reading from YASAPI/NT's buffer (and writing to WASAPI's buffer.)
• In Configuration dialog the new buffer organization is mirrored as follows:
  M4_IMG(../images/2.2.0-beta1/yasapi,67) M4_IMG(../images/2.2.0-beta1/monitor,67)
• BTW:
  • On 2018-01-01 the Lovely Parasite  on his blog announced:
    M4_IMG(../images/parasite-announcement/18-01-01/announcement,67)
  • On 2018-06-25 he cancelled the announcement:
    M4_IMG(../images/parasite-announcement/18-06-25/announcement-1,67)
  • Instead that day he announced:
    M4_IMG(../images/parasite-announcement/18-06-25/announcement-2,67)
  • Because he's not shy that exact same day he also announced that he's not working on the Winamp wrapper anymore he likes to call WACUP but on something else:
    M4_IMG(../images/parasite-announcement/18-06-25/announcement-3,67)
  • Parasite, when we'll see a real product rather then some vaporware?
    M4_IMG(../images/parasite-announcement/18-08-08/vaporware,67)
    To us the only reason for coming up with one vaporware after the other (cf. also below) seems to be milking out some shekels from your naïve believers!

• Allmost the same as v2.1.0-β₆ except some code cleanup.
• Next steps might be:
  • v2.2.0-β₁  Reorganization of YASAPI/NT's buffer in order that it better suits gapless playback.
  • v2.2.0-β₂  Gapless playback.

• From the Lovely Parasite 's Twitter account:
  M4_IMG(../images/twitter/parasite-180704,67)
• As Twitter user Jeremy King puts it (including another spooky remark by the Lovely Parasite ):
  M4_IMG(../images/twitter/parasite-180705-1,67)
  M4_IMG(../images/twitter/parasite-180705-2,67)
• Twitter user Daria comments:
  M4_IMG(../images/twitter/parasite-180705-3,67)
• Twitter user J.R. Raith with a fine irony regarding the Lovely Parasite 's abilties:
  M4_IMG(../images/twitter/parasite-180705-4,67)

• Fixed a subtle bug with Dithering.
• Restructured time reporting functions, i.e. getwrittentime() and getoutputtime().

• Introduced Dithering:
  M4_IMG(../images/2.1.0-beta5/common,67)
• You might ask yourself what Dithering is:
  • First of all: Dithering makes only sense when reducing bit depth, say from 32 to 24 or 16 bits. Otherwise simply 0-bits will be padded.
  • When throwing away bits you might think a moment on how doing it. What next comes to mind is Rounding.
  • You might view Dithering as a generalized form of Rounding. When Rounding a constant value of half of the number of bits to throw away all set is added before shifting to the right by the number of bits to throw away (that way actually throwing them away.) Dithering generalizes this approach by not just adding a constant value but a value over time fluctuating from 0 to the number of bits to throw away before shifting to the right. This randomized version of Rounding is aimed to break interference pattern known as quantization noise.
  • Currently YASAPI/NT implements a simple Dithering algorithm (without noise shaping) following the idea sketched at https://www.kvraudio.com/forum/viewtopic.php?t=132643 under consideration of http://c-faq.com/lib/randrange.html.
• Please note that this is also Поднятая целина. Not a single prior (or hijacked) version of the plug-in is supports Dithering.

• Introduced support of Volume Control for Exclusive Mode playback due to WASAPI interface IAudioEndpointVolume (once scheduled as v2.1-β₃).
• Interface IAudioEndpointVolume is ab bit more special than Interface ISimpleAudioVolume because there must be hardware support for volume control.
• YASPI/NT tests whether there is hardware support for volume control by means of the IAudioEndpointVolume::QueryHardwareSupport method. If not it falls back to it's own software solution as is illustrated by the following images:
  M4_IMG(../images/2.1.0-beta4/monitor-active,67) M4_IMG(../images/2.1.0-beta4/monitor-fallback,67)
  The image on the left hand side shows a device with hardware support wheras the image on the right hand side shows one without.
• Please note that this as well is Поднятая целина. Not a single prior (or hijacked) version of the plug-in is supporting WASAPI interface IAudioEndpointVolume.

• The next regular update once scheduled as v2.1.0-β₂ introducing support of Volume Control for Shared Mode playback by means of WASAPI interface ISimpleAudioVolume.
• Replaced check box Volume Control by a respective combo box:
  M4_IMG(../images/2.1.0-beta3/common,67) M4_IMG(../images/2.1.0-beta3/monitor,67)
  The combo box offers the following entries:
  • Off  corresponds to the former check box being unchecked, i.e. no Volume Control at all,
  • YASAPI/NT  corresponds to the former check box being checked, i.e. Volume Control by means of a simple software algorithm provided by YASAPI/NT,
  • WASAPI  correspons to Volume Control depending on what is chosen by means of check box Mode, i.e.
    • when Shared  by means of WASAPI interface ISimpleAudioVolume,
    • when Exclusive  potentially (propably with the next β-release) by means of WASAPI interface IAudioEndpointVolume (with this β-release just by the software algorithm provided by YASAPI/NT).
    • What YASAPI/NT really applies is displayed at Monitor page.
• Please note that this is Поднятая целина. Not a single prior (or hijacked) version of the plug-in is supporting WASAPI interface ISimpleAudioVolume.

• This is an irregular update. Hence no new features. Just re-compiled with the new GTK+ runtime v180518-1351 depending now on zlib1.
• Created NSIS installers with GTK+ bundled because they might be preferable for some casual user over dealing with a second download and installation.
• BTW: Prior (and most likely as well hijacked) versions of the plug-in crash when used with Double Buffered mode, i.e. with Exclusive Pulled mode:
  M4_IMG(../images/misc/crash,67)
  Please note that versions 2.0.0-β₁+ have NOTHING IN COMMON with prior (or hijacked) versions (except part of the brand and of course some ideas). That's essential YASAPI/NT vs. YASAPI.

• With this β-release check box Volume Control is enabled:
  M4_IMG(../images/2.1.0-beta1/common,67)
• When checked, volume control due to a simple algorithm implemented by YASAPI/NT is enabled (i.e. no dithering nor accessing WASAPI interfaces.)
• Different to prior (or hijacked) versions of the plug-in the algorithm is applied when reading from YASAP/NT's buffer and writing to WASAPI's buffer. (Prior - or hijacked - versions of the plug-in did it when writing to the plug-in's buffer.) You'll immediately notice the difference: now there's practically no latency when moving Winamp's volume slider.
• What is chosen by means of Volume Control is reported on the Monitor page:
  M4_IMG(../images/2.1.0-beta1/monitor-volume-disabled,67) M4_IMG(../images/2.1.0-beta1/monitor-volume-enabled,67)
• The Lovely Parasite  on his WEB site with time stamp 2016-12-29 02:22 has published an updated version of the Winamp SDK expressing his Herrschaftswissen (might be translated by domination knowledge):
  M4_IMG(../images/2.1.0-beta1/winamp-sdk,67)
  We mention that because from it we've learned something interesting being valid just for Winamp 5.64+. You might consider this a prerequisite for this β-release and all what follows. We'll not going to C-include those header files but make deliberately use of what we've learned (starting with this β-release.)
• BTW: We're not certain on whether Winamp's current owner, Radionomy, is amused on the Lovely Parasite 's effort. As it seems way back already in late 2016 the Lovely Parasite  was forced by means of a legal complaint due to Radionomy to deliver the following statement along with changing its effort's URL:
  M4_IMG(../images/2.1.0-beta1/parasite-statement,67)

• Essentially the same as v2.0.0-β₁0 except some minor changes, of course:
  • At last minute we've changed writing YASAPI NT to YASAPI/NT (with a slash). In order to avoid too much slashes it now reads YASAPI/NT Output v2.0.0 (msc) or YASAPI/NT Output v2.0.0 (gcc), respectively, i.e. the compiler used is appended within braces.
  • Upgraded from Visual Studio Express 2012 to Visual Studio Express 2013 resulting in a minor updated msc version: from 18.00.3201 (cf. below) to 18.00.40629:
    M4_IMG(../images/2.0.0/versions,67)
    After all we don't use Visual Studio anyway except two command line tools out of the bunch:
    1. the C compiler cl.exe, and
    2. the library manager lib.exe.
• Please note that the first of the below mentioned limitations is already removed, i.e. format (mono to stereo and bit depth) conversions are yet available.
• This milestone should provide a basis solid enough for moving on.
• The next milestone will be v2.1.0 Volume Control (cf. milestones.) Our goal is not just provide some simple software solution but also support the ISimpleAudioVolume (for Shared Mode playback) and the IAudioEndpointVolume (for Exclusive Mode playback) WASAPI interfaces.
• Hence next we'll have the following refined targets:
  • v2.1.0-β₁:  Volume Control by means of software provided by YASAPI/NT,
  • v2.1.0-β₂:  Volume Control for Shared Mode playback supporting the WASAPI ISimpleAudioVolume interface, and
  • v2.1.0-β₃:  Volume Control for Exclusive Mode playback supporting the WASAPI IAudioEndpointVolume interface.

• Following is the perfect answer to the question from the Lovely Parasite 's forum: Post (Oct 21, 2017) taken from the guru3D forums makes the essential point (although the guy seem to mix up WASAPI with ASIO and that one should fall back on Shared Mode only if Exclusive Mode for some reason does not work. Only in case Shared Mode is used with the same format configured with Control Panel → Hardware and Sound → Sound → Playback → Device → Properties there should be no difference to Exclusive Mode):
  M4_IMG(../images/forums/guru3d,67)
  This guy apart each theory experienced the huge potential w.r.t audio reproduction each PC has due to WASAPI. The only thing YASAPI/NT adds is to make this potential available to Winamp users.
• Tip: We're digitally connecting our PC to the amplifier by using an inexpensive WASAPI enabled USB to coaxial/TOS adapter and that way using the quality DAC build-in to our amplifier in order to convert from the digital to the analog domain. (We've ripped our CD collection into loudenss normalized FLACs - most importantly a lossess format - and like listening to it in Winamp random mode.)

• Just discovered that the combo box advertised with v2.0.0-β₆ was disabled. Now it should be fixed.
• Worked on Pause again.

• We have the impression that the remaining quirks can as well be observed with the standard DirectSound output. Anyway, you shouldn't hit the Pause button too frequent with no time left in between.
• While looking at Pause we came through another obstacle: Disconnect when Pause. This feature was fully implemented all the time but was disabled because it didn't work with Double Buffered mode we're focussed on these days. With this mode and the option disabled the plug-in got immediatly stucked when un-pausing, i.e. the plug-in's IAudioClient seemed not to start again after having been stopped. This morning we had the right idea to finally resolve the issue: When in Double Buffered mode it's not sufficient to just stop the IAudioClient but it also needs to be reset. Hence the Disconnect when Pause feature is back again (also when in Double Buffered mode, i.e. Pulled Exclusive mode):
  M4_IMG(../images/2.0.0-beta8/common,67)

• Implemented Bit Depth conversions:
  M4_IMG(../images/2.0.0-beta6/yasapi,67)
• In case you try to convert to a format not supported by your device you might get an error like
  M4_IMG(../images/2.0.0-beta6/error-initialize,67)
  When getting such an error you should cross check Configuration → Explore.
• This might become v2.0.0.
• Our further plans are
  • v2.1.0:  volume control, and
  • v2.2.0:  gapless playback.

• Our preferred mode using this plug-in is double buffered, i.e. exclusive pulled. With this mode we sometimes observed that the plug-in got stucked. As a source of this strange behaviour we identified an underflow of the plug-in's buffer.
• Our solution is in such a case sending silence to WASAPI instead of reading from the plug-in's buffer and reporting the incident by means of Dropout counters under Configure → Monitor:
  M4_IMG(../images/2.0.0-beta5/monitor,67)
• A rule of thumb for configuring the plug-in: Make the buffer as small as possible but not that small that dropouts occur.
• Introduced preprocessing this WEB page by means of the m4 macro processor allowing for a much more flexible way of editing.

• From the
  M4_IMG(../images/wa-forum,67)
• From the the Lovely Parasite 's forum:
  M4_IMG(../images/parasite-04,67)
• Who are those people prefering inferior products just for political reasons? Obviously they like being replaced by an uncivilized "people" with an IQ of about 70. Anyway, we're not.
• We doubt that people attracted by the Lovely Parasite  know what WASAPI really is. It could be that the Lovely Parasite  itself does not. We're convinced that they're satisfied by anything labelled "WASAPI" without asking any further question what's below the hoot. They shood stick with DS, really:
  M4_IMG(../images/parasite-05,67)

• We've uploaded the (hopefully) fixed version 180412-1003 of the latest GTK runtime.
• The reason the prior attempt was broken was that under the hood of remaining fully binary compatible the good people from the GTK team created a dependency to libfribidi-0.dll we'd not packaged.
• In case you're interested in what the unsusual version numbers mean: They are constructed from the latest time stamp on MSYS2 of all files making up a complete runtime.
• You can view the real versions by means of About → Versions. As far as we can see this time libgtk hasn't changed at all and libglib has a minor (but incompatible!) change from 2.56.0 up to 2.56.1:
  M4_IMG(../images/yagtk-rt/180412-1003,67)
• We're now a step away from DepenencyWalker we once used to determine the DLLs needed (a tedious work we thought we're doing once and for all time) and started to create a shell script determining depencencies automatically by means of the commands strings in combination with grep (instead of DepenencyWalker).
• Thanks again Ralf!

• A user notified us by PM that the latest GTK runtime published on SourceForge is broken (it's not available any longer). Many thanks go out to Ralf!
• For now you should revert to the prior version 180403-0917 or stick to the expert approach.
• Sorry for any inconvenience.

• Introduced options for defining the positions in Z-order of the Configuration and About dialogs, respectively.
• Fixed saving the coordinates of dialogs in case they are not visible.
• Changed some identifiers which may have broken your configuration. Please double check.

• Added mono to stereo conversion.
• Slightly changed the semantics of the Cancel button.

M4_IMG(../images/2.0.0-beta1/thread,67)

M4_IMG(../images/2.0.0-beta1/dro,67)

• We're back again: This is a preview of what you might expect to come. It's re-written from scratch with several improvements, hence we called it new technology (NT). It's our attempt getting rid of annoying nasty parasites because we assume that those parasites are silly coders just being able to do some silly native win32 GUI coding based on drawn dialogs created with the help of some resource editor and hence we no longer provide a resource file.
• This NT version is superior to any prior version by any means and does let any prior version look just like a silly prototype:
  • Exclusive pulled (i.e. double bufferered) playback is fully supported.
  • In case of pushed playback a periodic timer may be utilized. This allows for a wonderful symmetric solution compared to pulled playback where no timer is needed at all and playback is triggered in high accuracy by the device itself.
  • Initialization of any resource is deferred until it actually is needed. This way the plug-in's footprint at Winamp start-up time is the lowest possible, i.e. you will not notice whether it is installed.
  • Avoided any instance of busy waiting. In any attempt to fall back on it substituted it by thread synchronization means, i.e. WaitFor[Single/Multiple]Object[s]()/SetEvent() or g_cond_wait()/g_cond_signal() functions, respectively.
• The GUI (i.e. the Configuration and About dialogs) were made from the great GTK+ toolkit.
• You might fear that building on Gtk+ might pose some overhead compared to a native Windows implementation:
  • This is, of course, true.
  • But you should note that this is constraint to GUI/configuration and not to playback.
  • As long as you don't make use of the GUI there is no difference to a plain Windows WASAPI implementation. WASAPI is, of course, 100% Windows and nothing else.
  • Loading the GTK+ DLLs in a Winamp session is deferred until the Config or About buttons, respectively, are hit for the first time. To give an impression on the overhead of loading the GTK+ DLLs we display a wait cursor during the time it takes. (Be warned and be patient, especially when GTK+ has to be loaded after re-booting your system!) Once the DLLs required for GTK+ are loaded there is no measurable difference between GTK+ and a native Windows GUI.
  • Last but not least please remember the above note: This was the perfect opportunity for me to dive into the world of GTK+ programming. The result is more than satisfying.
• This preview has the following limitations:
  • Format conversions (i.e. monto to stereo and bit depth conversions) are not implemented yet.
  • Volume control is not implemented yet.
  • Gapless playback is not implemented yet.
  • The documentation is not fully updated yet. (Updating might continue during the next days.) The documentation of previous versions is available here.

• https://sourceforge.net/projects/milkdrop2-compile/
• https://sourceforge.net/projects/milkdrop2-compile/files/milkdrop2-compile/

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.

• Added the section A Message Silently Disappearing from the Winamp Forums to this documentattion.
• Added the section Some Additional Notes Regarding the Parasite to this documentation.

• Parameterized the configure script that it may be useful for others as well (cf. the new section Compiling YASAPI from Source below). It now supportes the "./configure && make" cycle well known from UNIX/LINUX systems.
• Fixed the error introduced with the prior version that YASAPI does not play in pull mode (as reported to the WA forum)

• Updated my build machine from Vista to Windows 7 (good bye Vista users).
• Hence the new version is build using MSVC 11 / Windows SDK v7.1A (instead of the respective MSVC 10 / Windows SDK v7.0A under Vista.)
• Dropped the SSE2 versions because by using MSVC 11 they make no sense any longer.
• As usual, some code clean-up.

• Some final code clean-up before moving on.
• Development ist stalled again.

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 GREAT!

• Factored out a framework for simialr plug-ins.
• Connect to the device before continue playing after flush when in underflow.

• Disconnect on pause and undeflow when option Disconnect is choosen.
• Removed timer for disconnecting gapless sessions because it is not needed any longer.
• Fixed crashing of the configuration dialog in case the device selected in the previous session has meanwhile become invalid.

• For gapless mode it is configurable after which time interval the connection should be released when in idle state.
• Reworked the tracing facilities of the debug version.

• Stopping player when Winamp closes and not already stopped (needed for gapless mode).
• Guarding against locking zero sized device buffers.
• Reworked About dialog.

• Fixed AUDCLNT_E_BUFFER_SIZE_ERROR appearing in eclusive/pull mode.
• Fixed a potential forever-loop which may have appeared at the end of a track.
• Fixed crashing as client of the WinampMatrixMixer output plugin.

• Gapless playback.
• A common option for switching on/off gapless playback (disabled by default).
• A device option for choosing whether the time offset for gapless playback is maintained as a 64-bit integer value (representing the playback position) or as a 64-bit floating point value (representing the quotient taken from the playback position and a frequency). For a deeper understanding regarding position and frequency values you may refer to the documentation of the IAudioClock::GetPosition() and IAudioClock::GetFrequency() methods. We feel that as long as a constant frequency value can be assumed choosing the time offset as beeing maintained as a 64-bit integer value is preferable.
• A debug version for SSE2.

• The Default Device is listed in the respective configuration dialog's drop down box as an option to choose.
• In case the Default Device is choosen from the drop down box (and saved),
  • the configuration is saved for the physical device which was configured at the time (configuration time) as Default Device from Window's System Control when the configuration was loaded to the dialog,
  • each time a new track starts, the physical device configured at this time (play time) as Default Device from Window's System Control is used to play the track (please note that this device may differ from the one configured at configuration time).

• Detect end of track by respective "isplaying" request.
• Fixed bug regarding synchronization of Share Mode and Strategy options.

• Some minor code clean-up.
• Further development is stalled because according to the Winamp team they have developed a native WASAPI output plugin: "Benski has coded a new out_wasapi plug-in" and "itll probably be included with 5.8 beta"'.

• Guarded against writing when paused.
• Stopping audio client when underflow.
• From the configuration dialog, dropped the device list page in favour of a combobox on top of the dialog.
• Slightly adapted default values.

• Introduced an (by default enabled) option "Write Block" that in case the plugin's "write" method delivers more data than actually could be written to the ring buffer it should block and wait until enough data are consumed from it rather then returning immediately.
• For automatic mode, removed restrictions for switching from exclusive to shared mode.

• Reorganized the configuration dialog:
  • Focused again on the most important two (per device) parameters "Mode" (share/exclusive) and "Strategy" (push/pull).
  • Duplicated those two parameters from the "Device Options" page to the dialog's top-region.
  • Moved the former top-region parameters to a new "General" tab-control page.
  • Added a "Store" button with similar functionality as the "OK" button except that it doesn't close the dialog.
• Fixed several bugs.

• Reorganized configuration of device period.
• Added progess bars to the configuration dialog in order to visualize the load of the ring and the shared buffers.
• Added an option for dis-/enabling the visualization.
• Added an (experimental) function for balancing the shared buffer.
• Added some more tracing to the debug version.
• Split the verbose debugging into verbose level 1 ond and level 2 (even more verbose).

• Added an option for configuring whether calculation of the buffer sizes should be based on the default or on the minimum device period as proposed by WASAPI. Made default device period the default. So long the calculation was silently based on the minimum device period.
• Added tooltips to the configuration dialog's controls.

• Complete re-write based on a new architecture. The basic idea is to serialize all requests and dispatch them into just one worker thread. In particular the serialization takes into account asynchronous requests resulting from the WASAPI device.
• Round up ("ceil") the size of the ring buffer to the next multiple of Winamp's packet size (576 samples).
• Special treatment of double buffering, i.e. pull in exclusive mode.
• Additional options to configure the debug version.

• Improved thread synchronization during start-up.
• Fixed a bug regarding recovery from error AUDCLNT_E_BUFFER_SIZE_NOT_ALIGNED of the IAudioClient::Initialize() method.

• Implemented recovery from error AUDCLNT_E_BUFFER_SIZE_NOT_ALIGNED of the IAudioClient::Initialize() method (cf. remarks section from MSDN documentation).
• Added support for KSAUDIO_SPEAKER_7POINT1.

• Improved synchronization with visualizations and video because of
  • corrected calculation of max latency and
  • corrected calculation of "written time".
• Dropped "written time" options.
• Dropped the call to IAudioClient::IsFormatSupported().
• New device specific options "Auto Convert PCM" and "SRC Default Quality". These Options are only available in shared mode. They correspond to the AUDCLNT_STREAMFLAGS_AUTOCONVERTPCM and flags, respectively, of the IAudioClient::Initialize() method (regarding the AUDCLNT_STREAMFLAGS_SRC_DEFAULT_QUALITY flag cf. also here).

• Automatic re-sampling in shared mode seems to work now.
• Added an "Exit Winamp" option to the error message dialog box.

• Support for multiple devices.
• Configuration options per device.
• Various fixes.

• Utilization of the IAudioClock interface instead of the GetTickCount() or the timeGetTime() functions for reporting the elapsed time to Winamp.
• Option for controlling whether "written time" should be calculated.

• Option for treating mono as stero (default switched on).
• New default options for buffer configuration.
• Some fixes.

• Support for pull strategy.
• Support for volume control.

• Component Object Model (COM) error messages are displayed with the file and the line number where they occur.
• Compiled with shared "MSVCR110.DLL" (instead of static as before).

• Improved configuration for buffer sizes.
• Provided a SSE2 version.
• Compiled with the C compiler from "Visual Studio 10 Express" (instead of "Visual Studio 9 Express" as before).