1
Preview Build Discussion / Re: [CHANGES MADE] New update breaks beat visualizer
« Last post by dro on Today at 07:37:43 PM »The preview build has been updated to 23528 which should now resolve this issue in 23518.
Recent Posts
2
Preview Build Discussion / Re: First impression and remarks on x86 WACUP
« Last post by wd9895 on Today at 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.
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.
3
General Discussion / Re: Any way to enable autosaving?
« Last post by dro on Today at 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.
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.
4
General Discussion / Any way to enable autosaving?
« Last post by slipperyflippery on Today at 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)
(I'm less interested in fixing the crashing issue, it's infrequent and doesn't happen when just playing songs normally)
5
Preview Build Discussion / Re: First impression and remarks on x86 WACUP
« Last post by dro on Today at 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.
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.
6
Preview Build Discussion / Re: New update breaks beat visualizer
« Last post by wd9895 on Today at 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.
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.
7
Preview Build Discussion / Re: New update breaks beat visualizer
« Last post by dro on Yesterday at 07:01:58 PM »Based on the code not having changed around the handling it's actually an older bug (potentially going back to 2024) which 23518 just happens to be more likely to trigger. As it's still possible for it to work but is more likely to fail when using a modern skin. I'm still double-checking changes I've made as I've not seen it happen with them but as it could work before am being cautious.
8
Preview Build Discussion / Re: New update breaks beat visualizer
« Last post by Eris Lund on Yesterday at 04:55:31 PM »Can confirm, the left VU meter in the Classic Skin is entirely dead.
9
Preview Build Discussion / [CHANGES MADE] New update breaks beat visualizer
« Last post by xcile92 on Yesterday at 12:42:09 PM »heres your first bug?
10
General Discussion / Re: Clock Timings
« Last post by dro on January 08, 2026, 02:37:03 PM »There really shouldn't be any tangible difference in the audio output of any audio player unless dsp/eq stuff is being messed around with. I try my best to ensure that what's decoded is what gets sent to the output which some call flat & others can't tell a difference (all players basically sound the same to my aging ears). If another program better suits your needs then you should use that instead.