That's a bit odd as it should've been enabled by default. At least it was something simple to resolve it unlike I expected :)
Its still working here & a few others from a quick check of things so this might be the random failure that a few have reported ever since the feature was added. Check if there's a "discord_response" entry in the winamp.ini within you wacup settings folder just after the playback start has occurred.
the mess that is "winamp" nowadays is having it's ass whipped & i'm quite glad i've nothing to do with it ;)
what calls itself "winamp" over that time isn't the nullsoft / aol era winamp & tbqh wacup should never have needed to exist. I sure wasn't happy with how things were going nor were the others who convinced me to start making a plug-in pack for 5.666 after I'd been let go which evolved a lot since.
Its a fair reflection of how it's been handled by them over the past 11yrs with how messed up its gone.
Nothing to do with them & began as a plug-in pack which feature crept a bit too much into becoming its own standalone winamp-like player. For now it still has to use a few of the pre-compiled dlls from 5.666 which I'm gradual working on replacements though gen_ff (modern skins) will take some time.
ah ok. will just trust you then that things are fixed with the changes.
ok, I only mentioned it as the array is 33 elements but the change clamps it to 32 so the last 127 seemed superfluous if it's previously been determining lut_size from the array size. anyhoo if you're finding its working fine now then I'll apply it & find those sets to try it out on just to confirm.
it was mostly them trying to get a free dev team but they've messed that up. not that I suspect they'll be reducing the licensing restrictions as all of that is very much intended nor care too much in the long term as desktop was never their focus.