Originally posted by chros
If I toggle on the Crossfade button on the Modern Skin, and switch back to the Classic Skin, the playback is still remains crossfaded, which is a greta thing !
But I have to switch between skins if I want to switch On or Off this feature ! That's why I have asked this question ...
So if there isn't, may I request it ?
Goto Preferences->Output Plugins->Directsound->Fading and toggle "on end of song".
That's the exact same thing as in the Modern skin.
Originally posted by EAK125@Plague - What is really wrong with the older codebase? Newer isn't always better (look at anything by real - hahaha - real sucks!) so what are the limitations of the wa2 codebase compared to wasabi (other than cross compatability)? Are there things in it that aren't supported anymore or new stuff it dosn't support - if so couln't u just update the codebase to utilize them?!? I'm not a coder so please keep and explanation to a near genius level.
Well, most things Wasabi offers can be, and is beeing, implemented in the Win32 Winamp 2 codebase.
However, the Winamp 2 codebase is still Win32 and it's plugin system isn't nearly as good as Wasabi's component system.
Winamp has most stuff baked right into winamp.exe while in Wasabi, everything is a component, even the core is a separate component and can therefore be replaced if someone makes a better/different one, as can everything else. In Winamp, you're stuck with alot of what they offer since most of it is built right into the .exe.
To the end user tho, the difference won't be that big, tho there are differences even the end user can notice.
For one, the Wasabi skin capability is more limited in Winamp 5 because alot of things have to stay unchanged in order to maintain Classic skin compatibility (that issue could have been solved for both Classic and Modern skins if Wasabi was used as codebase instead). For example, the inner section in the standardframe has a singlecolored background in Winamp 5, where in Wasabi, you can have any background you want. You can't move any content around in there either, where in Wasabi most components have a xml file with the layout specifics, which can easily be overridden. Also, the Pledit in Winamp is so ugly in Modern skins, only to maintain full Classic skin compatibility.
That's a few examples that the end user can notice.
And finally one last thing, speed.
Winamp is faster if you're using Classic skins, BUT Wasabi is faster compared to Winamp using Modern skins.
There are alot more stuff on a coder level that I can't explain myself so you'd have to ask some more experienced Wasabi developer for that.
A couple of posts made it before mine, cos I was watching Tv at the same time as I wrote this
So what I am hearing (in really dumbed down verancular) is that you have to make your in/dsp/out plugins force their way into winamp2x\5 through precut holes in the system which limits the way you can make your code.
Kinda back to the square peg\round hole analogy. Gotta trim the edges off to get it through...
Where as in wasabi you can cut your own hole the way u want it and it becomes part of the whole.
Am I close?!?
Hehe, I like this.
"Kinda back to the square peg\round hole analogy. Gotta trim the edges off to get it through..." lol
Yea you're close..