31
General Discussion / Re: Procrustes question
« on: January 29, 2024, 01:43:59 PM »
Skins + old plug-ins are a pain in the whatnot at times. Glad to hear it got you to be able to see the plug-in ui.
-dro
-dro
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)
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.
>> The thread "Known Reported Public Preview Build Issues " was last updated in January 2019 and nothing can be found at https://getwacup.com/known_issues.html. So it could be that some/all of this is already known.That thread / page needs to be started over again which is intended once the next set of preview builds arrive.
Problem #1 - Jump to File BoxWill look into it as that was already meant to have been fixed in relation to some of the dark mode handling changes that broke it in an earlier build.
1) I deactivated the "Skin the window in the current WACUP skin stlye" option in the plugin. But then the "Jump to File Box" can no longer be used properly because the text "Search for Text" is displayed exactly above the input field. You can type without problems but you can't see what you have written. You can use mouse-over to make the overlay disappear, but only until you press the next letter, then everything is covered again.
2) The "Delay from last typing action before the search is processed" option in the plugin is already applied when opening the "Jump to File Box" and not only when typing. I don't know if this is intentional but it seems to be quite useless when opening the box for the first time.I'd need to look into it as there's things in the plug-in from over 20yrs now that I honestly can't remember why they were implemented or what the intent was meant to be. It being linked to the loading of the dialog does seem wrong.
3) When you open the "Jump to File Box", the cursor is normally on the currently playing song. However, both the "Limit the number of search results to be displayed up to..." option and the "Only show search results when a real search has been entered" option prevent this. It would be nice if the cursor would still be on the current song with both options so that you can continue to scroll quickly through the list using the arrow keys.I can't currently replicate the search field not being focused on initial loading under classic or modern skins & whether it's being skinned or not.
This might be difficult with the limit option, if you set the limit to 1001, for example, then the cursor would have to be on the song and 500 songs would be listed up and down. But I see no problem with the "Only show Search..." option. If you deactivate both, the box behaves exactly as in Winamp. But setting a limit speeds up a large playlist with 50000+ songs enormously! It would be a shame if you had to sacrifice these two options in order to continue to benefit from "scroll from current song".
Problem #2 - Global Hotkeys PluginI've never seen that happen before & right now I've not been able to replicate it. Maybe there's some other software running / keyboard driver type stuff that's interfering as the input control for the hotkeys is not fancy so shouldn't be breaking like in the manner shown let alone it requiring multiple process restarts.
I was able to create/change all the hotkeys I need. But it took me several attempts. Because from time to time the following error occurred in connection with CTRL+ALT+Something:
Restarting WACUP solved the problem. For some hotkeys I also needed up to three restarts. No big deal and eventually I was able to create them all but I thought I'd report it.
Problem #3 - Playlist m3u/m3u8 LoadingI've been trying to replicate all 3 of these but so far haven't. I'm either not following things or there's something else going on that I'm missing which maybe is even down to stripping the install back a lot as you've mentioned in another part or maybe if you've got wacup running in legacy mode. With build 17040 that's only needed for having the equaliser work whereas I'm currently on a newer dev build than recent beta 18106 & legacy mode is no more & things afaict work correctly on all counts from what I've been trying. I would also suggest maybe trying the classic base skin to rule out at least the first two being related to the skin being used as there are things that the modern skin engine plug-in does which in some scenarious might be able to cache / display the wrong information until a proper playback event then occurs.
1) If you load a playlist via Play > File (Key L) or via the EJECT button (Open File(s)), the song that is currently playing is written to position 1 in the playlist instead of the song stored in the *.m3u/m3u8 file. Only playing this song will then show the correct name.
2) If the playlist is completely empty and you press stop and then load a *.m3u/m3u8 via Play > File or the EJECT button or the Play button, position 1 also does not show the name of the song but the full path to the file. Again, the song name is only updated when you play it.
>> I have a playlist in which Song 1 is displayed correctly but I could not find out what makes the difference. Possibly the path of the files which sometimes contains special characters like an "&" sign. I saved all playlists again with WACUP but the generated m3u/m3u8 show the same behavior.
In addition, all playlists are loaded correctly (and song 1 is displayed correctly) if you load them using CTRL+O or via the playlist itself. Manage Playlist > Open Playlist.
3) If WACUP is started via *.m3u/m3u8 then Song 1 in the Playlist is always played even if "Playlist Shuffling" is activated. Winamp already selects a random song at startup. Only if WACUP is already running and you then load a playlist will a random song start. In WACUP Song 1 is always at #1 in the Shuffle Inspector!
4) If the Playlist is completely empty and you press Stop, Winamp 5.666 Build 3516 is displayed in "Windoshade Mode" instead of WACUP v1.9.20.17040 (x86) as in "Normal Mode".That depends on the skin & if it's a modern style of skin then there's limits on my live patching skills to override some of the gen_ff plug-in strings whilst needing to provide that compatible string for other things the gen_ff plug-in needs. So that's why there's going to cases of the winamp version string appearing over the wacup version.
Problem #4 - PerformanceThis is one that I'm not going to modify over what is provided. The whole script timer aspect had to be taken over by WACUP code to be able to use gen_ff under it without needing the Winamp core program & the way the old slider worked just wasn't worth the effort on my part to try to figure out how to hook into the studio.xnf settings handling without making other aspects suck & didn't see it being worth the effort. That's why my handling ended up as just a basic high/low toggle & I always knew that it was never going to be the best fit for some but it's the choice I've made.
1) I have disabled the media library, video playback and many plugins and yet WACUP uses slightly more CPU than Winamp (even though the load is ridiculously low). While trying to reduce the CPU load to Winamp level I realized what the problem is. In Winamp I can set the "Timers Resolution" in the Modern Skins menu. In WACUP I can only choose between 60fps and 30fps, i.e. between an update of 16.6ms or 33.3ms. But in Winamp I have set 66.6ms which corresponds to 15fps. If I set Winamp to 16.6ms or 33.3ms then the load is similar to WACUP. So I suggest adding a slider like in Winamp or allowing a user-defined value in addition to the 60fps and 30fps. Possibly also only via INI Edit, would be fine with me.
2) Why is the Public Preview release only available in x86 and not in x64? Is the performance better or even worse with x64?The x64 build is not yet at feature parity to the x86 build & was mostly for my internal needs to be able to compare on how close an all native wacup implementation vs the various stages of the normal x86 wacup + re-using some of the exe/dll from 5.666 was.
Okay, here's a small request for the wish list:I've added it to the todo list as something to consider. As a generic way to have any of the currently available skinned windows being registered would be the nicer way vs having to do too much on per plug-in customisation to get things implemented as would be the case now.
Feature Request - Extension of the Global Hotkeys plugin
It would be fantastic if you could define more hotkeys in addition to the ones you can already assign. I'm thinking, for example, of " Show Album Art" or the Waveform Seeker. At the moment you have to click on WACUP before ALT+A or ALT+R will work.
That reminds me, is there a way to open "Album Art" and the "Waveform Seeker" via a button in the skin? By action, rightclickaction, dblclickaction, cfgattrib or something else? I would like to build the buttons for this into my skin.Possibly if it was coded into the skin (looks like one of the bento based ones from the screenshot) but my maki knowledge is slim so I don't have an easy suggestion on how best to try to achieve this.
When will the final version be released? Is there a roadmap somewhere or other ways to view the development? A Github page or something similar?I've no eta on when a final will be done & it mostly comes down to when everything that's needed to be at feature parity or better is done along with ideally no or at least the very minimal need to re-use any of the dlls from 5.666 along with shell integration & localisation support. Then there's whatever distractions & oh look a squirrel moment I have working on things. So no, there's no formal roadmap & based on my prior attempts at something like it, they never worked out as planned so I decided not to bother doing them & waste mine & others time doing them. The build changelogs, odd stuff when I remember to post or what I'm talking about on the discord server are the main ways to follow what's going on.