Winamp3 Build #499c Released
 

For all you Winamp3 junkies who are left: a present. Winamp3 build #499c. Please discuss it here. Yes, we know about the bug with the about box.

[edit]I have been asked to reiterate that this build is not supported in any way. Please do not distribute it.[/edit]

any changes from the last #499?

Try it and see ;) (translation: I'm too busy to try it). It likes to crash a lot for me though.

Yes I am junkie!!!

Works fine!!! (If you like crashes)

I am now the user of Wasabi Player!!!

hint: Name change Winamp3 -> Wasabi Player

Other things:
Weird fonts
Everything looks kinda weird!

Includes gen_ff changes from Winamp 5

TTF (TrueType)

fonts where changed, name was changed, skin was changed, plus a HELL of alot of source code changes.

for those that actually work with wasabi, you will notice that the base studio folder is now GONE. :) AND, the SDK compiles alot easier than the few other previous test SDKs.

more thoughts from me will come soon when i get time to rant.

winamp3 is evil!

everything is so dark and dead.

not bad at all and it works ok on the ol' work machine :)

the font changes are a bit naff but the menus seem nicer for it so it's evens on that i guess.

to play some more on my machine (muwhhaaa...)

-daz

Why don't we get to have #500? it's stable enough to hack into Winamp 5, but not alone??

#499c seems great. things i noticed:
-text in monitor aspect setting (playlists->display) is cut off (minor annoyance, but looks unprofessional, should be fixed b4 final).
-extension list text disappears?? (fixes on restart)
-I like the new font. it's clean and legible.

~WHEREamI

Eh? We're saving the build 500 number for a Windows/Linux release, that's all :).

actually, bas was talking about possibly resetting the build number, as its no longer "Winamp3".. now that it is "Wasabi Player", it should be completely seperated from the winamp name, and therefor, wont get the comparison to winamp v2.x bashing that it always got.

well, i thought the build number more came from the Wasabi build number than the player itself. they kinda go hand-in-hand though, i guess.

hehe... we should make sure it's "Wasabi Player" and not "Wasabi Media Player"

@Russ: oic. makes sense i guess? gen_ff is based on #500 though, right?

Gen_ff was forked off the Wasabi tree a few months back. It's based on #499.

Anyone got Yonido's J-Key working?

Any idea on how to get it working would be nice!

I got the Jump Windows but it's blank!!

lol! we get to have the incremental linker file for avs!! but no wac :(

ok, something to note with wasabi player....
ive been messing around with this things day and night since it was built...

i have NOT be able to get older components to work with it... they will have to be re-compiled.

bas had issues compiling AVS with this SDK, that is why it is not included. you can force-install AVS, and itll crash when you open the window.

there are TONS of improvements all over the SDK compared to the original b499. the FormWnd is really nice.. i like it alot, and RM-X now uses it for its configuration. Without modifying any code, i was able to compile DeJaVU Meter for Wasabi Player, and with a few hacks, i also managed to get wIRC up and running.

any other questions? please ask...

and remember... it is NOT Winamp3. :) thank you.

hmm, both good and bad..

good: Wasabi can be developed for Wasabi Player entirely and not just Winamp 5 (ie: more time for Wasabi Player related work)

bad: Wasabi/Wasabi Player will have a hard time following Gen_ff/Winamp 5 when it comes to skin compatibility.
For Wasabi Player to ever have a chance, it will have to fully support Winamp 5 skins, just like Winamp 5 need to be able to fully support Winamp3 skins..

Other than that, I've been looking forward to this day along time now.

on to other things....

About the fonts:
Wasabi Player now use Freetype fonts as default (can it even be changed to TrueType? I tried in configurification but it changes back again to Freetype) as do Winamp 5 for Modern skins.
This change has affected every single place there is a textline, for better or worse.
But it's no biggie, stuff (xml) will just have to be fix0red a little and problem gone...
Though with this move, it's important that both ttf and freetype text will look good (though freetype will probably be prioritized cos of portability)

Skin changes:
default standardframe is now in Wasabi Player/themes/default (this is a good thing, since it was all spread out in the Wacs dir before)
however, will this mean there will be a way to switch the theme? would be cool, cos personally I like the 499 skin better than 499c.
New skin is largely built using xml-generated graphics (this is why it looks like it does) which is a lot faster to load than regular bitmaps.

I think this release marks the start of very good things to come..

-Plague

Are we now *trying* to cause confusion?? :D kidding.. i think it may cause confusion for a while, but after the confusion clears, it will be even less confusing. 'cuz right now, i completely understand the whole situation, but i'm still confused :igor: :D

actually, since there are so few who care about wa3/WP anymore :( :cry: , it may cause very little confusion.

also, that means this thread is misnamed, and so is the download. and there are a lot of refferences to winamp3 in the prog itself. oh i love being picky! such fun.

~WHEREamI

Have a little faith.
People stopped caring for more or less two reasons:

1. There was only one public release of Winamp3 and it was way too early (thank you AOL). Alot of people liked it, some didn't.
Among those who did like it, alot of them never realised there were alot of developer builds released and got tired of waiting for a new release.

2. When AOL pulled the plug on Winamp3, most of the users who still cared enough about it to actually develop something for it, stopped. Only a very limited number of people willing to develop for it still exist.


So, what have we learned from this?
Well, two things:

1. AOL are evil ;)

2. Public releases attract users.
But, before going 1.0, take the time to make it 1.0 worthy.
During that time, make sure to release developer builds, because that attract fellow developers and some hobby users.
After going 1.0, make sure to release public updates atleast once a year in order to keep the users and attract more users..


