Last Updated: 22 February 2017
However much we try to do things correctly and implement bug free code that works as expected and wanted, some things may end up not meeting that. So the aim of this (hopefully) small document is to note all known issues within the Winamp Community Update Project (WACUP) which are either known about and are planned to be fixed at a later time or those that cannot be fixed due to fundamental issues preventing a fix (i.e. due to native Winamp code)
File Associations & Shell Integration Preferences
- The File Association & Shell handling preference features have been disabled from being configured in this build as well as the installer forcing the install to not make use of the registry. This has been done due to the replacement code for those features not working 100% correctly and so by disabling the preferences and registry access, it will prevent having issues initially.
- This is due to the complexity involved in overriding Winamp’s native handling in addition to directly including functionality that was provided by the JTFE plug-in (e.g. icon libraries) as a single solution.
- This is also complicated due to Windows 7 being different to how Windows 8.x / 10 require file associations to be handled (much to user annoyance) so by disabling all of this related functionality it’s possible to provide a beta build that generally works and for the initial testing will not mess with any existing Winamp installs (which is for the best).
Library Playlists Plug-in (ml_playlists.dll)
- Toggling the Preferences -> Media Library -> Options -> ‘Group the 'Play' and 'Enqueue' buttons into a single button’ option causes Winamp’s Media Library to reload the view (equivalent of changing to another library view and going back again). If the Library Playlists side view is enabled and a playlist was shown in the side view and ‘Remember the currently selected playlist in the side view’ option is unchecked (not default behaviour) then when the first library option is changed, the selected playlist will not be on reloading.
- This is a side-effect of how the library option works (forcing the view to be reloaded when the option changed was simpler than requiring additional per-plug-in hooks to allow for live updating of state).
- There is not a simple way to know if this situation is happening and so the only ‘fix’ is to re-select the desired playlist or to check the ‘Remember the currently selected playlist in the side view’ option.
- Sorting in the root library playlists view of the ‘External?’ column may not appear to be sorting in the correct order depending on the language being used and it’s equivalents of English’s ‘Yes’ and ‘No’ words
- The sorting is done by the playlist core service and uses the information associated with the playlists and is not based on the column text which if in the case that ‘Yes’ is alphabetically before ‘No’ in the language being used will cause the ordering to appear opposite of what might have been expected.
- The sorting is consistent in how it occurs irrespective of the visual issues from the language used with this column (which is provided to see if a library playlist is using the original external file or if it is making use of a Winamp managed copy of the original playlist at the time of being imported).
JTFE Main Playlist Queue Highlighting
- This feature isn’t currently working (i.e. showing a  next to a queued playlist item) but the queue behaviour should still be working
- This is due moving certain functionality out of the plug-in and into the loader core which then ensures that it is available for any plug-in (e.g. Playlist Separator) without needing the JTFE plug-in to be installed.
- This also breaks the ability to customise the colours being used for the highlighting by the plug-in.
ML Enqueue and Play (ml_enqplay.dll)
- Some of the menu items added by this plug-in may not be correct in all cases
- This is due to some of the expected menu item ids not being the same which will be fixed either in the plug-in or by providing the menu items directly within the affected replacement media library plug-ins
Module Decoder (in_mod.dll)
- Transcoding support for this plug-in is not complete and so has not been enabled with the current modified release of the original source code which is provided (which will be enabled when the bugs are resolved)
vgmstream Decoder (in_vgmstream.dll)
- Transcoding support for this plug-in is not implemented so using it with such features will not currently work
Skinned Preferences (gen_prefs_skin.dll)
- Due to this not being 100% complete, it is for the time being provided as a separate dll only download from the main WACUP installer and can be found within the beta downloads and will need to be manually installed
- Not all dialog controls are correctly displayed or handled due to incomplete implementations or not knowing about the controls needing to be handled
- If you find anything that is really wrong or not being handled please let me know.
- Remember that you can always remove / disable this plug-in if not liking having skinned preferences
- The dialog frame of the preferences window is not Winamp skinned which can look somewhat weird
- This is planned but needs some more work before it is enabled in release builds of the plug-in
- Clickable web links may not appear with expected colour
- This is a limitation of the display controls being used which do not make it possible to customise.
Streaming Url Processor (in_url.dll)
- Due to this allowing access to urls that Winamp was not really intended to play (i.e. youtube) it can lead to long delays before the url begins to play (depending upon the internet connection being used)
- More research is required to determine if there is a better way to achieve this feature and / or how to reduce the time taken for playback to occur even if the url has been pre-cached for repeat plays
- Some of the preference pages will flicker / display artifacts when resizing the preferences window
- This needs to be investigated further but is a lower priority as resizing is unlikely to happen frequently
- This can also be more pronounced when using the skinned preferences plug-in & disabled controls
Secondary Stage Setup Window
- Due to some of the overrides of the native Winamp code used in the second stage of installing Winamp, it is possible for the window to re-appear if cancelling instal or an error occurs which prevents setup completing.
- The setup process as a whole needs to be reviewed and altered (partly due to Windows changes regarding file associations) so other than really the skin selection (which could be a one-time on first install), there is little real need for the secondary stage of setup anymore.
- The reason for overriding some of the native Winamp code is to prevent call-home aspects or other aspects related to what was needed / available when Winamp was owned and maintained by AOL.
- Not all of the new / replacement plug-ins are fully translatable due to some features not being complete or under flux whilst being (re-)developed with support to be implemented when the actual feature is complete.
- My recommendation is to not make updated localisations until things are more stable though it might be handy to keep an eye on what is going on (crashes from localisation issues should be reported)
- Additionally the installer will not be localised until a later time (e.g. v1.1) to coincide with any updated localisation packs made available at the time (older original Winamp language packs that are known not to work correctly will not be included & may need to be force disabled when using WACUP)
- Not all of the web links for help support or version changes are currently working and will often end in a 404
- This is primarily related to the sale of Winamp and a lot of the web infrastructure no longer existing.
- For web links that are WACUP specific and are currently missing, these will be resolved as development progresses (primarily for things like changelogs when those changelogs are created).
Uninstall Information Overwritten
- When WACUP is installed it will overwrite the uninstall information that was present for a prior Winamp install
- This is happening due to re-using certain expected registry locations which 3rd party plug-in, skin and related tool installers so that they are able to find the WACUP install as a Winamp install to work with
- This is not a new issue as installing multiple Winamp installs has always overwritten these details so that only the most recent Winamp install is the one noted via the uninstall information (which is not an issue for the majority of users who only make use of a single Winamp install i.e. if not beta testing)
- As of this update, the WACUP installer does not include any of the Visualisation plug-ins (AVS, Milkdrop, etc) that were included as part of the native Winamp installer
- This is being done for the time being as a time (for building and installing) and space saving (~1MB for the installer and more when installed) for the WACUP installer and local install.
- Before WACUP leaves beta then the visualisation handling of the installer will be resolved and most likely only including Milkdrop (due to AVS not working well on Windows versions newer than Windows XP) either as a sub-installer (directly included or downloaded as needed) or to just provide it as a stand-alone installer for those that may want it.