Latest restricted WACUP beta release is build #19100 (May 10th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #19100 (May 10th 2024) (x86 only)


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 - jim2005

Pages: [1]
1
Preview Build Discussion / Re: Media Library refresh should be more clever
« on: November 19, 2023, 11:09:50 AM »
The recent beta releases have a feature in the preferences media library group called folder monitor that does what you're asking for. I don't know if it is also in the current public release. Look for it.

I checked it and it, happily, exists in the preview build too. It was disabled in my installation. Is it (i.e. disabled) the default setting? If yes, I think it should be changed since it's an easily overlooked option.

Now that I have enable it, WACUp detects folder structure and metadata changes (like lyrics).
Many thanks!

2
Preview Build Discussion / Media Library refresh should be more clever
« on: November 18, 2023, 10:33:16 AM »
Hello,
I think this is a bug, not a future request.

In Winamp 5.x (as well as in the previous WACUP preview, or so it seemed to me), refreshing the Local Library was very quick. Somehow the Media Library plugin was able to detect the changes in the metadata or the file structure of the library and scan only those files that had really changed.

Since the build #17040 (I guess this is the first time ml_ll plugin was introduced in public builds, pls correct if I'm wrong), when I perform a "Refresh metadata for all library item(s)"), the whole library structure is scanned as if it was the first time. Result is that the time to complete this action is very long (my library consists of 250,000 songs) and it's always this long even when the changes are very small (e.g. adding a file or changing ID3 metadata in a dozen of songs). I pruned and compacted the library but (unsurprisingly) it didn't improve.

Am I missing something? Is it a feature to be implement on a future build?
Is it possible to temporarily switch to the legacy (ml_local ?) plugin (and where can I obtain it?) in order to check if it worked better?

Thank you

Pages: [1]