Latest WACUP public preview for x86 & x64 is build #24360 (April 20th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24360 (April 20th 2026) (x86 & x64 changelogs)

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.


Messages - VulgarAscetic

Pages: [1] 2
1
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.

2
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 :(


3
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

4
Happy to help, thanks for all your work :)

5
Adding a blank space " " in library search will return a list of incorrect files, pulled from various locations on the computer, including outside of the designated library folders. In my case, Winamp is only set to watch D:/Music but a blank space search returns audio files from my Windows User Desktop & Downloads.

In addition, some library files are displaying broken or missing metadata, but only when returned via a blank space search. If I search those same audio tracks normally, eg. "artist name" in search, then the metadata appears correctly in the library.

Sorry I can't provide a good screenshot of this one, but the results in my Desktop and Downloads are private. It's an easy repro to try yourself tho.

Repro steps:

1. Go to library
2. In the search box, type a blank space with spacebar
3. Observe library results from incorrect locations and broken metadata

The attached screenshot does show a blank space search (obviously invisible) returning 52 tracks missing Genre and 43 tracks missing Artist, but under normal searches and at a default no search state, no item in my library is missing these data. I'm not yet sure what is determining which files appear broken under a blank space search.

6
Hey there,

These one seems like a bug but may be intended behaviour. However if the latter, it's very unintuitive and not great UX.
Filtering by an album and then using the library context menu to "show all by artist NAME" does not override the search filter.
The terminology of "show all by artist NAME" implies I see everything by that artist, with the album filtering removed.
Untested with other filters such as "genre" but I'd expect the same behaviour.

Repro steps:

1. In library, use the "Album" filter to select an album
2. In library panel, while only viewing the selected album, right click any track
3. Select "show all by artist NAME"

Actual result:

The search bar is populated with the string "?artist="ARTIST NAME" " but the results in the library are still filtered by the original album filtering, therefore hiding any results not in the currently selected album.

Expected result:

In repro step 3, the album filtering should be removed, and ALL tracks by artist should be displayed, as implied in "show all by artist NAME"

7
New media items added to library via a monitored folder will appear with missing metadata until the metdata is edited. The "missing" metadata actually appears to be in place, but just does not initially appear in the library. This seems to affect some of the newly added files, while some appear with the correct metadata in the library.


Repro steps:

1. Go to Preferences > Media Library > Folder Monitor
2. Ensure a folder is being monitored and all options are enabled, such as real time monitoring
3. Add a new folder to the monitored location, which contains some mp3s with correct metadata
4. Wait for the library to auto-scan, or restart WACUP to trigger a scan
5. SOME of the new media items will appear as blank entries at the top of the library
6. Right click a blank entry, and "Edit metdata"
7. Click in any field and then click "Update" (You don't need to actually change any values)
8. The media will now appear with correct metdata in the library

In the screenshot attached you can see three entries of a folder I added, two of them are missing metadata while one track appears correctly (censored as it's unreleased!). This occurs with every folder I add.

8
Yeah I have that option enabled.

But I have found an updated repro: you do not need to actually change any metadata. Simply scroll halfway down your library, right click any item, "edit metadata for selection..." and the immediately close the new window without changing any fields and the entire library will refresh back to default view at the top.

EDIT: I'm an idiot and literally had this as the original repro lol

Somewhat conversely, if you have a search active that finds one result, (eg. a specific song title) and then change some metadata that invalidates the search, the library will then refresh but land in the CORRECT location with the changed item highlighted. But I have seen that there was a change regarding this in the latest build which could have helped here.

9
The new option works perfectly, thank you so much!

10
Currently if you pause a track while sending RTP info to Discord, Discord will show that the track is continuing to play indefinitely.

The track must be stopped rather than paused. It would be great if pausing a track also cleared the Discord RTP info, or if there was at least an option to toggle this behaviour, similar to the option to toggle the Stop behaviour.

11
I know that these tags have been correct for years, and at *some* point changed to the incorrect character, but unfortunately I can't say when that occurred, but I'm inclined to believe it was recently, as in since changing to WACUP, as one of them was appearing as an incorrect Artist which I'd be surprised if I hadn't noticed until now.

I have now managed to change the tags using the external mp3tag tool, and they appear to be sticking correctly now, so there is definitely a bug with tags changed via WACUP regressing to the incorrect English characters.

I'll keep an eye on them moving forward and see if they change back again.

12
Thanks for helping clarify that!

13
Mp3 tags which include the Polish character "ł" are randomly regressing to the English "l", most notable when Polish "ł" is included in more than one tag, eg. song title and album title.

Repro steps:
1. From the library view, open "Edit item metadata" window on an mp3
2. Change the song title to something including "ł" (eg. "hijkłmno")
3. Change any other field to the same title, eg. artist, album artist, album name, etc.
4. Click Update

Expected result:
All fields should maintain the new titles

Actual result:
One of the fields with "ł" will regress to the English character "l"

14
Thank you for replying! Apologies I missed it until now. This is definitely a bug in that case, as any current search will not be respected after a metadata update - the library view will always "refresh" back to the top once the Edit Metadata window is closed

15
Skins / Re: Scaling doesn't affect library text
« on: August 24, 2025, 01:37:10 PM »
That's exacty what I was looking for, thank you so much!

Pages: [1] 2