Messages

1

General Discussion / Re: Drag and drop a music folder with a playlist file adds duplicate files

« on: November 24, 2023, 11:01:16 AM »

I get what you're describing, I just don't remember it as being a thing Winamp would do from having previously worked on it to ignore playlists found within drag+drop actions though I see 5.666 acting as described from a quick re-test so I guess my memory of things isn't all that great nowadays. Maybe I need to consider adding in an option to ignore playlist files on drag+drop actions.

De-duplicating what WACUP adds from drag+drop actions along with trying to use the playlist ordering &/or metadata to get the expected track order to deal with Explorer not often providing files in the expected order (due to file creation, selection quirks in Explorer) is something already on my list of things to do. So doing all of that might be the more sensible thing to do with my time vs an option that imho could cause more issues than it helps, will have to have a think & see when I can schedule it into things.

-dro

2

General Discussion / Re: Drag and drop a music folder with a playlist file adds duplicate files

« on: November 24, 2023, 01:31:35 AM »

No such option currently exists & a smarter handling of drag+drop still needs to be coded so for now it'll just add what it's given even if that then duplicates things. I'm also not aware of Winamp having done any filtering of things either since both programs just parse the given list of files from the drag+drop action.

-dro

3

Preview Build Discussion / Re: Media Library refresh should be more clever

« on: November 20, 2023, 03:22:20 PM »

Without trying it out I'm not sure but it's something I've got on my of things to consider once I can be certain of the core input plug-ins being able to cope with it. The folder monitor handling is itself multi-threaded so it checks for files to consider & then hands that over to a different thread which then does the metadata reading allowing for the initial scan to generally take less time. That's still hitting multiple files on the drive at the same time due to the overlapping of things relying somewhat on the OS / file system cache to minimise the effect of it.

-dro

4

Preview Build Discussion / Re: Media Library refresh should be more clever

« on: November 20, 2023, 01:42:57 PM »

I think I see what the some of the confusion is now I've had a look back at what the ml_local options were.

The ml_ll refresh option is intentionally set to re-read the files because the modified file time can't always be relied upon as there's tools that don't always modify it whereas ml_local offers a differently named option that is a trigger option for its watch folders feature which afaict would just look for overall file differences (time changed / not present).

I will look to add an equivalent folder monitor trigger to ml_ll's library button sub-menu though I'm likely going to do it so specific folder monitor entries can be triggered for those that are enabled at the time or something along those lines (will see what happens when I start coding things).


The ml_ll folder monitor is equivalent to ml_local's watch folder handling & it should be importing the folder list from ml_local's settings though the comment about it being enabled by default, I'm not sure what's meant by that. As the prefs is always going to be there & the logic is if it's present in the imported settings then any folders should be auto-enabled on an ~6hr default interval between scans vs any other config options such as how it's done on initial loading (as unlike ml_local I try to avoid it spinning up too soon if doing quick load & close / post-crash issues).

There's even an option on the import folder dialog which allows for them to be added to the folder monitor but that isn't enabled by default because I've seen too many cases of sub-folders being added which'd then cause the folder monitor to be looking at many folders when it's not appropriate - maybe that's what is being referred to as not enabled by default ?


One final thing, ml_ll's metadata reading is more involved than ml_local's since it collects more information about the files such as format information & associated albumart which obviously can take longer to determine per file despite doing what is reasonable to try to minimise how long it overall takes to do all of that.

