1
Preview Build Discussion / Re: [Bug] Preferences window is completely missing
« on: September 06, 2026, 01:22:04 PM »
Amazing, thank you! <3
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.
2
Preview Build Discussion / [Bug] Removing folder from "Folder Monitor" does not remove files from library
« on: September 06, 2026, 01:20:42 PM »
Removing a previously scanned folder from Media Library Folder Monitor does not remove those files from the library.
I had a library across two drives "P:" and "M:". On scanning both, all the tracks in library duplicated as expected. However, removing M: from the Folder Monitor did not remove the tracks from my library, and I don't seem to have any option to do so now.
"Scan Folder Now" option does nothing, and "Automatically remove missing files" is not a valid option as the files technically do still exist on both drives.
Screenshots show the library tracks are duplicated, despite only one folder appearing in Folder Monitor.
Repro steps:
1. Have music files located in two separate folder locations
2. Add both folders to the Media Library Folder Monitor
3. "Scan folder now" on both folders
4. Observe all files appear in WACUP library as expected
5. Remove one folder from Media Library Folder Monitor
6. Observe those files incorrectly still remain in the library
Expected Result: Removing a folder from Folder Monitor should remove the files from the library, or there should be an explicit option to do a kind of "purge" of the library.
I had a library across two drives "P:" and "M:". On scanning both, all the tracks in library duplicated as expected. However, removing M: from the Folder Monitor did not remove the tracks from my library, and I don't seem to have any option to do so now.
"Scan Folder Now" option does nothing, and "Automatically remove missing files" is not a valid option as the files technically do still exist on both drives.
Screenshots show the library tracks are duplicated, despite only one folder appearing in Folder Monitor.
Repro steps:
1. Have music files located in two separate folder locations
2. Add both folders to the Media Library Folder Monitor
3. "Scan folder now" on both folders
4. Observe all files appear in WACUP library as expected
5. Remove one folder from Media Library Folder Monitor
6. Observe those files incorrectly still remain in the library
Expected Result: Removing a folder from Folder Monitor should remove the files from the library, or there should be an explicit option to do a kind of "purge" of the library.
3
General Discussion / Re: Is it possible to preserve play counts while moving music to another drive?
« on: August 20, 2026, 07:58:57 PM »
That would be really amazing, I'll keep an eye out in the next patch notes, but no pressure ofc 
4
General Discussion / Is it possible to preserve play counts while moving music to another drive?
« on: August 19, 2026, 08:24:20 PM »
I'm moving my music library from drive D:\ to drive M:\ and all the folder and file structure is the same. Can I do this and preserve the play counts in my WACUP library? If I scan my new drive the files appear as "new" files in WACUP and all have 0 plays.
5
Preview Build Discussion / Re: [Bug] Preferences window is completely missing
« on: August 19, 2026, 08:04:14 PM »
Ah nice, that fixed it. I thought I had tried that but it's a pretty precise click so I must have just missed it. I have no idea what caused this but I do move WACUP around across multiple monitors regularly enough so maybe something to do with that?
Thanks for the help as always
Thanks for the help as always
6
Preview Build Discussion / [Bug] Preferences window is completely missing
« on: August 17, 2026, 05:34:51 PM »
As in screenshot, Preferences window appears as a floating bar with no panels or details at all. This occurs when opening Preferences either via File>Preferences or the Ctrl+P shortcut.
7
Skins / Re: Big Bento Modern v1.2
« on: May 21, 2026, 12:44:55 PM »
Additionally (sorry for double post) I have a feature request which I'm not sure shoudl go in this thread or general WACUP feature requests.
It would be good to have a permanent "X" button to clear the search filter even when the search filter is empty, as in 5.666 I would frequently use this button to quickly defauly my library view to the top of the list. Currently, the "X" only appears if a search filter has been filled out, which is not always the use case.
It would be good to have a permanent "X" button to clear the search filter even when the search filter is empty, as in 5.666 I would frequently use this button to quickly defauly my library view to the top of the list. Currently, the "X" only appears if a search filter has been filled out, which is not always the use case.
8
Skins / Re: Big Bento Modern v1.2
« on: May 21, 2026, 12:41:47 PM »
Got a feature request for this: would it be possible to have an option to always display the volume slider and mute button? Currently they are hidden behind clicking the volume button, which is weird UX for such a crucial control. I'd expect an instant mute when I click the volume button, and I'd also expect the volume slider to be always visible in a prominent location.
Additionally, the UX of clicking volume to turn mute visible, and then having the mute button appear some distance to the left, is also awkward.
Thank you for all the work on this great skin
Additionally, the UX of clicking volume to turn mute visible, and then having the mute button appear some distance to the left, is also awkward.
Thank you for all the work on this great skin
9
Preview Build Discussion / Re: [Bug] Library refreshes to default view after user has scrolled downwards
« on: May 21, 2026, 12:38:14 PM »
Tried to repro, it seemed to coincide with a track finishing and moving to the next in the playlist, which occurred about 63 seconds after scrolling down the library.
Tried the same repro again after manually playing a song from the playlist which meant my mouse cursor was no longer focused over the library view, and the the bug did not reproduce, so there's a few variables and red herrings in this one right now
Tried the same repro again after manually playing a song from the playlist which meant my mouse cursor was no longer focused over the library view, and the the bug did not reproduce, so there's a few variables and red herrings in this one right now
10
Preview Build Discussion / [Bug] Library refreshes to default view after user has scrolled downwards
« on: May 21, 2026, 12:33:37 PM »
When viewing your library, if you scroll downwards some arbitrary amount and then leave WACUP idle for some indeterminate time, the library will "auto-refresh" and revert the view back to the top of the list. Unsure how much exact time this takes, but it's not long, maybe in the realm of 30-ish seconds.
Repro steps:
Result: Library will revert view back to the top of the list after some time
Repro steps:
- Open library
- Ensure search is empty so view is at default
- Scroll down through your library
- Stop at a random location
- Wait, and observe WACUP
Result: Library will revert view back to the top of the list after some time
11
Preview Build Discussion / Re: [Bug] Edited metadata regresses to previous values, "update file tags" fails
« on: May 21, 2026, 12:29:24 PM »
Thanks for the clarification and once again thanks for all of your work!
Thinking out loud here, but I had an issue with external tagging tools (specifically Mp3tag) having the same ambiguous failure of "can't write to file" until I realised I needed to run it as an administrator, and now it will write correctly.
I wonder if the old x86 plugin is failing for a similar reason? But I don't recall it being an issue with 5.666 so could easily be some other bug/regression that has appeared since.
Thinking out loud here, but I had an issue with external tagging tools (specifically Mp3tag) having the same ambiguous failure of "can't write to file" until I realised I needed to run it as an administrator, and now it will write correctly.
I wonder if the old x86 plugin is failing for a similar reason? But I don't recall it being an issue with 5.666 so could easily be some other bug/regression that has appeared since.
12
Preview Build Discussion / [Bug] Edited metadata regresses to previous values, "update file tags" fails
« on: May 09, 2026, 03:33:23 PM »
When updating some mp3's metadata, it appears successful, but any subsequent edits to the same file metadata will regress previous edits. Additionally, some files will regress by themselves over time, effectively going back to previous metadata. It's unclear what causes this "timed" regression.
Selecting "Update file tags" checkbox in the metadata editor will give a "Metadata updating error" box, but it is unclear what causes this to fail, when other mp3 files will update their metadata correctly.
Worth noting that these same files can be successfully edited in other software such as mp3tag.
Screenshot show the metadata successfully changed in Wacup but not in the file metadata seen in explorer.
Repro steps:
Selecting "Update file tags" checkbox in the metadata editor will give a "Metadata updating error" box, but it is unclear what causes this to fail, when other mp3 files will update their metadata correctly.
Worth noting that these same files can be successfully edited in other software such as mp3tag.
Screenshot show the metadata successfully changed in Wacup but not in the file metadata seen in explorer.
Repro steps:
- Right click a file in library
- Go to "edit metadata for selection"
- Ensure "update file tags" is UNCHECKED
- Edit the track name to something else
- Click update
- Track name appears to change
- Repeat steps but change the album title this time
- Album title updates, but track title will regress to before the above edit
- Open metadata editor again
- Ensure "update file tags" is CHECKED
- Change any metadata and click update
- Update fails
13
Preview Build Discussion / Re: [Bug] Ableton .asd files cause WACUP to lose metadata from .mp3 files
« on: April 15, 2026, 07:16:16 PM »
Yeah it's bizarre, but the correlation between the broken metadata and the files with generated .asd files here is perfect. It's extremely unlikely I've ever edited metadata in WACUP while working on some project in Ableton that locked these files, but I won't rule it out.
I'll have a play around with the repro steps and if I'll update this thread if I find anything concrete.
I'll have a play around with the repro steps and if I'll update this thread if I find anything concrete.
14
Preview Build Discussion / [Bug] Ableton .asd files cause WACUP to lose metadata from .mp3 files
« on: March 31, 2026, 10:04:24 PM »
Ok this is a good one! When adding an mp3 (or any other audio file) into an Ableton project, there is an option to generate an .asd analysis file alongside it, which is basically a waveform editing reference file. https://www.ableton.com/en/live-manual/12/managing-files-and-sets/#analysis-files-asd
These are generated next to the audio file, an example is importing MUSIC.mp3 into Ableton will generate a MUSIC.mp3.asd file in the same directory. Annoyingly, Ableton does not provide an option to generate the .asd files in a custom location, which means they end up scattered in random folders across all your drives.
The bug here is that any mp3 files which have an accompanying .asd will fail to load correct metadata into WACUP. The screenshot shows a ton of mp3s I dragged into an Ableton project a few days ago for a performance over the weekend, which are now missing lots of metadata which existed prior to the Ableton project. Opening WACUP today I noticed this bug. The strange thing is about 4-5 of these tracks have very old .asd files from months ago, but only generating the new .asd files on the latest Ableton project a couple of days ago triggered this bug. (Had to censor the screenshot due to lots of unreleased material here, sorry.)
Repro steps:
1. Ensure you have mp3 tracks added to your WACUP library and they appear with correct metdata
2. Open an Ableton session
3. Ensure Ableton option are set to generate .asd files
4. Drag one of your mp3s into Ableton and wait for waveform to fully generate
5. Save the project
6. Restart WACUP (I guess?)
7. Observe broken metadata on the file you dragged into Ableton
The real fix here is to pester Ableton to give us a custom .asd folder the same way Reaper does for it's analysis files, so they are not randomly scattered across every single folder on your computer, but people have been requesting this for like 15 years if you dig through old Ableton forum threads
These are generated next to the audio file, an example is importing MUSIC.mp3 into Ableton will generate a MUSIC.mp3.asd file in the same directory. Annoyingly, Ableton does not provide an option to generate the .asd files in a custom location, which means they end up scattered in random folders across all your drives.
The bug here is that any mp3 files which have an accompanying .asd will fail to load correct metadata into WACUP. The screenshot shows a ton of mp3s I dragged into an Ableton project a few days ago for a performance over the weekend, which are now missing lots of metadata which existed prior to the Ableton project. Opening WACUP today I noticed this bug. The strange thing is about 4-5 of these tracks have very old .asd files from months ago, but only generating the new .asd files on the latest Ableton project a couple of days ago triggered this bug. (Had to censor the screenshot due to lots of unreleased material here, sorry.)
Repro steps:
1. Ensure you have mp3 tracks added to your WACUP library and they appear with correct metdata
2. Open an Ableton session
3. Ensure Ableton option are set to generate .asd files
4. Drag one of your mp3s into Ableton and wait for waveform to fully generate
5. Save the project
6. Restart WACUP (I guess?)
7. Observe broken metadata on the file you dragged into Ableton
The real fix here is to pester Ableton to give us a custom .asd folder the same way Reaper does for it's analysis files, so they are not randomly scattered across every single folder on your computer, but people have been requesting this for like 15 years if you dig through old Ableton forum threads
15
Preview Build Discussion / [Bug] Equalizer plugin does not remove low frequencies <300Hz
« on: March 24, 2026, 11:56:58 PM »
Setting the EQ to remove anything under 300Hz doesn't really seem to have any effect. I've provided two screenshots, one has no EQ with a full spectrum visible, the other screenshot has the EQ entirely rolled off under 600, but the effect only seems to scoop the mids. Anything under around 300-200 start to become drastically audible again, with the lowest frequencies almost unaffected. There is a mild reduction in the lows/subs, but nothing even close to what the EQ should be doing at these settings.
I've tested this behaviour on the high end and roling off high freqs does seem to work as intended.
Repro steps:
1. Play some music
2. Open the EQ
3. Roll off everything at 320Hz and lower
4. Use a spectrum analyzer (or your ears) to observe no change in low end
I've tested this behaviour on the high end and roling off high freqs does seem to work as intended.
Repro steps:
1. Play some music
2. Open the EQ
3. Roll off everything at 320Hz and lower
4. Use a spectrum analyzer (or your ears) to observe no change in low end