Recent Posts

1

Preview Build Discussion / Re: 1.99.12.18980 M3U Stream sync connection errors

« Last post by dro on Today at 12:50:31 PM »

The problem is that whatever provided you with https urls for the streams shouldn't have done that (if it was from shoutcast then that's one more complaint to leverage against them) & it should've only given you http urls as that's only what the provided streams are using.

It worked in the old WACUP preview because I was having to force https -> http to avoid issues with the re-used plug-in that handles such streaming & that masked the playback problem but it then broke legitimate https playback. In hindsight I should never have done that action.

The current build allows both https & http to work but it's now "broken" things for you because it's honouring what the url type is & as those don't support https (again those provided urls should never have been https ones from whatever service was providing them) then until I make my own plug-in for streaming which might attempt to re-try failed https as http it requires you to 'fix' the urls which'll work on both builds.

-dro

2

Preview Build Discussion / Re: 1.99.12.18980 M3U Stream sync connection errors

« Last post by JamminR on Today at 05:28:50 AM »

Pardon my lack of full understanding - from the context, you're acknowledging this is a bug? (non-SSL not recognized?)
It will be added to an issue list, and some time corrected?
Even if my playlist has incorrect http vs https entries (i've obtained it from directory.shoutcast.com some years ago), it seems 'wrong' to me that the old version still plays it and the new does not without editing.

I went to directory.shoutcast.com and searched for some pulsradio stations - couldn't find this particular 'station, but dragging/dropping the PLS and M3U download links into the new preview seemed to work.

3

Preview Build Discussion / Re: Bug when switching skins in Preview v1.99.11.18916

« Last post by Darkhell on Today at 03:39:46 AM »

I'm using v1.99.12.18980 x86 too, currently for troubleshoot purposes i've renamed the WACUP folder that is created in "C:\Users\***\AppData\Roaming" su when open wacup again a new WACUP folder is created there with all default settings, so no custom skin path, just the default one with the skins that comes with wacup; respect to the file/folder name, the next letters that work (behavior is a little different depending on if is a folder or a file) are, for 2nd letter a,b,c,d,e,f,g,h (i, j, k, etc appear to not trigger the problem) ;for 3rd one i'm not really sure (maybe 3rd, 4th,.. letters are not really relevant), but for example:

If i put a file "bet.txt" then can't load big bento, if rename the file to "bat.txt" then big bento works and now bento doesn't load.

If i put 2 files at the same time, "bat" and "bet", then can't load bento neither big bento

Respect to the .ini file i mean the "winamp.ini" on "C:\Users\***\AppData\Roaming\WACUP", the line "skin=" points to the applied skin, if bento is selected then the ini shows "Skin=Bento", if i trigger the problem with file "bat.txt" then wacup writes the value of skin as trigger file/folder name, in this case bat.txt so in ini it looks as "skin=bat.txt"; as far as i've observed studio.xnf data is irrelevant for this bug

i attach my ini file; just in case, i'm on win11 23H2 build 22631.327 with latest .NET Framework 3.5 y 4.8.1 para Windows 11, version 23H2 para x64 (KB5036620)

4

Preview Build Discussion / Re: 1.99.12.18980 M3U Stream sync connection errors

« Last post by dro on Today at 01:19:05 AM »

The older preview builds are still referenced on the site by following the prior / last preview build link from near the top of the initial text on the site's main preview build page.

I've tried to play all of the links in the example playlist & as-is none of them are working for me either in the current preview or the very old one (which ended up hanging whilst trying to do anything but that might be to do with whatever I'd last done to that test install a few years ago) nor in other players / browsers.

However the problem seems to be because the old preview build would try to force streams to use http:// when https:// was found as that's what was needed to allow the re-used in_mp3 plug-in dll from 5.666 to be more likely to play things.

The newer build has long since resolved that problem & that re-used in_mp3 is now able to try to play the stream urls as-is which is a problem here because what you've provided doesn't respond on the https:// urls from the server side (ideally there should be an attempt to drop back to http but the connection is also taking an age to timeout it seems).

If you edit the stream urls to use http:// then just the sc1 & sc2 server urls don't seem to be responding from my testing.

-dro

5

Preview Build Discussion / Re: Bug when switching skins in Preview v1.99.11.18916

« Last post by dro on Today at 12:58:50 AM »

