Latest WACUP public preview for x86 & x64 is build #21136 (March 9th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #21136 (March 9th 2025) (x86 & x64 changelogs)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

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 ... 115
1
For the next build I've changed the string I'm getting back from the metadata reading library to use commas instead of spaces if it needs to combine duplicate fields together which I hope will do what you're wanting (i.e. acting like the left of the example image instead of the right). This will require a local library refresh to be done for the change to be seen if using any files known to that part.

2
Wishlist / Feature Requests / Re: Options for the Lyrics Plug-in
« on: Yesterday at 10:06:21 AM »
The way the cache works is all implementation details & it's already changed since it was first introduced so making it human readable isn't something I'm going to do for it as that's not the point of it. That's where a mode to try to store the lyrics into the file is still on the todo list. It's also why I'm using a hash based on a few factors instead of metadata for the filename as that makes things simpler for what I need to do whilst also avoiding creating potentially long filenames that cause other issues.

The point of the cache file is to avoid re-querying for the lyrics whether it was able to be found or not (hence the empty file) otherwise it can be triggering multiple online look-ups when that's just not a good use of resources especially if there's no results. The one thing I have forgotten to do is have the cache get pruned to prevent it growing too large (like is done for the artwork) so I'll need to add that & I'll also consider adding options like with the waveform seeker plug-in where it has a clear cache & clear cache on exit options which doesn't do what you're wanting but balances things out a bit between the request & what I'm wanting the cache to do.

3
Would you expect the first 'artist' to be used in that instance? I'm not sure without looking into it what last.fm is doing with possible multiple artists for a song. I'd also need to look into what's going on with the tag reading library I'm using to see what it can do or what I'll need to do with the provided string from it.

4
Can you give me an example of the issue? As I'm not sure how adding ATF support would help since that in itself would be relying on title, artist & optionally track, album & albumartist metadata being right to start with unless it's about splitting multi-part values (on artist & albumartist I assume) & if so it might be simpler to have a mode that just tries to get the first value up to a comma or a slash vs ATF overhead.

5
Which build type of wacup & version of it are you using? Also is it an MP3 or AAC based stream or something else? Though imho pausing streams is never going to work right as there's a limit on how much steam data is able to be buffered before the limit is reached or connections get closed from being unresponsive.

6
I forgot to update the summary known_issues.html page (will get that done now) though the /preview/ or /preview_x64/ page have a link to the current known issues page that the to be updated known_issues.html page links to. No need to apologise as not finding things is on me. Main thing is that unchecking that option has resolved the crashing you were experiencing.

7
General Discussion / Re: Plantages à répétition - Repeated crashes
« on: March 21, 2025, 01:42:25 PM »
Per the known issues on the preview build download page, go to Preferences -> General -> Windows 10 | 11 & disable the SMTC feature to resolve this crash issue.

8
It doesn't seem natural to do it & is why I think it's easily missed but the main thing is it helps you do what you were wanting to achieve.

9
The main part of the issue is from when I added in running / stopped status text to the menu items & that broke some of the handling used to figure out what's being worked with. This is going to essentially require selecting the none option & then re-configuring the plug-in to use which isn't something I'm going to have the installer try to do as there could also be prior setups where it's still working ok since going over 2 vis plug-ins was also triggering some weird handling issues with everything else that had changed since this was first added.

There's also some message handling changes due to working with modern skins that inadvertently broke things with trying to batch turn the plug-ins off so that's now been modified to hopefully be better behaved even if the vis might cause a crash (as they can do) by at least clearing out the config settings before things are messed around with. Hopefully all of that will manifest as working ok when the build is up.

10
The feature is broken when it comes to the menu handling & probably more now I've started having a look into this. So its not updating the config file & depending on how things are reacting it may or may not allow the actions to start the plug-in which likely aligns with what was reported. This isn't a feature I often use so I'm still trying to determine when I broke it but will look to get it working again for the next build.

11
Preview Build Discussion / Re: Crashing issues
« on: March 15, 2025, 09:45:24 PM »
Not to worry & main thing is it's behaving with that option off until the next build with the needed fixes is made available hopefully towards the end of next week (as of this reply).

12
With classic/ 2.x skins like you screenshot then if you make the drop on the bottom area of the main playlist window outside of where the list contents are shown then it should add those new items a t the bottom of the playlist even if that's not where the contents are showing. The same also applies to the top area of the window iirc. For winamp3 / modern style skins that handling isn't supported due to how they're implemented.

I'm not going to add empty space especially as unlike winamp I have it coded my main playlist implementation to be able to show partial playlist lines at the bottom instead of clipping things to full lines & being more confusing imho when trying to work out if there is more still to be shown or not.

13
Preview Build Discussion / Re: Milkdrop
« on: March 14, 2025, 07:30:03 AM »
Nope as that's a standalone program (i.e. has no plug-in code integration now I suspect due to what it was forked from) nor am I aware of it having had its source code made available at this time. It'd likely be more work than it's worth trying to merge anything even if its code changes were available into the 2.25 based code I've been iterating upon.

14
Preview Build Discussion / Re: Crashing issues
« on: March 13, 2025, 10:15:58 PM »
You shouldn't post crash reports publicly & I've now removed it though have kept a copy to look at when I'm back on the PC.

As for this beta preview build crashing it's in the known issues section of the download page as to what is the likey reason for it to crash (as I've not flagged the build as being one for most builds to update to) & the workaround if your install isn't getting the pot release fixed plug-in via the crash reporter (something I need to resolve before a new build is formally released).
Quote
If the SMTC feature is enabled (Preferences -> General -> Windows 10 | 11) it can trigger a crash due to a change in the build that was incorrectly applied.

15
I'll have to recheck multi-vis handling & get back to you.

Pages: [1] 2 3 ... 115