1
Visualisations / Re: Martins collection of milkdrop presets
« on: Yesterday at 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.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
General Discussion / Re: Video File Classifications / Supported File Types
« 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.
3
Skins / Re: Big Bento Modern v1.2
« on: April 09, 2026, 05:45:15 PM »
What you've posted is already the log of the error & is the same script file as others who've reported the issue have had the skin engine complain about. I've tried setting things to what I think you've described & I still cannot get that script error to appear be it in a new or existing installs.
Until I can see it happen & for it to consistently fail there's little I can do right now as I don't have anything else to try against what was already done before the recent build went up which tried to resolve the failures I could force in the mentioned script file. This is why modern skins are just awful to try to support.
Until I can see it happen & for it to consistently fail there's little I can do right now as I don't have anything else to try against what was already done before the recent build went up which tried to resolve the failures I could force in the mentioned script file. This is why modern skins are just awful to try to support.
4
Skins / Re: Big Bento Modern v1.2
« on: April 07, 2026, 09:12:29 PM »
It's the same issue as the post above & there's also a whole dedicated thread about it but there wasn't the specific information which I'm hoping when I look into trying it will be what causes it to occur on my side as I've not been able to replicate it to get it fixed.
5
Preview Build Discussion / Re: Volume Control?
« on: April 03, 2026, 10:14:49 PM »
You can try holding down shift as you're trying to change the volume which iirc I added to try to use a finer resolution if possible (I can't double-check the source code until tomorrow or if that was only going to help classic skins as if depends on the way the request is done).
As the volume scale from what having winamp compatibility requires doesn't really fit into 1% steps as it's a 0-255 range which depending on the skin type & implementation either doesn't align nicely (as with classic skins) or depends on what the skin author may have chosen with modern skins or which way its triggered.
The volume tab on the playback preferences page is the only way to otherwise get an exact position in that 0-255 range mentioned above (along with other control options like using the OS process control instead which does more of a 0-100% range from what I remember whilst skipping wacup's control).
As the volume scale from what having winamp compatibility requires doesn't really fit into 1% steps as it's a 0-255 range which depending on the skin type & implementation either doesn't align nicely (as with classic skins) or depends on what the skin author may have chosen with modern skins or which way its triggered.
The volume tab on the playback preferences page is the only way to otherwise get an exact position in that 0-255 range mentioned above (along with other control options like using the OS process control instead which does more of a 0-100% range from what I remember whilst skipping wacup's control).
6
Preview Build Discussion / Re: [Bug] Ableton .asd files cause WACUP to lose metadata from .mp3 files
« on: April 02, 2026, 08:56:30 AM »
I don't get what the connection of a supporting file that shouldn't even be being touched when mp3 metadata is being read is here unless you're doing the import / metadata refresh when that other program has a lock on the file access which would prevent what I'm trying to do from working. If so I don't see anything obvious I can do for it other than skipping anything that I might be attempting if the file is locked (which I thought I was doing & if that's not right then that could explain the metadata disappearing).
7
General Discussion / Re: Wacup does not play the whole songs
« on: April 02, 2026, 08:43:51 AM »
1.99.45.23518 isn't the current build (there's also no stable wacup build & everything provided is a preview build to set expectations) & isn't even the 1.99.45 build that's still provided on the site as part of the old build archive.
1.99.47.23960 is the current build (as shown to be updated to) & is the one that would need to be tested against.
With the file seemingly not playing correctly, I don't know what output plug-in you're using, if things like silence skipping has been enabled or if it's a case of the mp3 header information being wrong for which I would really need a small example file if the suggestion below doesn't help.
Otherwise the only obvious thing to try without a file is to go to Preferences -> Plug-ins -> Input -> MP3 | WAV -> check the option for exact checking of mp3 length. As the build you're running turned that off by default after the one before it having it on by default & it causing a slew of performance issues. However the build that's still being worked on has a hybrid mode that tries to deal with badly formed files (e.g. vbr encoded files without some of the expected header which will clip playback in a manner that seems to seen) but that prefs option is the quick fix to see if that might be what's going on.
1.99.47.23960 is the current build (as shown to be updated to) & is the one that would need to be tested against.
With the file seemingly not playing correctly, I don't know what output plug-in you're using, if things like silence skipping has been enabled or if it's a case of the mp3 header information being wrong for which I would really need a small example file if the suggestion below doesn't help.
Otherwise the only obvious thing to try without a file is to go to Preferences -> Plug-ins -> Input -> MP3 | WAV -> check the option for exact checking of mp3 length. As the build you're running turned that off by default after the one before it having it on by default & it causing a slew of performance issues. However the build that's still being worked on has a hybrid mode that tries to deal with badly formed files (e.g. vbr encoded files without some of the expected header which will clip playback in a manner that seems to seen) but that prefs option is the quick fix to see if that might be what's going on.
8
Preview Build Discussion / Re: [BUG] Monitor disconnects break window positions
« on: April 02, 2026, 08:38:36 AM »
I cannot view imgur links so you need to attach it as I can't tell what skin you're trying to use (if it's a modern skin then there's bugger all I can do, if it's a classic skin there were some changes in 23960 that were an attempt to help if freeze was enabled but there's a point at which the OS especially if it's Win11 tries to "help" to keep windows not being off-screen).
9
Preview Build Discussion / Re: issues with wacup replay gain and mp3 metadata writing
« on: April 01, 2026, 12:20:19 PM »
It's just not a priority for me to work on something that is going to be a non-trivial set of changes for _both_ build types when I'm instead focusing this year working more on what is actually going to bring me enjoyment. If the x86 build is also not allowing for MP3 metadata updating then that means the in_mp3 from the 5.666 installer likely isn't present to use (or it's failing / being blocked) as that's the only way with the normal x86 install for MP3 writing to be attempted.
10
Preview Build Discussion / Re: issues with wacup replay gain and mp3 metadata writing
« on: March 27, 2026, 05:51:05 PM »
Metadata writing support in the x64 build for MP3 isn't yet implemented & is why the x86 build is still the preferred one for most to use.
11
Preview Build Discussion / Re: [Bug] Searching library with blank space " " returns incorrect/broken files
« on: March 24, 2026, 07:06:04 PM »
Thank you for reporting this as it's absolutely not the intended behaviour & until I've finished debugging this it appears to be allowing everything that's stored in the db to be shown which includes any failed imports or items that have been soft-deleted (done to make it easier to get back things such as if a drive goes offline during a scan so they go away but any custom metadata isn't necessarily going to be lost).
12
General Discussion / Re: Double clicking .wav's rapidly enqueue's the wav instead of playing immediately
« on: March 20, 2026, 05:17:05 PM »At any rate I really appreciate if you look into this behavior.I've had a look into this & have an initial set of changes for the next wacup build though how well it'll actually work for your needs I don't know. I've also not done any comparison testing against a winamp install as what it does really doesn't help in comparison to my code base & what I'm working with.
From what I could see under testing, wacup being slow to respond &/or duplicating things was due to how the initial batch handling is done which actually is processing the external command quickly but is causing all of the play message requests to stack up which depending on how many are made & other aspects I could easily make it take almost a minute for the wanted action to appear to finally happen. As it's trying to process every play request that's been given to it along with the related stop that goes on which slows down the ui responsiveness & makes it seem like there's no playback happening even though the play/stop is actually being processed with the stop happening before output is able to be properly constructed making it not play anything in that state (which is imho correct as it's just the handling dealing with things as quickly as it can & avoiding doing things that it's already determining aren't required as a very quick play then stop action will trigger).
What I've done is now try to check if there's already a pending play action in the message queue from any new external actions coming in & filter them to reduce the amount of reprocessing that might occur. Doing that helps avoid the unwanted adding of the items to the playlist when it should just be showing what's been added into it along with reducing the play messages that are being queued up which avoids what I described in the prior paragraph. I still don't know if that's fully resolved the extra items being added but so far I've not managed to see it occur including when using the behaviour that allows a folder to be passed & expanded so to me it seems better against what I've been able to test.
And final thing for now is that /clear <file> isn't a valid command-line action so that shouldn't have worked & seemed like it did due to what I've tried to describe above.
13
Preview Build Discussion / Re: Audio spectrum display issue
« on: March 14, 2026, 10:56:26 AM »
If it's in the buffering state then it means that the vis data vs the playing state has lost sync & it can't match what's playing against the samples that it's expecting to try to render. There is no configuration option available to adjust as it shouldn't be messing up & as you've mentioned streams, I'd need examples of the stream(s) having issues to determine if it's a format specific issue or streaming in general though I've not seen it happen from some recent re-testing but that might be I'm not having issues with getting enough stream data or things just keeping in sync so who knows. Also the output plug-in being used might affect things with notsoyasapi being known to cause a de-sync even with local files.
14
General Discussion / Re: Double clicking .wav's rapidly enqueue's the wav instead of playing immediately
« on: March 14, 2026, 10:51:01 AM »
I can't access anything from imgur as I'm geo-blocked by them since last year.
As for what's shown in the video, wacup is a different program to winamp so there are differences in behaviour & currently what you want it's command-line handling will not do as it's batching up requests coming in from the multiple spawned instances which was done as it helped with others double-clicking on a large selection where that otherwise would do more like you're wanting but wasn't what they wanted as it then lost files being added.
At this time wacup can't do what you need without either adding in another option to change the behaviour or for me to find a different way to achieve what is the intention of the handling whilst allowing quick additions to work. As for the /clear aspect, it does work but it's covered as part of the batch handling so it cannot do what you're currently wanting & maybe just having that not be handled by it might be the quicker way to get closer to what you're wanting but I won't know until I allocate time to look into it.
As for what's shown in the video, wacup is a different program to winamp so there are differences in behaviour & currently what you want it's command-line handling will not do as it's batching up requests coming in from the multiple spawned instances which was done as it helped with others double-clicking on a large selection where that otherwise would do more like you're wanting but wasn't what they wanted as it then lost files being added.
At this time wacup can't do what you need without either adding in another option to change the behaviour or for me to find a different way to achieve what is the intention of the handling whilst allowing quick additions to work. As for the /clear aspect, it does work but it's covered as part of the batch handling so it cannot do what you're currently wanting & maybe just having that not be handled by it might be the quicker way to get closer to what you're wanting but I won't know until I allocate time to look into it.
15
Preview Build Discussion / Re: [BUG] Waveform Preview No Rendering in new build
« on: March 13, 2026, 02:06:53 PM »
That's good to know that you manged to get things working. Am also wondering if some of the network path handling changes made in the builds from this year could've helped where it was incorrectly failing on trying to access such paths where the status wasn't certain which caused it to generically fail any access attempt when it should've made an attempt (as it now does). That path handling also got an option to allow for it to be disabled via the second options page of the advanced prefs page.