Messages

31

General Discussion / Re: Wacup in IDLE uses up performance

« on: April 07, 2025, 07:36:57 AM »

What happens if you use the base classic skin? Most likely it's something about the re-used modern skin engine plug-in & how it copes with higher than 60fps displays (not something I can currently try out myself).

32

Skins / Re: Winamp Modern Updated for WACUP

« on: March 28, 2025, 04:42:44 PM »

You need to re-read the information on the x64 download page or from within the wacup installer.

33

Wishlist / Feature Requests / Re: Portables Support

« on: March 28, 2025, 04:10:21 PM »

The portable install type limits what plug-ins are going to be loaded to only those known to the safe in that mode (unless prefs -> advanced -> portable mode -> use 3rd party plug-ins has been enabled) though I don't remember the ml_pmp plug-in being blocked from loading in that mode other than first having to got to prefs -> plug-ins -> media library to ensure it's been enabled from there. WACUP in its current state is likely not a viable option for you if portables support is something you really need to have working as I just don't have any eta on when I'll eventually get around to replacing the plug-in with my own.

34

Wishlist / Feature Requests / Re: Portables Support

« on: March 28, 2025, 09:11:48 AM »

The WACUP installer already tries to install a copy of the portables plug-in (ml_pmp, pmp_*) from 5.666 but it's not enabled by default to avoid some of the issues that the plug-in had even under a native 5.666 install which requires it being enabled via preferences -> plug-ins -> media library -> finding ml_pmp & checking the option to enable it. Using any copy of that plug-in which isn't from the specific 5.666 installer that WACUP is using to get winamp files from isn't going to work & will very likely induce more possible crashes than can already happen with that plug-in.

The problem with the portables plug-in has always been it can work for some but it won't work for others & is why it's not enabled by default. Also using any form of that plug-in especially from after 5.666 isn't supported nor meant to be allowed & if it crashes there's nothing I'm going to even consider to do about resolving those problems.

With the local library idea, if the drive is mapped to the same letter on all instances of trying to use it then it might work but like you note it's not great & is clunky even if making use of the manual option to remove missing files or by using the folder monitor feature to have it periodically scan for & hide the portable entries within the db instance via the soft delete that it uses for the handling of missing files. That's the only thing I can think off if the original 5.666 form of the plug-in can't be used per the start of the reply (that might require re-running the installer to ensure the expected versions of the plug-ins are present).

35

Wishlist / Feature Requests / Re: ATF support for Last.fm scrobble fields

« on: March 26, 2025, 04:01:52 PM »

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.

36

Wishlist / Feature Requests / Re: Options for the Lyrics Plug-in

« on: March 26, 2025, 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.

37

Wishlist / Feature Requests / Re: ATF support for Last.fm scrobble fields

« on: March 25, 2025, 07:27:18 PM »

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.

38

Wishlist / Feature Requests / Re: ATF support for Last.fm scrobble fields

« on: March 25, 2025, 11:56:35 AM »

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.

39

Preview Build Discussion / Re: Unpausing a radio stream after few minutes makes WACUP skip to next entry

« on: March 23, 2025, 09:30:16 AM »

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.

40

General Discussion / Re: Plantages à répétition - Repeated crashes (solutionné)

« on: March 22, 2025, 10:55:02 AM »

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.

41

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.

42

Wishlist / Feature Requests / Re: Extra Space to Drag N Drop to the playlise....

« on: March 20, 2025, 12:03:03 PM »

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.

43

Preview Build Discussion / Re: "the visualisation plug-in executed illegal operation."

« on: March 18, 2025, 12:44:08 PM »

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.

44

Preview Build Discussion / Re: "the visualisation plug-in executed illegal operation."

« on: March 17, 2025, 07:38:16 PM »

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.

45

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).