Latest WACUP public preview for x86 & x64 is build #24960 (August 31st 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24960 (August 31st 2026) (x86 & x64 changelogs)

Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Visualisations / Re: SmokeEffect
« Last post by dro on August 26, 2026, 07:55:55 AM »
Do not click configure because your WACUP will crash the software!
This isn't a WACUP issue as it also does it under a winamp 2.9x instance.

If it helps narrow it down: does WACUP produce a crash dump or an entry in Windows Event Viewer (Application log) when you hit Configure? A lot of old Winamp-era vis plugins call into the config dialog with an HWND/API assumption that doesn't quite match how WACUP hosts them (vs original Winamp), so the crash is often specifically in the config path rather than the visualization itself running fine otherwise. If you can grab the exception address/module from the crash (or just enable "keep debug info" if WACUP has that toggle under preferences) and post it here, that's usually enough for someone who knows the plugin API to tell whether it's a WACUP hosting issue or something in the plugin's own config code that never got updated for newer OS versions.
Firstly posting crash dmps onto the public part of the forum is a no-no for a number of reasons. Secondly WACUP's vis handling does things that Winamp didn't to try to better accommodate old plug-ins however a lot of them can & will crash as they either expect to be running in a folder that allows them to save their configuration (aka running as admin which doesn't help this plug-in) or were built in a manner that can conflict with DEP/NX-bit handling since the late XP days (this doesn't seem to be the case here but I'm not going to debug it further than a quick check to see why it might fail & the api handling doesn't seem to be it).
72
Visualisations / Re: SmokeEffect
« Last post by sgard on August 26, 2026, 05:20:43 AM »
If it helps narrow it down: does WACUP produce a crash dump or an entry in Windows Event Viewer (Application log) when you hit Configure? A lot of old Winamp-era vis plugins call into the config dialog with an HWND/API assumption that doesn't quite match how WACUP hosts them (vs original Winamp), so the crash is often specifically in the config path rather than the visualization itself running fine otherwise. If you can grab the exception address/module from the crash (or just enable "keep debug info" if WACUP has that toggle under preferences) and post it here, that's usually enough for someone who knows the plugin API to tell whether it's a WACUP hosting issue or something in the plugin's own config code that never got updated for newer OS versions.
73
Visualisations / SmokeEffect
« Last post by TheLegoBoy on August 26, 2026, 01:06:24 AM »
Nothing to say in particular ... Just play your favorite music and go on journey into those colored fumes.

Just like Geiss-style smoke.

Do not click configure because your WACUP will crash the software!

This plugin made by Matthieu Chopin.
74
Visualisations / Degnic
« Last post by TheLegoBoy on August 26, 2026, 12:54:45 AM »
All completed with packs classic and oldiest ever on the AVS Pack from Degnic.

Farewell Degnic a.k.a Blazer!
75
Visualisations / fsk
« Last post by TheLegoBoy on August 26, 2026, 12:12:57 AM »
A collections part and remixes are Degnic and UnConeD mostly S_KuPeRS.
76
General Discussion / Re: Global hotkey for playlist search (J)
« Last post by dro on August 24, 2026, 03:23:39 PM »
Build type as in the x86 or x64 type of wacup. Though I doubt it matters & assume that you've got different dpi settings between the 2 monitors & it's the caret position that you're referring to which isn't being correctly dpi adjusted.

[edit]
If I'm seeing what I think you're describing then I don't see the issue happen all of the time but it looks like if I change when I tell the OS to not mess with the skinned form of the jtfe window when it comes to DPI scaling to a bit earlier on in the window loading process it seems to resolve the problem I'm seeing.
77
Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results
« Last post by dro on August 23, 2026, 06:30:25 PM »
I've fixed some of the performance issue when trying to enumerate through too many folders with the newer dev build but more needs to be done to improve what's going on so it doesn't cause things to lock-up for a time as can still happen (at least it doesn't get stuck in a perpetual loop as I could quickly replicate).

[edit]
Have made some more changes which should now resolve it crashing when trying to interact with the preset browser whilst it's also trying to scan a folder (especially when it's the appdata one) along with it being much slower than it should do as part of sorting the presets that it's found (e.g. ~8sec to 0.1sec with the change made which leaves me with an ~5sec time to scan all of the appdata folder).
78
Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results
« Last post by LigH on August 23, 2026, 06:04:49 PM »
The crash in the MilkDrop plugin was due to trying to ascend the directory tree to get to the Documents. After a few wrong attempts to get me out of this culprit I found the correct INI file though.
79
Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results
« Last post by dro on August 23, 2026, 05:59:33 PM »
Setting milkdrop to scan the whole of the %appdata% folder really isn't going to go well & that's the only obvious reason I can deem why it caused the crashes that I saw. If it's crashing during the install phase then I don't get crash reports from that. I also have little control if the attempt to re-acquire the needed 5.666 files from one of its installers fails which for the most part is just for the modern skin support now.
80
Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results
« Last post by LigH on August 23, 2026, 05:21:09 PM »
OK, beta Dev-build.

Several crashes, uninstalls and fresh re-installs later (installer stops at the attempt to re-download original Winamp 5.666 libs when it tries to update an existing installation):

MilkDrop 2 works OK regarding the last bug.

But it behaves annoyingly for different reasons. So I doubt I will ever enjoy the port from AVS to MilkDrop2.
Pages: 1 ... 6 7 [8] 9 10