Recent Posts

1

Preview Build Discussion / Re: [BUG] NSF/NSFe playlist incorrect for some files

« Last post by dro on April 16, 2026, 10:35:53 AM »

I can reproduce this problem but I don't see why it's happening as it's just using what the nsfplug code is reporting back unless there's something that's changed between the standalone player & what's on github currently (couldn't see any obvious difference). Other nsfe I've thrown at it appear to be reporting the correct number of subsongs compared to what nsfplay is indicating which is odd but then some are also showing more than are expected so I'll have to do some more digging into what's going wrong here.

[edit]
Ok I think I get what's going on here. The files can have a 'playlist size' or a 'total song' which I'm using the later so everything that might be present is going to be extracted. I'm debating what to do & might have to add an option to the preferences to control which value is used when they're different (as your example shows it's a 16 track playlist but is reporting 54 songs though nsfplay doesn't seem to do that so I don't know if that's a quirk of the format or something else). Other ones I've given to it will show a playlist size & the tracks (maybe it's something about the metadata that's provided) so I'll see what I end up doing once I've thrown more files at this.

2

Visualisations / Re: Martins collection of milkdrop presets

« Last post by Incubo_ on April 15, 2026, 09:46:31 PM »

With Screen-Dependent Render Mode, it fixes the incomfortable behavior of old MilkDrop Presets, ex: Eo.S, yin, Che, Zylot etc.
And glad it's working with its feature on and shader aspect variable ignore fix.

Did you see my edits from the post I've told earlier?

Maybe I'll have an ability to turn on/off this feature with hotkey later...

3

Visualisations / Re: Martins collection of milkdrop presets

« Last post by Nitorami on April 15, 2026, 07:47:29 PM »

DrO: You made it rather clear that visualisation is very much at the bottom of your priority list, so I don't quite understand the intent of your comment. Anyway, the code is on github.

Incubo: We talked about that before per PM. I told you that you got the aspect wrong / different from milkdrop. You answered that this was because of an issue with vertex coordinates, and I should set bScreenDependentRenderMode=0 in the ini file. Well, that worked for me, although I was annoyed that you left the default setting at 1, breaking milkdrop compatibility. Why don't you simply set bScreenDependentRenderMode=0 per default ? It seems to do the job.
Anyway, the latest beta does it correctly, and independent of bScreenDependentRenderMode.

4

Preview Build Discussion / Re: [Bug] Ableton .asd files cause WACUP to lose metadata from .mp3 files

« Last post by VulgarAscetic on April 15, 2026, 07:16:16 PM »

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.

5

Skins / Re: in visualization/cover art bug.

« Last post by dro on April 15, 2026, 02:54:21 PM »

Don't have a go at wacup when it's winamp's gen_ff plug-in that's behind all of your issues!

6

Skins / Re: in visualization/cover art bug.

« Last post by parisienne17 on April 15, 2026, 02:48:27 PM »

Obviously tranparency is mandatory, how could have I forgotten about that ?
Cover art is ok but whatever I do, vis shows on top the player. It stays but I have to click the player to have vis trimmed.
​​​​​​​!§$£0#[ media player !

7

Skins / in visualization/cover art bug.

« Last post by parisienne17 on April 15, 2026, 03:22:12 AM »

Even if it shares 90% code with my previous skin, Just one added parent layer, I get issues with my new development; Onyx.

In compact mode, whatecer I do, I just can't shape cover art to the in holder shape : I've tried masking with <layer xxx sysregion=-2> on top of it or put a foreground image, corners still show up.

The in vis mode, despite also using regions, the in vis controls don't show and as soon as I click/drag the payer, wis disappears and controls showup.

What's wrong ?

8

Visualisations / Re: Martins collection of milkdrop presets

« Last post by dro on April 14, 2026, 10:55:29 PM »

So everyone else has working amd support I take it but haven't passed any of that knowledge back, how nice.

9

Visualisations / Re: Martins collection of milkdrop presets

« Last post by Incubo_ on April 14, 2026, 10:30:22 PM »

Hey! The inverse aspect ratio correction is 1 because it depends on screen (has Screen-Dependent Render Mode ON). That's why it does look stretched, but try this trick:
In a warp/comp shader code, multiply the uv with

Code: [Select]

float2(1, texsize.y/texsize.x) This is the most efficient way to aspect correct without problems.

So it goes like:

Code: [Select]

...
float2 aspect_ts = float2 (1, texsize.y/texsize.x);
rd = RotXYZ(float3 ((uv_orig-.5)*aspect_ts.xy/zoom*float2(torusdir,1),1), scenerot);
...

Let me see if it works for you.

...or I'll look into the code and I'll fix the ignored aspect ratio correction for shaders. Someday, somehow...

EDIT: I did look at milkdropfs.cpp and I see that both aspect vars were initialized with 1: https://github.com/OfficialIncubo/BeatDrop-Music-Visualizer/blob/master/vis_milk2/milkdropfs.cpp#L4951-L4957
I'll have a fix when I have time.

EDIT 2: Fixed: https://github.com/OfficialIncubo/BeatDrop-Music-Visualizer/commit/b6b9ea0665067027e23829dab133d5f051080f79
I'll update the BeatDrop beta test package shortly, so you can try.

EDIT 3: Updated! You can try to test with your presets if it works.

10

Visualisations / Re: Martins collection of milkdrop presets

« Last post by Nitorami on April 14, 2026, 08:45:17 PM »

Look. This is a beautiful atmospheric milkdrop preset I made over the past weeks. It features a variety of random scenes, random textures and a strictly rhythmic light pattern.  The screenshots don't really do it justice, you need to see it in motion.

Unlike my earlier presets, this one needs a bit more GPU power, and requires a half decent gamer's video card. Nothing too fancy, something like a mainstream GTX1650 of 2019 should run it smoothly. It does not require a high frame rate BUT BUT BUT the GPU power should suffice to keep it constant. The GPU load varies, depending on the scene shown, and if the GPU is too weak, the frame rate will change, causing unpleasant speed changes and stuttering. My own old GT710 does exactly that, and as a workaround I set the Canvas Stretch to 1.67 and limit the frame rate to 25 in the milkdrop settings, to get it running ok, albeit at lower resolution. Not satisfying really.

Note - On loading, the code will take a few seconds to compile, interrupting the usually smooth flow of visuals. If this is unacceptable, consider using third party milkdrop derivates like milkdrop3 or beatdrop. They have solved the issue by precompiling and caching presets, resulting in virtually zero loading time.

An on AMD video cards: Neither winamp nor WACUP support PSVERSION 4 on AMD video cards. But milkdrop3 and beatdrop have solved this.

A note when you use beatdrop: Beatdrop ignores the preset's aspect ratio correction, causing an unsightly disproportional stretch on wide monitors. To avoid this, I strongly suggest to set bScreenDependentRenderMode=0 in beatdrop.ini. And to leave it at that.

Best
Martin