So even if it only takes a few milliseconds per file (which isn't bad), that over 250k of files is going to easily be in the 12-15min range & I have been debating making ml_ll look at 2 files at a time instead of just 1 which could reduce the overall time but it could be slower depending on the drive contention & how well the input plug-ins deal with multi-threaded access (there's some that don't like it at all).

-dro

5

Preview Build Discussion / Re: Global Hotkey combination (ALT+anything) not working only for "Playback: Stop"

« on: November 13, 2023, 01:35:20 PM »

It depends on the feature & in some respects I'm less modular than Winamp due to having integrated a load of my Winamp plug-ins into the WACUP core where often it's just a few lines of code to do what's actually needed vs a multi-KB dll & bumping the overheads for things to achieve it (which was how it had to be done as a plug-in but as I've got my own core I can integrate things more easily even if it's not necessarily the cleanest of ways of doing it).

It also doesn't help that Alt is a bit of a weird key with how it can be handled at times & along with seeing ghost responses of the mouse still being clicked as part of the checks I was doing to try to allow the Alt based hotkey actions through it meant not only was Alt+<key> incorrectly toggling the next on stop option it could also be toggled afterwards at times along with the overall issue of not being handled as intended.

-dro

6

Preview Build Discussion / Re: Global Hotkey combination (ALT+anything) not working only for "Playback: Stop"

« on: November 13, 2023, 12:58:48 AM »

It's hard-coded handling within the core to help the hotkey plug-in with some other reported Alt+<modifier>+<key> issues, just it didn't allow for the simpler Alt+<key> to work correctly all of the time & needs a newer WACUP core dll & hotkey plug-in to resolve it. So not something that can be disabled to workaround it - only option for that would be going for Alt+<modifier>+<key>

-dro

7

Preview Build Discussion / Re: Global Hotkey combination (ALT+anything) not working only for "Playback: Stop"

« on: November 10, 2023, 12:53:45 PM »

It's a processing conflict with the 'advance to next on stop' option which is handled via Alt+Click & due to how the stop hotkey is sent the handler isn't seeing that it's from within a hotkey action & so toggles that option instead of doing the stop that's wanted. Will look to get it fixed for the next build.

-dro

8

Wishlist / Feature Requests / Re: Two little requests from someone using winamp for 20+ years

« on: November 06, 2023, 03:46:54 PM »

That shouldn't be needed now with the handling that's in place to try to maintain the shuffle table between sessions (as long as what's in the main playlist doesn't massively change between instances). It even tries to avoid including items already played if what's in the playlist has changed to only account for what's left to be played (which can be monitored via the diagnostic prefs pages).

Winamp had those issues in not being able to maintain things & yes shuffle off & manually triggering the randomise is the other way to see what's going on _but_ for WACUP which hasn't relied on Winamp's handling for shuffle / randomise in many years now, both shuffle & random actions go through the same code, it's just whether the main playlist queue list or the shuffle list is the one that gets updated.

-dro

9

General Discussion / Re: Can I sync an Ipod classic to my Wacup Library?

« on: October 31, 2023, 10:34:07 PM »

Did you also try using ml_ipod instead of the ml_pmp / pmp_ipod option ?

-dro

10

General Discussion / Re: Plug-in

« on: October 31, 2023, 10:32:51 PM »

I'll have to re-check things as I thought I'd made the portable install mode show an appropriate error description message within the plug-in prefs pages for this scenario.

-dro

11

Preview Build Discussion / Re: OGG files not playing in Public Preview v17040

« on: October 31, 2023, 05:00:52 PM »

There's nothing extra needed for OGG playback during the install process as long as it was selected in the installer (i.e. in_vorbis.dll in the plugins folder & libvorbis.dll in the root of the program install folder).

If disabling the other input plug-ins didn't help then me trying to find old copies of the plug-in from the betas isn't going to help (is also limited due to how some internal aspects changed in the month before the preview builds started being updated again) as I've got no idea where in the 2.5yrs an issue may have arisen as the plug-in not only does it's handling but it pulls in other aspects from the wacup core.

Just for my dwindling sanity, could you provide a small sample ogg file (can pm it) so I can double-check if it also fails for me or not. Otherwise at the moment I'm still trying to get things to a point to be able to do a newer preview build for the other issues that have come in from the past month & changes I've tried to make to deal with one possible idea in the handling of the libvorbis.dll delayed loading that the in_vorbis.dll uses.

-dro

12

General Discussion / Re: Plug-in

« on: October 31, 2023, 10:50:14 AM »

What is the message shown next to the disabled icon ? As that should indicate why it's not being loaded & there's no hard-block on the loading of dsp_iZOzoneFree.dll (is the filename I'm aware of being used by others as part of the patching that's attempted on it to resolve some issues it has).

Or have you installed WACUP as a portable install ? As that will prevent 3rd party plug-ins from being loaded unless you go to preferences -> advanced -> portable mode & use the option on there to allow 3rd party plug-ins to be loaded.

-dro

13

Preview Build Discussion / Re: OGG files not playing in Public Preview v17040

« on: October 27, 2023, 10:38:59 PM »

Am not seeing any duplication of OGG in there & it's matching up with what I'm seeing in a normal install (only problem is the formatting issue for some of the entries towards the end of the file that I'm not seeing from the test setups I've re-checked). Other than trying to disable some of the input plug-ins & see if that then allows things to play, I can't think of anything obvious without waiting for a newer build to see if that makes any difference or not as part of some changes I've made related to one user I know was having OGG file lock-up issues though that doesn't seem like this is the same issue.

-dro

14

Wishlist / Feature Requests / Re: Lock process volume level changing at 100%

« on: October 27, 2023, 10:19:57 PM »

That's the only option I can really suggest unless someone else knows of a different midi plug-in that can be used.

-dro

15

Preview Build Discussion / Re: OGG files not playing in Public Preview v17040

« on: October 27, 2023, 05:54:21 PM »

Have you installed any other input plug-ins from those that come with WACUP ? It might be best to go to preferences -> advanced -> diagnostics -> file associations & use the save option & attach it in reply to here please.

-dro