If things are going well (it will, if AOL let it), I think the Wasabi userbase will grow again. Maybe there'll be an entire new userbase consisting of people who didn't go from Winamp2 to Wasabi (wanting Wasabi to be something it isn't)..

-Plague

i cant belive im the only one who has noticed why the font stuff has changed... it now uses freetype rendering and not truetype.
and i think all wa3 forums should be killed and a litle section for wasabi and wasabi player opened.. as they are somthing DIFFERENT! like wa2 isnt wa3... wasabi player isnt wa3 also..
gen_ff + winamp2 = winamp5.. that is only there till wasabi matures into a stable enough system to have a new player built totaly on wasabi again.. by the time this happens... wasabi player will be more stable than anything

also. WHEREamI. please.. there is no build 500 so how could gen_ff be made with it?

i think russ jump the gun a little with putting 499c on the forums as alot still needs to be done to it.. it is just a snapshot of current code.. it isnt a release.. but anyway... tis late and im going to bed.. bye

Bizzy:
No, you're not the only one who noticed.. :)
Look a few posts up:
-Plague

This mod would be very happy with that happening.

I'd rather everything went into Wasabi Development to start with - I can't see that much activity happening, and it'd be nice to have it all in one place.

yes, i now realize my error. i somehow got the impression that there was an internal, unreleased build 500. i now know that gen_ff was forked off around 499. but i still look forward to a build 500, purported to have a Linux version.

Im junkie too!

I love it!

The King is dead!
Hail the new king, Wasabi Player !!!

I still can't get used to the Ugly media library in winamp2.9x/5 and the way you manage your playlists! (wa3 had a great playlist.. and in wa5 you gotta open the library for the playlists)

Plus, wa3 has gapless playback!

I hope that in a year or so we'll have a powerful wasabi platform to build on a great player...


i do hope that brennan keeps working no it!

plague: [wpdir]/Wacs/wasabi.system/platform/freetype.wac <<< just delete that

uuh, that's a little TOO radical..
I don't mind having Freetype fonts, I just wanted to clear up whether the config reg setting works or not...

-Plague

So does Winamp 2.x/5.x
__________________________________________

Anyway, all hail the Wasabi Player
TF it isn't dead.

Question is, will it be Nullsoft Wasabi Player?
ie. supported on this site with its own forum(s).
I hope so . . .

It will become apparent that this question doesn't in fact matter.

Ok, it was released a little early in my opinion. =\ Although it nice to know that you guys are working on a project thats not just about looks! I will be quite pleased if a new project forms out of this, for a player based on wasabi kicks the shit out of what ever winamp2 is. I do like winamp5 but its a tinker toy compared to what winamp3 can do. I dont know what it is winamp3/wasabiplayer seem to be more comfortable to me. Even though it crashes and such keep up the good work fellas your getting somewhere!

The decision to release it was controversial, but I decided to release it because a hell of a lot of people thought the project was dead. And while this may not be particularly usable, that wasn't my intention. I released it to show that Winamp3 isn't dead, and that it's back with a vengeance.

And believe me, this isn't the last surprise we have lined up.

bug report
 

anyone else get a whole lot of error message boxes during the install?

it keeps saying stuff like:

-----
winamp3.exe - Entry Point Not Found
-
The Procedure entry point ?_dispatch@SysCallbackI@@MAEHHPAXPAPAXH@Z could not be located in the dynamic link library common.dll.
-----

when the install finishes, I get to see the winamp 3 splash screen, but then the program just crashes :(

i tried redownloading and reinstalling..

cancel that bug report :)
 

Ah, thanks.. after I uninstalled everything worked fine. :)

Screenshot? Can anybody post it...
and that skin download too?

skin
 

here's the skin.. had to zip it for the forum to accept it

http://darkain.skin-zone.net/comments.php?rootid=27

here are 2 images... the first is RM-X on b499, the second is RM-X on b499c.

(yes, i know the page doesnt load 100% correctly in MS-IE, i just havnt gotten around to fixing it yet)

Thanks! ;)

I like it, it looks more "Linuxy", which is allways good. Windows font rendering is fugly!

I agree the references to winamp should be changed, to diefferentiate this. IMHO it should never have been called winamp in the 1st place.

Lookin forward to theses "surprises"!

I never realized how many times I opened the about box until I ran into this build :p

Per-user settings
 

Thanks for still developing this one! This is my favorite mp3 player. :up:

There are few bugs persisting in this build

1. Support for per-user settings is buggy. It works when path to "Documents and Setting\Username\Application Data\… " contains only US characters, but when some e.g. accented or engraved character is used, paths stored in studio.xnf are stored or read incorrectly, so no playlists are loaded at atartup, even if they are physically present in pledit folder as well as in studio.xnf (this bug is present since per-user support was introduced-I think I reported it already using bugzilla).
2. Same problem applies for playlists named using such characters.
3. The font used in this build is HORRIBLE:cry:-I use LCD display with 120 dpi resolution and I can't see almost anything. (Winamp 5 has the same problem, but I didn't care much as I uninstalled it in few minutes :p ). Please see attached screenschot-it's not scalled-this is really what I see :igor:. I think I'll have to resort to original #499 :(
4. When LAN network path ("\\Server\dir style", I didn't check if it applies also to mounted drives) is not accessible, WP lags for quite a long time.
5. I liked that dark gray taskbar icon from original #499 more than this white ;)