Latest WACUP beta release is build #9166 (October 21st 2021) | Latest WACUP public preview is build #7236 (March 11th 2021)

NOTE: New beta testers are not currently being added as I need to re-work the beta test program

If you've not already requested to be a beta tester & would like to then please send a PM to 'dro' to be added to the beta test group.

Note: requests to be a beta tester are processed in batches when new beta builds are released so please by patient of this process.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - kylejcrb

Pages: [1]

I've encountered a bug with WACUP build #6800 (and earlier) when using some legacy plugins, in particular the NSF player NotSo Fatso (I prefer this plugin to NSFPlay because of its "Shadow to Playlist" feature.) The plugin itself has proper functionality as expected, but any changes made to the settings within the plugin are not persistent and will reset whenever WACUP is closed. This seems to affect any plugins that would normally save to the plugin.ini file in the C:\Program Files (x86)\WACUP\Plugins directory. Modifying this file manually does not change these settings in WACUP, either.


I have encountered a bug in WACUP build #6800 (and earlier) in regards to SPC archives, or .RSN files. When attempting to open these files, they will appear in the playlist with the filename, and "(contains ## valid files)" appended to it. The individual songs are not expanded into the playlist and the file is not playable. Renaming the file to .ZIP makes the individual songs appear in the playlist as expected, but renaming a full collection of .RSN to .ZIP seems rather extreme to fix this issue.


I've encountered a bug with WACUP #6800 (and earlier) involving the tags for SPC files. It seems that the ATF setting overwrites the ID666 tags in both the playlist and the File Info section. Disabling it corrects the problem with SPC files in playlists, but the File Info window is still incorrect, and obviously it isn't ideal to disable ATF universally for a problem with one file format.

Pages: [1]