Recent Posts

1

Wishlist / Feature Requests / Re: Feature Request: Display Opus Codec Vendor (libopus) info in File Info Basic Tab

« Last post by dro on Yesterday at 10:24:22 PM »

I'm not sure about having it do it just like the 3rd party plug-in as yes there's space but then just filling it with a load of info also doesn't necessarily help most users.

I'll at least add the vendor entry & see about some of the others shown along with double-checking any of the other ogg related formats so they're more consistent in what's reported where I think it makes sense.

2

General Discussion / Re: Bookmark Subfolders Missing Last Letter on Right-Click Menu

« Last post by dro on Yesterday at 10:14:30 PM »

Can you attach the images to the post please as imgur geo blocks me from seeing them.

3

General Discussion / Bookmark Subfolders Missing Last Letter on Right-Click Menu

« Last post by mpamp64 on Yesterday at 09:51:42 PM »

The last letter of bookmark subfolder names are being truncated when navigating the right-click menu.

Right Click Menu


Media Library


~~ Thank you for keeping WA alive! ~~

4

Wishlist / Feature Requests / Feature Request: Display Opus Codec Vendor (libopus) info in File Info Basic Tab

« Last post by szabiz on Yesterday at 07:32:53 PM »

Hello DrO and the WACUP community,
I am a long-time user trying out the modern WACUP with my Opus files. I noticed that when I open the "File Info" (Alt + 3) and look at the Basic Info tab, some detailed technical information about the codec vendor (like Vendor: libopus 1.5.2) is missing, unlike in the older, official Winamp with a separate Opus plugin (see attached images for comparison).

There seems to be plenty of room for this information on the basic tab.

This information is helpful for verifying the source of my audio files.

It would be a great addition if these specific technical details could be visible in the Basic Info tab, similar to how the older plugin handled it, instead of having to go into a raw data view.

Thank you for your hard work on WACUP!

5

Preview Build Discussion / Re: [CHANGES MADE] New update breaks beat visualizer

« Last post by dro on January 12, 2026, 07:37:43 PM »

The preview build has been updated to 23528 which should now resolve this issue in 23518.

6

Preview Build Discussion / Re: First impression and remarks on x86 WACUP

« Last post by wd9895 on January 12, 2026, 06:20:36 PM »

Oh. I read your explanation about the VU meter. That's noticed.
For the missing length column I'd like to be more precise of what I mean. Please have a look on the attached pic.
For your reference: I made a complete new installation and a new import of library.

7

General Discussion / Re: Any way to enable autosaving?

« Last post by dro on January 12, 2026, 05:56:51 PM »

It shouldn't be crashing at all from those actions & causing you to try to find workarounds which might be what's causing it to occur or can make it fail differently. What build type & version of wacup are you using & does wacup's crash reporter run when it's failing on you?

Ratings go into the local library db which tries to auto save out of needed once there's not been any activity or enough dirty entities are deemed to have occurred.

Library playlists should show a save button on the view or will save out when the action being done to them completes if not within the selected playlist view.

The main playlist with the undo plug-in installed should make backups when any change occurs to it.

I just can't remember if it's on the undo or autoplay prefs page or somewhere else that the timed trigger for storing any changed settings option is still on which would then do the local library save as well. But setting that too often will cause ui hangs & is more likely to trigger a crash.

8

General Discussion / Any way to enable autosaving?

« Last post by slipperyflippery on January 12, 2026, 05:19:39 PM »

I'm trying to rate and add various songs to playlists but sometimes the program will crash and I lose all progress since I last closed it, currently I just close WACUP every now and then to save all my changes but is there a way to make it autosave everything I've done so I don't have to redo any work I've put in?

(I'm less interested in fixing the crashing issue, it's infrequent and doesn't happen when just playing songs normally)

9

Preview Build Discussion / Re: First impression and remarks on x86 WACUP

« Last post by dro on January 12, 2026, 04:52:01 PM »

I still can't replicate the missing length column issue that you've mentioned here & also mentioned again in the thread about vu meter issues which I've not seen anyone else report it. The only obvious thing since it seemingly can get that information is to run a refresh of the local library or just attempt to do it on a specific selection within one of the local library views & see if that makes a difference.

If it still doesn't make a difference when using 23518 (or a newer build depending on when this is seen) then I could do with a screenshot of the local library view showing what you're seeing (maybe the sizing of the column vs trying to reduce drawing of non-visible elements vs potential OS dpi related handling is conflicting) & a copy of the library.dat & library.idx files from the settings folder (preferences -> advanced -> diagnostics -> settings location tab will provide your paths). The library.dat/.idx files should be pm'd instead of posting here & depending on the size of them you might need to upload to some external hosting if they won't fit within the pm attachment size limits.

10

Preview Build Discussion / Re: New update breaks beat visualizer

« Last post by wd9895 on January 12, 2026, 09:33:52 AM »

You are fast
Confirmed, the left VU meter in the Classic Skin is dead on 32bit version.

Another phenomon which I might have heard also in the previous beta: The 32bit version sounds "better".
I have to check settings of equalizer and used outpot plugin.

The length column is still empty but I'm confident for the future
Have a good Monday start into the week !

P.S. This is feedback no critics.