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 ... 145
1
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?

2
Wishlist / Feature Requests / Re: Lyrics Plugin Text Alignment
« on: Yesterday at 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.

3
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.

4
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.

5
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.

6
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.

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

8
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).

9
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).

10
General Discussion / Re: Radio issue...
« on: October 02, 2026, 02:05:19 PM »
Other than trying out the newer 1.99.55.25130 build (24960 would've been the current build when this thread was started) without a reply there's nothing else I can do.

11
It simply hang at the [Connecting] phase in the player.
1.99.55.25130 fixed & adjusted a number of things when it comes to stream playback which should've resolved the cases where I could replicate things showing in the manner quoted (e.g. it often wasn't resolving the likes of listen.m3u into playable urls due to a core bug).

12
General Discussion / Re: Playlist Editor Display Question
« on: October 02, 2026, 02:00:54 PM »
The point of the playlist editor / playback queue is to see what's in the list to know / control what'll potentially be played next. There is no mode to clip it down to just what's playing (just to keep it as the central item seen within the window area via the Playlist prefs page) & I don't intend on implementing such a mode as that imho would just be too confusing vs how it's all meant to work. As the main window's song ticker shows what's playing then I don't see why just hiding the playlist editor window isn't enough for whatever you're trying to do.

13
General Discussion / Re: WAV files won't play with Not So YASAPI
« on: October 02, 2026, 01:56:12 PM »
1.99.55.25130 is the current build so it'd be better to re-test against what I'm currently offering though I'm not seeing 24960 acting in the manner described unless it's something specific to the wav file that are trying to be played. The only way I could get that build to act in such a manner which affected all formats was if the pull mode strategy was enabled since that never seems to have worked & 25130 removes it).

If 25130 still doesn't behave then you'll need to provide a small example file which you're trying to play that exhibits the issue so I can try it out myself.

What's also odd is that there's none of the output plug-in descriptions showing on the output plug-in list from the provided screenshot which is making me wonder what else might be missing from the install.

14
Preview Build Discussion / Re: CD related feedback
« on: September 25, 2026, 05:42:34 PM »
The CD view not updating as expected on eject / loading a drive I think I've now resolved. It was trying to but the timing of things with the media library as a whole had changed which meant it sometimes ran things sooner than expected causing it to get the intermediate state of the drive instead of what's seen when toggling the view once it's ready.

I can't replicate eject not working from the button nor the menu so I don't know though it doesn't help that there's a means to try to close an open tray but the way things seem to be reported back are inconsistent or not there so it might be that or a permission problem (i.e. something else having some access on the drive, I dunno).

The artwork should now load now consistently as I've had to change in_url to not try to handle the CD items during the attempt to find what can provide the artwork for the CD items.

I can't replicate double-clicking the navigation tree item not working (maybe it relates to the eject problem) but every time I've tried to play a CD that's been loaded it'll work.

The double-clicking / enter is different to 5.666 as my plug-in hasn't been coded to do it now I've re-checked the code. I'm debating if I want to implement it or not since it'd be adding in another option as imho it needs to be fine-tuned to not use the local library or playlit setting but I suppose it makes some sense to have it for audio cds.

15
Preview Build Discussion / Re: CD related feedback
« on: September 25, 2026, 11:51:47 AM »
I started to look into this last night but my bluray drive lasted a minutes before it crapped the bed (which I initially thought was something I was doing wrong but not, the lights are on, it makes a noise but can't read any type of disc) & somehow took out my dev drive for a while (*) which was not a fun last night & then this morning trying to get things going again & I'll need to look into getting a replacement bluray drive.

(*) The OS / bios stopped seeing it as a drive at all at one point but thankfully it came back & I've not lost any data on it afaict.

Anyhoo, now I've got a machine that runs along with a working cd/dvd drive I think I'm seeing most of the problems mentioned. So far I've only managed to compare against build 23410 (Dec 2025) to see how far back I need to be looking at for changes made (e.g. if it's the libdiscid update or something else as part of other crash fixes that's inadvertently messing with how the cd plug-in now wants to work). That build seems to behave so far which gives me a 10month window of builds to now work my through hopefully without any other hardware problems.

[edit]
23528 (Jan 12) seems to be ok but 23960 (Mar 1) doesn't so that looks like it might help me narrow down what I changed.

Pages: [1] 2 3 ... 145