Latest WACUP public preview for x86 & x64 is build #24784 (August 3rd 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24784 (August 3rd 2026) (x86 & x64 changelogs)

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.


Messages - dro

Pages: [1] 2 3 ... 142
1
Neither do I hence adding in what length is reported to the error message to try to give me something to figure out why you keep saying it's broken for you. For reference I don't proactively use the scrobbler mode so there's a whole entirety that it's just shit / broken / never right.

2
As I cannot replicate this or it's potentially expected per my prior reply with network shares & items not already pre-cached into the local library then all I can I do is add what was internally obtained as the length & report that as part of the error message to try to diagnose it.

Alternatively for now you can trying checking the option on the scrobbler page to allow shorter durations to be sent & assuming network shares are still involved, go to preferences -> advanced -> options page 2 -> un-check the network file path checking option on there.

Also apply the post-release updates if not already done as the about|updates page showed there ones pending being applied.

3
What are you actually trying to achieve?

4
I assume it's https://getwacup.com/community/index.php?topic=2059.0 that you're referring to as the prior thread which was locked which was done since it was reported as being resolved. I'll have to look into this as I'm not seeing it showing 0:00 but something doesn't look quite right with the time that's being reported in either of the playlist elapsed / remaining modes (the single playlist item seems to be ok). I've also moved this into a more appropriate part of the forum (not sure why visualisation was chosen).

[edit]
I see why it's not working though I'm also going to have to do something to try to reduce the time that it takes to calculate things as it's too slow for either of the playlist* display modes & is also potentially behind some of it showing just as the playing position.

5
General Discussion / Re: Classic Skin Window Layout Storage
« on: Yesterday at 04:43:16 PM »
Multiple installs or messing with shortcut parameters after using the new instance handling via the Ctrl+Alt+N shortcut to copy the original settings folder into multiple ones & then using them as per https://getwacup.com/community/index.php?topic=839.msg5186#msg5186 (e.g. /NEW /INIDIR="folder" /CONFIG="folder\winamp.ini" for the same install but different config folder handling).

6
General Discussion / Re: Enhancer DSP
« on: Yesterday at 04:11:45 PM »
I've got a change for the next build which hopefully will help get the enhancer window position being maintained again despite it always wanting to put it over the position of the classic skin's main window. As there's some instances where it won't always save out the position I'm trying to track on closing & there's something odd with the timing of things during the first plug-in load which made it ignore what I was trying to make it use instead of it's own intended position.

7
Resolved Issues / Re: bugs in version 1.99.45.23528
« on: August 11, 2026, 06:35:43 PM »
If the portable install works & the other when updated to use the same version doesn't then it's most likely an odd config problem since the skin shouldn't matter especially if set to a classic one. Other than bundling up the broken installs main set of config files so I can have a look at them I'd rename the winamp.ini to something else & then run it again to see what that does (it'll reset most settings & window positions but is the simplest way to see if it's likely the main config file at fault).

8
Thank for confirming the sort of workaround works & should save you having to reset it every time.

9
Wishlist / Feature Requests / Re: Play Tracking Preference Not Saving
« on: August 09, 2026, 10:02:10 AM »
The preview box showing text is wrong so that's now fixed for the next build. Otherwise the action is working correctly against what I'd tried to do vs the original behaviour so it'll leave what's in the file as was last set when playback stops instead of clearing it (maybe that needs to be a dedicated mode possibly via another options from the dropdown assuming it actually makes sense to implement that).

A space character not being maintained is due to the handling stripping off whitespace characters when the formatting strings are processed. The simplest way to ensure you will have a space / effectively empty output no matter is to use $char(32) as the formatting string. You could also use $crlf() which just outputs a linebreak & should still do the same as the $char mode.

Also I've only checked this against the current (as of this reply) 1.99.53.24784 build.

10
Resolved Issues / Re: Jump to file with space in filename fails
« on: August 04, 2026, 04:36:55 PM »
I've uploaded a post-release update for the jtfe plug-in (can be accessed via preferences -> about|updates -> about tab or the OS toast that might appear) which should now do like with 24626 & earlier with spaces in the search whilst keeping the internal processing optimisation that inadvertently broke things.

11
Resolved Issues / Re: [FIXED] v1.99.53.24778 installation crash
« on: August 04, 2026, 02:01:23 PM »
Thanks for the confirmation that it's back to working ok again for you (I assume it'll help for the others though I've not had confirmation from them yet). Was an oversight as part of some changes made to reduce the code size of a few of the dlls whilst also reducing the code complexity with loading things but it didn't behave correctly during some new / incomplete updates. Main thing is that it's now been resolved.

12
Resolved Issues / Re: Jump to file with space in filename fails
« on: August 03, 2026, 09:45:56 PM »
I made an optimisation that isn't behaving correctly which I hadn't noticed as I'd only been doing single word searches & none of the beta testers had mentioned it being an issue vs the other changes made to the jtfe plug-in to resolve other ui hang / crash related problems. Will try to have a look into it tomorrow or Wednesday & put up a post-release update to fix it once I'm in a position to debug it (is too late now).

13
Resolved Issues / Re: v1.99.53.24778 installation crasg
« on: August 03, 2026, 08:27:20 PM »
1.99.53.24784 is now up which should resolve the problem with the installer crashing.

14
Resolved Issues / Re: v1.99.53.24778 installation crasg
« on: August 03, 2026, 11:49:15 AM »
I've tentatively already figured out the cause before I had to go out this morning but I need to do a bit more testing along the with checking out a few other things raised before I put up what should be a fixed installer later today.

15
Resolved Issues / Re: v1.99.53.24778 installation crasg
« on: August 03, 2026, 08:26:26 AM »
It's not something I've seen so I'll have to see if I can replicate the installer crashing later today as you're now the second person that's let me know something isn't right.

Pages: [1] 2 3 ... 142