Has anyone else upgraded to 5.57?
EDIT: Should mention I have also tried the most recent vgmstream I could find, 721.
edited 3:50 AM EST December 20, 2009
So with all these troubles and issues, have you considered going back to WA5.56 (or a good known working install) sounds to me WA.5.57 it's not worth the trouble yet, and this is no linux kernel, this is a win32 app haha.
I don't plan to touch anything in my my winamp setup until I read something major (eg In_mod.dll fixed to use inbass or very critical inflac/inmp3/inmp4 fixes be it security or not and even then I'd first try to get the dll alone rather than the entire executable)
Been reading too much issues with 5.57 specially in 'our field'
edited 8:34 AM EST December 21, 2009
edited 7:18 PM EST December 21, 2009
Well, 5.57 does have a really quite nicely improved video playback, but it's something I can live without for now I suppose.
Also it crashes whenever exiting Winamp after viewing the configuration options for Modern Skins.
Plus MGME (though renamed) alleviated temporary VGM support during the 5.57 installation in my case.
Weird...
edited 4:53 PM EST December 24, 2009
Failing that, can it play MED mods, cross fade similarly to the Sqrsoft Advanced Crossfader (out_sqr) and look pretty (need all features of Big Bento as a minimum now)?
Not being a smart arse; if it can actually replace Winamp to full extent then I will happily abandon it. It's become the Windows of media players...
MED sure (and 160+ other Amiga formats), with the Delix plugin.
Truth to be told, I've made the jump at around 2.30, so can't compare to newer Winamp versions, but never felt the need to go back.
New version is out, there site seems a bit slow at updating but the file is on there server.
Seriously, it seems that the Winamp installer screws up the existing dlls somehow. So copy the fresh ones over the existing ones.
edited 10:00 PM EST January 14, 2010
will have a look into it over the next few days as i'm wondering if the optimiser (is meant to re-base the official dlls for a loading time improvement) is messing with something but need to check it out properly.
and unfortunately 5.57x was a messed up release but 5.572 seems to have been better in general (unfortunately not for emu related areas it seems).
-daz
edited 10:53 AM EST January 25, 2010
edited 10:53 AM EST January 25, 2010
in_psf still works so maybe you can compare against it somehow, if he gives access to the source?
I do wish they'd leave shit alone if it's going to break stuff.
Hotcakes: it's never done intentionally to cause breakages, etc but unfortunately it can and does happen in particular with plug-ins that are still designed in the 2.x style instead of being better designed really for a 5.5+ style (so all unicode & newer api compatible).
in most cases it's generally issues in the external plug-ins (not helped that documentation is dire for large parts of plug-in integration) which are shown up by the changes in the client itself (like the change in compile has caused for some plug-ins).
and it's not helped that i've not been active around here for sometime to keep up-to-date with issues (like the v5.51 spectrum vis incompatibility crash which was caught from this forum/irc) as often an issue posted over here will be something many more are experiencing but aren't properly reporting.
either way i'll post back once i've had a chance to check things out and see what the issue is and see if a resolution can be done for the future.
-daz
franpa: i'd have hoped so ;)
-daz
I posted about plugins not working right before, maybe you can prioritize it or something? It's been some time since that post of mine.
----------
Update (5.57 & 5.571 fresh installs):
Installing/updating with "Modern Skin" support selected during the install process, renders VGMStream and MGME input plugins not initializing. Reinstalling without "Modern Skin" support results in the 2 mentioned plugins working fine and dandy.
This is with the plugins and the dll files they depend on, already installed before installing or updating Winamp.
http://hcs64.com/files/vgmstream/
http://mudlord.xtemu.com/files/in_mgme.dll
edited 11:42 PM EST January 26, 2010
i've just installed vgmstream and was getting a crash, loaded up a debug winamp.exe and the crash disappeared so not sure what that was (will have to try again).
have re-run the installer on an install with in_vgmstream present and the supporting dlls and the dll rebaser is handling all of the dll as i thought. from working through things, the issue is coming from the rebasing of libmpg123-0.dll. as a workaround, changing libmpg123-0.dll to read-only makes the rebaser ignore the dll though will look into it closer to see why it is happening but at least there's a workaround for the moment.
is there a current link for in_mgme.dll as the one provided isn't working for me.
-daz
edited 7:32 AM EST January 27, 2010
It's not the latest version though, not sure where to get that from and I forget what version I tested with.
Some other times, I get 2 UAC prompts, one with a yellow banner and another with a blue banner, both 1 after the other.
and even still, there are times where there are no UAC prompts.
It's pretty strange. My account is a Admin one and UAC is at the default level.
edited 12:20 AM EST January 28, 2010
well i've had a look at things more closely and the issue appears to come from the import table in the dll's internal structure being altered by the rebaser (is using the BindImageEx(..) api and is as such causing the loading issue.
however by using BIND_NO_BOUND_IMPORTS in the api call it appears to rebase the dll it ok without destroying the import table in libmpg123-0.dll & in_mgme.dll.
why it only affects these dlls is beyond me at the moment though i wonder if it's related to how the dlls have been compiled. either way there's the read-only workaround for the moment though will do what we can to patch the installer's rebaser tool which will hopefully be done in time for the next client release.
as for the UAC stuff (though i'm only just getting upto speed on when it's activated in Winamp), it should only be appearing when a registry access is required (often if the restore file associations option is enabled on loading) or when doing things via the File Types preference page or uninstalling a plugin. however the UAC handling as improved in the 5.572 client so it now works consistantly going on what i've seen personally (Vista+Win7 under admin and standard accounts).
-daz
Otherwise MGME can't remember configuration after closing Winamp unless Winamp is run with admin permissions...
Franpa: basically in_mgme needs to be updated as above. there isn't a built-in api for detecting such an event as saving settings has always been down to the plugin to implement in a correct and sensible manner (maybe doing a foobar2000 option would make better sense but the relucatance of so many plugin's to be built to work properly under 5.x as it's horrible/evil/bloated/etc etc as i keep seeing from comments is no wonder there are the issues being experienced).
back to the original issue and unless i can figure out what is done differently with the compiles of in_mgme and libmpg123-0.dll, they'll just be black-listed from being rebased (though i'd prefer a method which automatically copes with such dlls as i've a feeling there are other cases out there).
-daz
http://www.theess.com/med-soundstudio.html
I contacted the author who said they're not interested in Winamp or MED any more, so I'm boned. Basically it suffers from the re-basing issue (not a huge deal) and now I can't get it to play anything without crashing (worked pre-5.57). Then again, it was never a very good piece of code, even back in the 2.x days.
Might as well go the whole bloody hog to support all of Winamp 5's extra functions, heh.
edited 10:38 PM EST January 29, 2010
Also, I think the reason there are separate ANSI and Unicode builds of some plug-ins is because the damn thing defaults to the ANSI functions even if there are Unicode versions exported. They may have fixed that recently, but it's probably worth testing anyway.
mudlord: people do it for the foobar plug-ins so why not actually do it for the Winamp plug-ins as well and it's not like it's that difficult (only took a few hours to fix up 64th Note for all of the metadata api and getting it to follow the correct path for saving settings into).
plus using the correct api for saving settings which has been available since the 2.9x series isn't a player specific hack imho (is down to other loaders to ensure that it's offered correctly if they want to work properly).
kode54: the decoder api is used internally for the transcoding (which was sort of taken from the external version provided early on with the ml_ipod project).
as for the ansi/unicode thing, the unicode exports are meant to be the prefered option so if you can give an example where this isn't the case then i'll have a look and get it patched as applicable.
-daz
edited 5:10 AM EST February 3, 2010
all i'm trying to do is offer suggestions to help improve the usability of the plug-in in the "dickhead" of a client but if that's the approach (which has been mirrored by other input plug-in authors) then i'll stop trying to help.
and with that response i cba to waste my own time fixing the rebaser when i don't have to - well done.
-daz
edit: your probably sarcastic but yeah :P
edited 10:19 AM EST February 3, 2010
I backed up all my plugins that didn't come with winamp, moved the folder to desktop (in case I'd missed a DLL somewhere, and I actually had :P), and also deleted Winamp Detect from /program files/.
After that, I ran the 5.572 installer, copied back the plugins, used vgmstream_external_dlls.zip to replace libmpg and libvorbis, and restarted winamp 5.572.
Worked like a charm!
I guess Winamp's rebaser doesn't like MinGW compiles.....
Running WA 5.572, Modern Skins support installed, but not actually using a "modern" skin.
I'm going to scream, then migrate to something else if my winamp fucks up seeing how I have a ton of plugins just to play all the music archived on this site.
Also I refuse to update Winamp anymore, I'm too paranoid that Nullsoft's going to fuck up shit even worse.
Nice logic there.
Also, maybe some of your 3rd party plugins don't work together very well?
edited 12:37 AM EST March 5, 2010
I think you misunderstand me...
Out of nowhere, be it either a Winamp update or even just sitting inactive for days, suddenly some of my friend's winamp refuses to work anymore giving a "Guru meditation error" flashing on the top of their screen. Why? I don't fucking know... but for whatever reason it's always some input plugin, of which I've been suggesting to my friends to play back .SPC, .MINIUSF, whatever, and it's been working fine for me for years... Then out of nowhere it stops working for them.. so I put the blame on Nullsoft for changing something on Winamp 5 that probably shouldn't have been touched, because it would break compatibility with all plugins that I've been keeping up to date as much as I can.
I don't even keep Winamp up to date anymore until a plugin I'm keeping up to date with deems it necessary to update.. since I don't want anything to go screwy.
Seriously.
Speaking of Winamp, does anyone know if I can get Winamp3's skin working in Winamp 5 as a "Classic skin"? Since I miss Winamp3's look so damn much now....
"does anyone know if I can get Winamp3's skin working in Winamp 5 as a "Classic skin"?"
No, but doesn't the "Winamp Modern" skin look essentially the same? It's been a long time since I ran WA3 obviously but I thought that's where that skin came from.
If I still had my copy of Winamp3 (which was YEARS ago when I still had my Dell before my father comendeered it due to his Medion crashing for reasons unknown to me...) I'd show a screenshot.
edited 8:53 PM EST March 5, 2010
Not sure how I'm going to beable to get this skin working in Winamp5, in all the ways it worked in Winamp3, but it's worth a shot.
The skin is indeed, Winamp3, but Winamp3 had a darker toned version of this that was selectable as a option I don't even remember now, and this classic skin doesn't appear to have the option to make it that certain tone that I like.
But still, thanks for the good find!
I still miss the "Thinger" though, *sigh*
I obviously -do- know that modern skins have a Guru-style error message, Rukario apparently didn't. Sorry you didn't get the joke.
I've known about the "Guru mediation error" ever since reading about it on wikipedia (OH NO!!!!!!!!!!!!!!!!!!!), and I have no idea why Modern Skin Support would be so pissy and unstable.. I don't even make us of it either, I've been perfectly fine with Winamp3's default skin and glad to have it in Winamp5 at long last, thanks to Mouser X's search.
@Rukario: The Modern Skins use some blend of Nullsofts Java-like language they invented 'for' Winamp 3 - everything Winamp 3 did used the language but it proved to be slow and unstable, hence the whole build was dropped and they went back to Winamp 2 + Modern Skins support, the only thing they kept from Winamp 3 (well, as far as the end user is concerned anyway).
Since then, code stability does not appear to be something Nullsoft have had in mind... I swear it's just gone downhill since.
And by that I mean, the output wasn't bugged or fucked up in any way, and the visualizations never fucked over if the output was Unsigned instead of Signed. (As in Unsigned 8-bit, Signed 8-bit visualizes just fine, Unsigned 8-bit is TOTALLY fucked up..)
Oh and one fundamental aspect, Winamp3 could actually play back MP3's that have a RIFF header instead of what's normally expected for MPEG-3, see games like Freelancer, and a few others, Aliens vs Predators 2 as well.
Works for me most of the time.
I installed Winamp 5.5+ (I'm pretty sure there was a 7 and a 2 in there, but I don't remember *exactly* which one it was) into its own directory, and then moved/copied all the "old" stuff back in, as I saw fit. If I know it comes with the Winamp installer by default, I left it. Otherwise, I used the versions from my previous install. Annoyingly, this has posed a few problems, most of which are unimportant (If I attempt to rip a CD with Winamp, Winamp crashes).
Also, I think I'll remove the Media Library. It seems to cause issues with the title/tag display in the playlist. I think this is related to a combination of the Media Library, and having "Advanced Title Support" (or whatever it's called) disabled.
As for the buffering issue mentioned above, Winamp plays 1-2 second files just fine for me, so long as they are not the file I play first (they have to be in the playlist, and Winamp has to reach them as it goes through the playlist). I have my buffer settings at 5-10 seconds. Something really high. It makes the gap between songs much, much less (almost my entire library is accessed from within some kind of archive. I use in_zip a lot).
Honestly, perhaps I'm blind, but I can't think of any serious complaints I have with Winamp. In almost all instances that it's crashed, I've known the reason for it (usually it's my own fault. Often, however, it's crappy plugin. Most recent offender: in_skool/in_oldskool. It plays a ton of Amiga formats. When Knurek posted the Amiga Archive, I installed in_skool to see if it could play them. It plays most of them, but crashes if you attempt to do anything else...). Though, recently, I haven't used Winamp as much as I used to, and I only very recently upgraded to 5.5+ (I was using 5.5<something> previously). Maybe I'm just lucky, for once (odd though that may be). Mouser X over and out.
Guess I'll grab the pre-5.57x Winamp...
No, that colour scheme is what appeals to me, and it also prevents my parents from ever understanding or making out a single thing on my screen...
The fix is due to an issue that occurs when either installing Winamp, or running it for the first time (something it does to my mingw32-built dlls). If it still doesn't work for you in 5.572, try installing the fresh dlls (from this site) again.
I haven't tested any of this myself, though.
edited 2:56 PM EDT March 15, 2010
If you look CLOSELY in Winamp.ini you can see that the variable for this setting has the word "hack" in it, so yeah, it's just a shitfix that ends up breaking something else along the way...
It's best to keep the buffer as low as you can get it, otherwise, you'll have to deal with serious sound lag in EQ\DSP setting changes (obvious), BUT, also the memory\device viewer in NEZPlug++ and other things...
mp3s always have a short gap at the beginning and end of 'em. When you loop it, it is very noticeable. To avoid it you need to wither do some 'correction' in the way of stripping out the silence, or implementing a buffer and db monitor which is obviously a much more beneficial route to take because it open up the way for simple cross-fading for those that like that.