Latest WACUP public preview for x86 & x64 is build #24360 (April 20th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24360 (April 20th 2026) (x86 & x64 changelogs)

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
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!
22
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 !
23
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 ?
24
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.
25
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.
26
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
27
General Discussion / Re: Video File Classifications / Supported File Types
« Last post by ww on April 13, 2026, 05:39:15 PM »
Understand.

Thanks WW
28
General Discussion / Re: Video File Classifications / Supported File Types
« Last post by dro on April 13, 2026, 05:23:46 PM »
The metadata / file handling with in_what isn't yet full done which is preventing it being able to detect & report back the 'type'. That causes it to treat things as unknown which the library will assume is audio & will require a rescan once that's eventually implemented.
29
General Discussion / Video File Classifications / Supported File Types
« Last post by ww on April 13, 2026, 10:48:26 AM »
Hello dro,

thanks for your recent updates, esp. the video support in-what, so I have restarted using WACUP for video play.

Video playback works ok with all my filetypes which are MKV, MP4, MPEG, MPG, AVI, TS.

Scanning the storage location and adding the files to the local library works as well. Unfortunately only the MP4 files are sorted to the Video View, all others show up under Audio View. Checking under the Local Library - Supported File Types tab, only MP4 and M4V files are shown as Video types, all other typical video file types are listed as Audio. Is this the reason why they are also shown in the Audio View i.o. Video, and if yes can this be corrected?

I use the last dev build 24270.

Thanks WW
30
Preview Build Discussion / [BUG] NSF/NSFe playlist incorrect for some files
« Last post by nelsonhf on April 12, 2026, 02:02:49 PM »
Hi, i'm using WACUP v1.99.47.23960 with the included NSF/NSFe Player (in_notyansf.dll) v0.9.7 and in some files the playlist gets an incorrect (larger) number of tracks than the actual file has (compared with another player like NSFPlay or plug-in). As an example this is the same file opened with WACUP and NSFPlay:



Pages: 1 2 [3] 4 5 ... 10