Latest WACUP public preview for x86 & x64 is build #25130 (September 30th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #25130 (September 30th 2026) (x86 & x64 changelogs)

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

Pages: [1] 2 3 ... 146
1
Attach the image please as I cannot see anything from imgur (am geoblocked since September 2025) also you need to confirm what version & build type of wacup you're using along with the OS being used.

2
Quote
Changed more of the internal ATF handling to avoid working out the length of strings when it's already been determined for a small performance improvement especially when doing 1000's of ATF calls
That's the reason for it not behaving correctly with build 25130 which was not intentional & will require a new build to resolve it.

I might also see about adding an extra parameter or a case insensitive version of $replace as it caught me out initially that the string I was testing with didn't match exactly.

[edit]
Have added an optional fourth parameter to what'll be part of the next build which is set to 1 (e.g. $replace(%title%,String,,1)) will treat string & String as the same. If not set or not what's expected then it'll keep doing it all as case-sensitive comparisons.

3
You're welcome.

4
I think I've got it fixed for the next build. There's something odd about the drone skin vs lyricsplugin which is affecting the normal timing of things happening (based on what the other skins are doing whilst debugging this) that causes the bitmap used as part of the drawing of the main playlist window to not be available during the initial drawing.

That causes it to end up in a weird state where the drawing mostly works but the colours basically doesn't as it falls back to working with a default monochrome bitmap that the OS creates for the drawing surface. So that's why no selection is showing up or even the expected colours from what I was seeing & it comes down to a 1 line fix to filter out the painting when in that invalid state which at least for what I'm seeing under testing is now getting it to load correctly with the plug-in.

5
The portable install mode won't load 3rd party plug-ins by default as a lot of them aren't going to be truly portable (lyricsplugin is one of those by using the registry from what I remember). If you go to Preferences -> Advanced -> Portable Mode -> there's an option to allow 3rd party plug-ins to be loaded in portable mode for those happy with things no longer being guaranteed to be portable.

lyricsplugin is also throwing an expired site certificate everytime it loads which is annoying (not the first time the plug-in &/or it's site have gone weird in the time I've been doing wacup & was why I needed to make my own even if it's not feature comparable to what want as it avoids the whole embedded IE browser webcontrol mess that lyricsplugin relies upon to still work for now).

I can replicate it breaking things when the drone skin is the one set to be loaded on start-up & lyricsplugin is enabled. If I start with a different skin or change from drone to any other skin I've got to test with & then back to it in the same instance it then behaves. Though why if it's the one that's been loaded & trying to reload it without changing to another skin doesn't update things is also weird which I'll try to look into hopefully later today.

6
I've attached what the prefs page should look like with a red box around the button that'll become enabled if it's seeing that there are applicable post-release updates for the installed build.

7
It's the same as I've already got which I'd expected so wtf is going on that is causing it to break for you when I cannot replicate it on anything I've tried nor can I see anything with the code changes that I'd made between the builds that would relate to skinning as it's a standard part of the code used for all of the skin types trying to be used. Does making a test portable install & using the skin in it also break?

8
Wishlist / Feature Requests / Re: Lyrics Plugin Text Alignment
« on: October 06, 2026, 01:55:46 PM »
Assuming build 25130 is being used if you go to preferences -> about | updates -> about tab -> follow the instructions to get the post-release updates & then there should be a new text alignment block on the lyrics window right-click menu to change how it's rendered.

9
Preview Build Discussion / Re: [CHANGES MADE] CD related feedback
« on: October 05, 2026, 08:29:14 PM »
I've uploaded a post-release update for the cd plug-in (it'll appear as an OS toast notification or for speed you can go to prefs -> about|updates -> about tab & follow the instructions from the button on there) which should fix track#1 not playing after the first eject in that running instance due to the plug-in not releasing something internally when it's doing a double-check of the track type to avoid trying to play data tracks if those have been added (as is the case with one of my test cd's which I'd done most of the testing with so missed this).

The phantom track issue was also noted by someone on bluesky against an older build & I've seen it happen once but couldn't get the debugger hooked up quickly enough to check what was going on before the disc at the time had finished loading. The albumart / lyrics windows may not see the changed artwork due to how things are cached which I'll need to look into (likely with a forced change notification being sent out) along with the whole ui hang that can occur if a disc has just been ejected whilst set to try to repeat playback & it's then sat waiting for the device to appear. I also need to do testing with the other drive that finally arrived but I've not tested it out yet.

10
General Discussion / Re: WAV files won't play with Not So YASAPI
« on: October 02, 2026, 10:21:25 PM »
I dunno then as that's the only way I can get close to the issue you're having with notsoyasapi though at this point it'd be simpler to use notsodirect (it's the default output plug-in since its the most compatible for what I expect wacup to run on) & I'll have to mess around under a Win11 VM to see if I can replicate it there.

11
General Discussion / Re: WAV files won't play with Not So YASAPI
« on: October 02, 2026, 03:37:37 PM »
The sample file appears to play ok though I'm only testing on Win10 as of this reply though from the other image I had a thought & on the wasapi prefs page, go to the devices tab & if it's not then check the 'Auto convert to system samplerate' option on there & close the prefs page to allow the change to be applied (it's default is checked which I've re-checked from looking at a clean test install). That option being un-checked is the only way I can quickly replicate the provided sample file not playing.

12
1.99.55.25130 went up a few days ago which has the changes for all of the problems that I was able to replicate when it comes to streaming (as long as the needed plug-ins are able to be loaded i.e. as long as smart app control isn't blocking the likes of in_url).

There's also so many old radionomy & listen.shoutcast stream urls being provided despite none of them working for many years as of this reply...
The internet radio cache which any of the builds is provided has had some changes made to how it's generated over the last few days which filters out the ~36K of 'dead' streams that the shoutcast directory is providing which leaves around 7-8K of seemingly valid streams depending on when things are queried during the day. Alas I can remember when that had a legit 50K+ or internet streams & am surprised that the api is still even running considering that's a massively small number of streams vs icecast + radiobrowser. That's why for those paying attention the internet radio view has dropped from over 100K results to ~68K results.

Whether that increased filtering of the api results relates to the other mention of things not working I don't know but it's the only other thing I've been able to find in addition to the core / url playlist handling problems that affected the prior build.

13
Preview Build Discussion / Re: High CPU usage
« on: October 02, 2026, 02:15:23 PM »
1.99.55.25130 was uploaded a few days ago with the changes to dsp_wc that I was able to make so hopefully that'll be better behaved for you.

14
Preview Build Discussion / Re: [CHANGES MADE] CD related feedback
« on: October 02, 2026, 02:13:49 PM »
1.99.55.25130 was upload a few days ago which has the changes I was able to make (am still waiting on the replacement drive I ordered so I don't know if I've ended up making changes that are only behaving with the much older cd/dvd drive I was able to scavenge to test with).

15
Not having intentionally touched anything related to what I do to allow gen_ff to work under wacup since the prior build 24960 (I don't know if that's what you were using or not & the changes for that only related to the internal xml parser I was using so I could drop the expat library) I don't see a reason for it now not working.

I've also tried with both copies of the drone skin that I've got along with a range of classic & modern skins & none are showing an issue with the selection colour not being made use of. As such I could do with a copy of the skin that you're using along with what colour theme you're using from it (as the screenshot isn't the default skin colours afaict) & what version of Windows you're using (if only to rule out Win11 deciding to mess with things when there's no reason for it to be doing so).

Pages: [1] 2 3 ... 146