Winamp 5.666 Released (Build 3516)

[thinktink]

Probably wouldn't be extremely hard to hook those links with a plugin and redirect them elsewhere.

[DrO]

most things end up being routed through the same api (but not everything) and is something i've already thought about, but is not something that can be altered for final builds.

[r.e.e.d]

i am very sad about winamp, but i need to ask: are you guys still fixing bugs till 20/12?
i believe that i found one.
in a clean install, if a file is playing, enqueue another file from explorer right-click is enqueing and playing instead just enqueue. this is happening with any format, flac, ape, mp3.

on 5.65 this doesn't happens

[DrO]

there's a number of posts about the enqueue issue with the 5.66 release (even in the earlier posts in this thread). we are hoping to provide a quick update patch to resolve that issue shortly.

[r.e.e.d]

sorry, i missed that.
thank you!

[DJ Egg]

Winamp 5.666 now available

First 2 posts have been updated accordingly.

Enjoy! :-)

[thinktink]

Winamp 5.666 now available

First 2 posts have been updated accordingly.

Enjoy! :-)

OmNomNomNomNomNomNomNomNom...

[MarkRH]

Hmmm.. think I would have just skipped right on past that version number..

[thinktink]

Hmmm.. think I would have just skipped right on past that version number..

As a plugin developer I am aware of several API integer constants that use 0xFFFFFD66 and 0x29A as a special value. IPC_SETVOLUME and IPC_SETPANNING comes to mind and I am sure there are others. Like it or not (I don't by the way), 666 is in Winamp. Has been for a while.

[Koopa]

Isn't that a cosmetic thing in some parts only? Real version number is 5.6.6.3510, so compared to the last version, only the build number changed.

[kzuse]

I like the number and I love the new release! Big THANK YOU for this release!!

[DJ_MELERIX]

the final version of Winamp 5.7 will not be released then ?

[DrO]

DJ_MELERIX: the v5.7 release was v5.6x + Cloud services. as thats been stopped (like the rest of Winamp is being) then there is no reason to ship a v5.7 anymore as it was never completed. it was primarily just a numbering difference between the Cloud and non-Cloud releases as we'd try to make clear but that never seem to be understood.

Hmmm.. think I would have just skipped right on past that version number..

Having been an avid user myself for a long time and the number we were on, it only seemed fitting to show a nod back to the same thing which had been done in earlier versions. I know there are going to be people who won't like it and will refuse to use this build but Winamp itself is identified as 5.66 internally to plug-ins and is just a cosmetic thing.

if its that much of an issue for people, I can make a patch to remove the extra 6 from the ui parts (though would require a small donation to cover the time to do it) but will not be changing the final compiles now.

[foxyshadis]

New major release of Winamp, wow, thanks guys. That's a fantastic late birthday present!

One big bug:
After lots of debugging, and testing strings, I traced it down to a crash in tagz.w5s. The crash is in $sub, which isn't protecting against null strings. %rating% doesn't seem to be working at all, despite ML being active, and due to that, $sub(5,%rating%) will crash the player. (Sometimes it'll just disappear, too.)

Horray, now that I know that I can finally use Winamp again!

Aside from that:
gen_crasher wasn't picking it up because other plugins are overwriting SetUnhandledExceptionFilter for some asinine reason, these ones I found were:

in_NotSoFatso
in_psf
ml_orb
ml_plfix

Even with all of them gone, though, the Winamp crash handler never fires, just the generic Windows drwatson. Something weird happening, obviously.

Edit: %rating% is sorta but sorta not working. Add from ml, rating shows. Play, and it's gone. Except once, it showed. I have no idea what's different about that one file, it looks exactly the same as its neighbors as far as I can tell; I made them all from the same CD.

[DrO]

if only you'd posted about this 12hrs earlier

the crash reporter may not be loading due to other things on the system affecting it, though very strange about the others (and you'd want to get rid of ml_orb.dll anyway).