Latest WACUP public preview for x86 & x64 is build #24960 (August 31st 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24960 (August 31st 2026) (x86 & x64 changelogs)

Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
The only thing I've been able to replicate is that some icecast urls are being provided as 'http' but they're only going to respond to a 'https' connection & I've provided that as a post-release update which better deals with that situation (though the icecast instance providing the wrong url despite accessing it directly over an https connection is a bug with icecast imho).

I still cannot replicate any of the provided urls failing to play when in_url is present be it on Win10 or Win11 (which is where I happened upon by chance the 'broken' icecast url). Without clarification of what the status of in_url in the install is (which I ask for a reason to try to save wasting more of everyone's time), there's nothing else I can do & won't be for at least a week (maybe more) due to irl commitments.
42
I reinstalled 1.99.54.24960, but the problem persisted. I installed WACUP_Preview_v1_99_53_24784_x86, and it worked.
43
wd9895: The station list is updated daily against what I'm able to obtain from a number of sources so unless they're all messing up then that shouldn't be the problem. Examples would be helpful of ones that aren't behaving so I can inspect them.

vikingt: With what's shown it really shouldn't be trying to use the directshow decoder for url playback & would explain why nothing is happening. You need to check that wacup's in_url plug-in is present & enabled & loaded which can be done by going to preferences -> plug-ins -> input -> look in the list for in_url / streaming url processor. If it's not there then you'll need to re-run the installer & hopefully that should correct what is most likely the OS / 'smart app control' (since you've mentioned Win11) messing around with dll loading when there's no reason for it to do so.
44
I noticed the same: Many stations do not answer.
I checked the previous version and updated the cache of internet stations afterwards.
Result: Many are not playing.

I concluded that the list is a bit outdated as my personal favorite radio stations stream properly wo. any issues.
45
I've tried different output plugins on both laptops. no problem with local files, no problem with other players.
46
General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue
« Last post by dro on September 05, 2026, 10:43:12 AM »
I've got a simplish fix for you so the skin can work with 24960 by extracting the skin into a 'Quadelic' folder (a .wal file is just a .zip archive) within the wacup skins folder, then open the 'xml\configuration.xml' file within the 'Quadelic' folder & change the <elements/> to be </elements> & save it. Then select the folder extracted version of the skin (it should show with a folder icon next to its name in the skins menu) & that should then load correctly.



The problem is the / in the end elements part is invalid & what I now use for xml parsing doesn't like it but it's also possible that what had been used in earlier builds has been tightening up xml validation so might be why you had to go back a few builds to get it to work again (I've not tried the older builds to see what they're doing but it's a reasonable assumption with the changes that libexpat have kept making & which led me to want to drop it over all of it's security related churn). I still need to code in something that can handle this problem since it'll be expected for such skins to still be able to be loaded though imho the skin should never have been able to be loaded due to the error in the xml but that's another thing against libexpat being a lax parser.
47
General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue
« Last post by dro on September 05, 2026, 10:09:53 AM »
If going back to 24496 works then it's not just due to the xml parser change. I know there were some reports of some of the transparent skins not working correctly (not that modern skins ever work 100% under wacup due to how it's gotten the gen_ff plug-in to work outside of winamp) but I wasn't aware of there also being xml parsing issues. Have got the skin & will hopefully get it resolved for the next preview build as the error is coming from one of the skin's xml files not having the expected xml headers so I need to adjust my handling to deal with that.
48
All of them appear to play ok for me from a quick test. If you go to Preferences -> About|Updates -> About tab -> what is shown as the active input & output plug-in at the bottom of that prefs page when you're trying to play these streams? Also is the version info block on that prefs page populating correctly?
49
General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue
« Last post by petormeat on September 05, 2026, 05:48:17 AM »
Hello, thank you for the reply and sorry for the delay.
I attached the skin file as requested; I in fact did not know what wacup ver. I was using before but I remember updating 1 time before this last update brought me the error (with the crash fix available patch included); I'll be downgrading my wacup as suggested  :D

Edit: downgraded to ver 1.90.50.24496, no modern skin issues there
50
Hi,
After updating to WACUP v1.99.54.24960, I can no longer play online radio streams /sample attached/.
When I try to open a stream (MP3/AAC), nothing plays
No audio, no buffering, just no playback
The same streams work fine in other players (e.g. Media Player Classic)
The issue happens on two different laptops, so it's not machine-specific
The same streams were working correctly in previous WACUP builds
Switching SSL backend (no change)
Changing output plugins (asiooutput / notsodirect / notsoyasapi)
Restarting WACUP
Testing different streams
Both systems with Windows 11, WACUP x86
Pages: 1 ... 3 4 [5] 6 7 ... 10