Latest restricted WACUP beta release is build #18916 (April 18th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #18916 (April 18th 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.

Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
General Discussion / Re: WACUP does not merge albums, instead creates duplicates
« Last post by toribyte on March 19, 2024, 12:16:08 AM »
Thank youuuuuuuuuuuuuuuuu ;D ;D ;D ;D ;D
42
General Discussion / Re: WACUP does not merge albums, instead creates duplicates
« Last post by dro on March 18, 2024, 10:50:46 PM »
It's based around using 'album artist' for the matching with it then falling back to 'artist' if that doesn't exist (depending on the config options used). For vgm based sets as that looks like it might be, I know for some of them they often don't seem to want to group nicely as the album artist is somewhat treated as a per-track artist field.

The solution is to either try to re-tag them (which if it's vgm sets would mean that it's just custom metadata being stored in the local library db & not the actual files as writing tags for most of them often isn't supported) which'd then get things to group correctly but is relying on the db being maintained (which is probably why it's messed up if you had to start over). The other option would be to go to preferences -> media library -> local library -> uncheck the option to use 'album artist' & it'll then just look at 'artist' & that might be a better fit for the media you're using (is notes with that option about the recommended option above).

-dro
43
General Discussion / Re: WACUP does not merge albums, instead creates duplicates
« Last post by toribyte on March 18, 2024, 10:32:59 PM »
I don't know why it does this to some albums w/ various artists, but leaves some of the others intact.
44
General Discussion / WACUP does not merge albums, instead creates duplicates
« Last post by toribyte on March 18, 2024, 09:25:10 PM »
This, for some reason, only applies to my albums involving various artists.

Background: Because an unrelated program would not launch (instead as a background process), I had to clean reinstall my computer, but I had to rebuild my media library once I reinstalled WACUP. But for some reason, unlike last time I had this app, the library separates certain albums (like I said, when multiple artists worked on that album). Is there any way to "merge" them?

45
Wishlist / Feature Requests / Re: ML History View Column Heading Change
« Last post by Aminifu on March 07, 2024, 06:41:45 PM »
...

Will add the request to refresh the existing history titles to the todo list.

-dro

Thank you.
46
Wishlist / Feature Requests / Re: ML History View Column Heading Change
« Last post by dro on March 07, 2024, 05:46:09 PM »
I get the potential for confusion but I also think that there's enough context between title as a metadata field & title as a formatted string for it to not be a problem & as such I'm not going to change the column name as that's then introducing more disparity into things vs existing usage of the term.

Will add the request to refresh the existing history titles to the todo list.

-dro
47
Wishlist / Feature Requests / Re: ML History View Column Heading Change
« Last post by Aminifu on March 07, 2024, 04:41:17 PM »
"Playlist String" or something like that. I noticed this when I changed the PE ATF string I was using and saw that that column contents changed to match it. Older records used the previous PE ATF string. Not necessary, but would it be possible to add an option to update old records to match the active PE ATF string.

Since I'm using 3 different ATF strings in different places for the playing file, I've now changed the PE string to only show %title% and thus match the column heading in the history view.

Things could stay as they are, changes are not really necessary. Once I noticed this behavior and realized it wasn't an history view error in reading metadata, I decided to mention it.
48
Wishlist / Feature Requests / Re: ML History View Column Heading Change
« Last post by dro on March 07, 2024, 04:15:12 PM »
So what should the column name be? I am going to note that pretty much everything else I can see is using title for the pre-generated strings (main & library playlists, bookmarks, podcast downloads) & it's only the local library where there's a difference only due to how it's interaction with the lower level metadata.

-dro
49
Wishlist / Feature Requests / ML History View Column Heading Change
« Last post by Aminifu on March 07, 2024, 04:03:06 PM »
The column currently named "Title" in the history view doesn't display the file's title. It displays the playlist editor's string for the file that was played. I suggest the column's heading be changed to correctly indicate what is being displayed (or change the column's content to match it's heading).
50
Preview Build Discussion / Re: WACUP - First experiences, bugs, wish list
« Last post by dro on March 07, 2024, 01:58:43 PM »
The request for more / all of the generic embedded windows to be accessible via global hotkeys has now been internally implemented with any of those windows being automatically made into an available hotkey action to be able to toggle the window state.

-dro
Pages: 1 ... 3 4 [5] 6 7 ... 10