It's likely how I'm mapping the skin file / folder to a menu item index & based on the video it seems to be counting the empty folder which depending on how the drive returns the order of files (normally alphabetically with ntfs) would then place an a / b named folder before the bento skin items which if it's what I'm thinking would cause it to act as is shown (i.e. it's selecting the 'hidden' empty skin & reverts to the default skin instead of skipping that folder & using what was set for the menu string).

-dro

6

Preview Build Discussion / Re: Bug when switching skins in Preview v1.99.11.18916

« Last post by Aminifu on Yesterday at 11:15:40 PM »

... if there is a folder or a file in the root of the skin folder with names that start with "a" or "b", depending on the following 2 or 3 letters that accompany them, it affects the load of Bento and/or Big Bento, ...

I'm using the x86 beta build v1.99.12.18980.

I'm currently using 16 modern skins and 10 classic ones (excluding the default built in one). I have 5 folders and 1 file in my skins folder with names that start with "A" or "B". The folders contain the files for various modern skins (such as the Bento skins). The file is an archive file for a classic skin (Bento_Classified.wsz). What are the following 2 or 3 letters that trigger your issue? I would like to try to replicate this.

It is not clear to me which .ini file is changed and what the changes are. The winamp.ini is updated with the name of the skin being used when a session is shutdown, so that the next session is started with the same skin. The studio.xnf file is similarly updated if the skin is a modern one.

I have no problems switching among all the skins I'm using, using any and all of the methods currently provided.

7

Preview Build Discussion / Re: Bug when switching skins in Preview v1.99.11.18916

« Last post by Darkhell on Yesterday at 08:51:18 PM »

I can confirm that clicking the "Set skins directory..." button does nothing.

Have added it to the todo list though I've not checked why it's not reacting like it should.

As for darkhell's reply, I'd need confirmation whether it's happening with 18980 or not as I can't get that failure to occur & only can with the older 18916 build which was the one out when this thread was started.

-dro

Hi, after a lot of trial and error  i've found how to trigger the problem respect to the skin that doesn't load , how it triggers is really weird tbh  , for some reason (idk how to describe exactly), if there is a folder or a file in the root of the skin folder with names that start with "a" or "b", depending on the following 2 or 3 letters that accompany them, it affects the load of Bento and/or Big Bento, iv'e recorded a little example, in the video u can see how it changes the .ini file too:

https://www.youtube.com/watch?v=LWssrfy0T28

Respect to the ability to change the skin folder, well, is useful if u have a skin collection and don't want to move to the installation folder to be able to use them

8

Preview Build Discussion / 1.99.12.18980 M3U Stream sync connection errors

« Last post by JamminR on Yesterday at 08:37:24 PM »

For all WACUP can and tries to do, I really use it 90% of the time to stream the music from pulsradio.com while i'm doing other things on PC or in my office. Though i have several playlists from the site, I've attached the one I use most and am experiencing the below issue with.

Today, when starting WACUP_Preview_v1_0_21_7236 that I've used for many years, I was notified of the update to 1.99.12.18980.
I allowed an in-place upgrade. I then went back to my folder with my m3u files, double-clicked as i always do, and... no music ever played.
The new version opened. It showed the (new to me) Thinger. It opened the main deck, which, stayed at 00:00 play time.
I opened the playlist, and saw that several errors had occurred regarding the words 'connection sync error'.
I tries several of the items in the playlist.

I immediately re-installed WACUP_Preview_v1_0_21_723 from an old copy i had and am now streaming the music while typing this post.
(I tried finding a previous to the current preview on your site but i can't seem to find an archive release area)

How can I help fix this issue?

Thanks,
JamminR


EDIT - Just tried installing into separate folders instead of the 'update installation' option - same error occurs.
Exact terminology = "Error Syncing to Stream"
(a few in the list might have 'time outs', but, at least one or two in the list should work and not give time out or error syncing

9

Preview Build Discussion / Re: Bug when switching skins in Preview v1.99.11.18916

« Last post by Aminifu on Yesterday at 07:20:44 PM »

... when all of that got dropped I'd just not gotten around to implementing it since I'd not had to when the winamp core was able to handle the action for me. Is now sorted for the next build.

-dro

With all you do by yourself, it is quite understandable when some things fall thru the cracks. 

I'm still wondering why anyone would want to change the default skins folder. Although, at some point, someone will try to use any option that looks like it may be used.

10

Preview Build Discussion / Re: Bug when switching skins in Preview v1.99.11.18916

« Last post by dro on Yesterday at 10:22:35 AM »

When the beta & the preview are the same build then it's fine.

As for the prefs issue, I had a todo note in the code since it wasn't something I'd yet implemented when dropping legacy mode & should've had the button be disabled. As that prefs page used to heavily manipulate what the winamp core was providing & when all of that got dropped I'd just not gotten around to implementing it since I'd not had to when the winamp core was able to handle the action for me. Is now sorted for the next build.

-dro