This is more of a maintenance release than a feature update. The music player is quite usable for the most part. Malwarebytes seems to detect the installer of the old Winamp 5.666 as malicious too. The installer for the new version has been flagged by a few antivirus services on VirusTotal, the developers have indicated these are false positives. You can download Winamp 5.666 Build 3516 from the official website. Warning: Winamp's forums do not have an HTTPS website.ĭownload Winamp 5.9 RC1 Build 9999 from the Winamp website. Refer to the release notes for more information. There are plans to add more default services including Lyrics, and Jamendo. MusicBrainz or MusicStory will replace Gracenote features such as Autotag, CDDB. This includes native support for more audio formats (opus, ogv/ogm, TS, H.265, HLS, VP9, etc.). Winamp's developers have also published a list of upcoming changes that they plan to add to the software. ![]() Some required DLLs may not load on Windows 7 - 8.1. Winamp 5.9 RC1 breaks compatibility with old plugins, including those made by former developer DrO (creator of WACUP), such as the Jump to File Extra (JTFE). These bugs are also expected to be fixed in the next update. View File Info doesn't work, and ReplayGain calculation is broken for Vorbis files. Eleven of the worst affected presets have been removed, but are expected to be fixed in the Winamp 5.9.1 update that is slated for a future release. The Milkdrop plugin's visualization works, but it has issues with some presets. The migration process from VS2008 to VS2019 has resulted in some known issues. ![]() Though it wasn't mentioned in the change log, I noticed that the update also removes many of the old skins. Winamp now requires Windows 7 SP1 as the minimum required operating system, i.e., it drops support for Windows XP and Vista. The help link in the application directs users to a new online Help section.Īccording to the release notes, Winamp has been migrated from VS2008 to VS2019. Aside from these changes, the update fixes some memory leaks. The browser tab has been removed from the Bento skin. The music player has improved Windows 11 compatibility, support for vp8, playback of. a few other 3rd party plug-ins just failing to load / unload correctlyĬompared to what was coming through from the first 5.7 beta build, there's a lot less range in the types of bugs coming in, and Gracenote + 3rd party plug-ins account for almost 2/3rds of issues so my best suggestion is don't use the playlist generator stuff and make sure you're using 3rd party plug-ins which have been updated in the last few years to ensure that your Winamp install is as stable as it can be.This is the first update for the popular music player since Winamp 5.8 beta, that was released in 2018.random crashes at 0x00000000 (often seems to involve unrelated dlls loaded into Winamp's process space so little to do about it).random memory issues in gen_ff (likely heap fragmentation issues). ![]() ![]() random access crashes with the portable devices on device discovery.winamp.exe will randomly crash on some async title update callbacks (have seen it myself a while back but might be related to the browser helper dlls).ml_disc issue when accessing some title information (likely a driver related issue).in_cdda loading issue (dll dependency issues).in_wm (DRM / old sdk handling issues which cannot be fixed without a new sdk).Gracenote libraries (already known and cannot be fixed without a new sdk).crash on shift+e dialog, playlists enqueue issues, classic skin song ticker not updating in all cases, random crash issues from the bug reports, compat mode adjustments,language pack updates especially the d&d issues) but there's no guarantee.Īnd most of the issues coming up from the crash reports from the 5.66x builds are: It's still being looked into whether one more patch build can be done which allows for any glaring issues to be resolved (e.g.
0 Comments
Leave a Reply. |