[Bug] Ableton .asd files cause WACUP to lose metadata from .mp3 files

[VulgarAscetic]

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

[dro]

I don't get what the connection of a supporting file that shouldn't even be being touched when mp3 metadata is being read is here unless you're doing the import / metadata refresh when that other program has a lock on the file access which would prevent what I'm trying to do from working. If so I don't see anything obvious I can do for it other than skipping anything that I might be attempting if the file is locked (which I thought I was doing & if that's not right then that could explain the metadata disappearing).

[VulgarAscetic]

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.