91
Wishlist / Feature Requests / Re: Portables Support
« Last post by EighthSageScarlet on March 28, 2025, 02:08:04 PM »Further investigation has revealed that the 32 bit portable install does have the pmp plugins included.
Latest WACUP public preview for x86 & x64 is build #21136 (March 9th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #21254 (March 29th 2025) (x86 & x64 changelogs)
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
92
Wishlist / Feature Requests / Re: Portables Support
« Last post by EighthSageScarlet on March 28, 2025, 01:47:03 PM »Edit:
So I checked the portables plugin in the installer, yet I cannot find the plugin in Media Library now either. I have looked where you directed, and have even searched the x86 install Plugins folder for files containing "pmp" to no avail. Is it possible you removed it from the most recent 32 bit distribution as well? Or am I just doing something wrong?
93
Wishlist / Feature Requests / Re: Portables Support
« Last post by EighthSageScarlet on March 28, 2025, 01:34:55 PM »I was not able to find a copy of any pmp plugins in my install despite plugin_descriptions.ini listing them. I have messed around with the files so I will do a complete fresh reinstall to make sure I didn't somehow delete the native files accidentally, but I was pretty sure I looked at all of the plug-ins available when I installed the first time. It is completely possible that I missed it.
I will report back shortly.
I will report back shortly.
94
Wishlist / Feature Requests / Re: Portables Support
« Last post by dro 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).
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).
95
Wishlist / Feature Requests / Portables Support
« Last post by EighthSageScarlet on March 27, 2025, 07:44:37 PM »This has been touched upon in other forum posts (ie. https://getwacup.com/community/index.php?topic=703.0) but not (as far as I can see) in a request.
Winamp has a plugin that nicely cooperates with plug-and-play media such as a thumb drive. I've already tried to directly transplant this plugin and it appears to be incompatible with WACUP entirely. What I want is to be able to have a music library on a thumb drive that I can transfer between different devices without having to use each machine's space. This can be done in a somewhat ad-hoc way by adding the thumb drive's directory to the local library, but when I eject the drive the local library maintains references to all of the music without being able to access it, which clutters the library with songs I cannot play. In Winamp this is solved by a plug-and-play entry in the left hand side of the media library window, where you can access the thumb drive's "sub-library" of music, and that tab just disappears when the external drive is absent.
In the above forum post you mentioned this was low on your priorities list, so perhaps if you know of a better workaround, or some way to cannibalize the Winamp plugin to work with WACUP then advice would be greatly appreciated!
Winamp has a plugin that nicely cooperates with plug-and-play media such as a thumb drive. I've already tried to directly transplant this plugin and it appears to be incompatible with WACUP entirely. What I want is to be able to have a music library on a thumb drive that I can transfer between different devices without having to use each machine's space. This can be done in a somewhat ad-hoc way by adding the thumb drive's directory to the local library, but when I eject the drive the local library maintains references to all of the music without being able to access it, which clutters the library with songs I cannot play. In Winamp this is solved by a plug-and-play entry in the left hand side of the media library window, where you can access the thumb drive's "sub-library" of music, and that tab just disappears when the external drive is absent.
In the above forum post you mentioned this was low on your priorities list, so perhaps if you know of a better workaround, or some way to cannibalize the Winamp plugin to work with WACUP then advice would be greatly appreciated!
96
Wishlist / Feature Requests / Re: Options for the Lyrics Plug-in
« Last post by Aminifu on March 27, 2025, 04:37:56 AM »Ok, I better understand why you have things implemented the way you have. If you decide to add the options mentioned, they could be a useful addition instead of what I asked for. After I add or correct the metadata in my files, I make them read-only to prevent inadvertent changes. So, a mode to store lyrics in the files themselves would not be useful for me. I don't need to prune the entire cache, I just wanted to prevent the empty files. What would be considered too large a cache?
Sometime I use playlists that only contain instrumental songs. It would be just as fast to disable the lyrics plug-in in this case, than enabling an option to not create text files. Those that mix file files with and without lyrics in the same playlist will have to find their own solutions for not wasting directory name space on intentional empty files.
I have been deleting the empty files to force re-querying for lyrics in case they may be found later, when the same files are played again. I understand why you don't want to trigger multiple online look-ups. I think it would be worth the resources used if lyrics are found later. I will stop deleting the empty files, if you think the re-querying will lead to crashes or other processing errors in WACUP. Wasting directory name space is worth it if it prevents WACUP processing errors, imo.
During a session, I have been adding the song titles above the start of the lyrics in the text files, after they finish playing. From time to time, there are errors in the lyrics found online that I have been correcting manually. During a session, I make notes of which files need corrections and these titles help me find these files faster in between sessions, when I make the corrections.
Reasonable people can always disagree on the best way to handle things. Whether I agree with your design decisions or not, I want you to know that I appreciate all you have done and continue to do that makes WACUP better than Winamp was, imo. I don't expect WACUP to do everything the way I would like things done. Expect for real bugs, I learn to work with the ways things are done in WACUP and the skins. In case of skins, I sometimes make small changes in some of their image and script files, when possible, to have them look and work more to my liking, for my personal use.
Sometime I use playlists that only contain instrumental songs. It would be just as fast to disable the lyrics plug-in in this case, than enabling an option to not create text files. Those that mix file files with and without lyrics in the same playlist will have to find their own solutions for not wasting directory name space on intentional empty files.
I have been deleting the empty files to force re-querying for lyrics in case they may be found later, when the same files are played again. I understand why you don't want to trigger multiple online look-ups. I think it would be worth the resources used if lyrics are found later. I will stop deleting the empty files, if you think the re-querying will lead to crashes or other processing errors in WACUP. Wasting directory name space is worth it if it prevents WACUP processing errors, imo.
During a session, I have been adding the song titles above the start of the lyrics in the text files, after they finish playing. From time to time, there are errors in the lyrics found online that I have been correcting manually. During a session, I make notes of which files need corrections and these titles help me find these files faster in between sessions, when I make the corrections.
Reasonable people can always disagree on the best way to handle things. Whether I agree with your design decisions or not, I want you to know that I appreciate all you have done and continue to do that makes WACUP better than Winamp was, imo. I don't expect WACUP to do everything the way I would like things done. Expect for real bugs, I learn to work with the ways things are done in WACUP and the skins. In case of skins, I sometimes make small changes in some of their image and script files, when possible, to have them look and work more to my liking, for my personal use.
97
Wishlist / Feature Requests / Re: ATF support for Last.fm scrobble fields
« Last post by obli on March 26, 2025, 05:01:34 PM »Awesome! Thank you! Exactly what I was hoping for so long as there's a space after the comma like "Artist, Artist, Artist".
98
Wishlist / Feature Requests / Re: ATF support for Last.fm scrobble fields
« Last post by dro 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.
99
Wishlist / Feature Requests / Re: Options for the Lyrics Plug-in
« Last post by dro 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.
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.
100
Wishlist / Feature Requests / Re: ATF support for Last.fm scrobble fields
« Last post by dro 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.