Winamp 3 Plugin

F

fredhead

New member
I was wondering if someone could modify the winamp plugin to work with Winamp 3. I imagine it would be quite easy, but I have no coding/compiling skills.
 
from what i've heard about winamp3 it should accept the same commands that winamp2 does. it should work without any modifications.

winamp3 does have a new system to handle plugins but it is supposed to be backward compatible.
 
i tried using the winamp 2.x plugin manager for winamp 3 so i could emulate winamp 2.x calls, but it still doesn't work =(

fredhead said:
Well, when I tried to use the remote with winamp 3, it would not work. Any suggestions?
Click to expand...
 
tracker00 said:
i tried using the winamp 2.x plugin manager for winamp 3 so i could emulate winamp 2.x calls, but it still doesn't work =(
Click to expand...

Winamp3 may use a different window naming scheme. So the plugin may never know that "Winamp" is actually open.

right now winamp 2.x still tells windows to call itself "Winamp 1.x" this is just for backward compatibility.

with winamp3 they may have finally taken this out... but remember winamp3 is still in beta, so all features amy not be in there yet.

i'll take a look around the winamp3 sdk later and see if i can find anything interesting.
 
I wanted to ask this question for a looong time but never got around to ask... :p

what's so good about Winamp3 (apart from the flashy skins) that people like it so much? I mean, does it actually sounds better than Winamp2? It is even using 100% CPU with some skins at idle!!! :mad:
 
I prefer Winamp2 myself. Winamp3 right now reminds me of the times I tried switching from Netscape 4 to 6... Slow, and slugish. Do they use the same framework? Hopefully it'll improve given time...

NiDan or anyone doing a plugin, some random thoughts: :) As far as I can tell, they completely removed the old message-based ipc thing, and I couldn't find any WM_COMMAND or WM_USER being passed around. You could send WM_KEYDOWN, but I'm not sure if keys needing shift keys will work. Or you could use keybd_event(), but then you'd need Winamp to be always in the foreground. Plus with both, it's hard to find the main window since they named everything the same! Read through a few Wasabi code last night... Some interesting things that might work in - common/corehandle.h and studio/api.h. Maybe a Wasabi bridge thing that would emulate a Winamp2 window would do for now?
 
cow said:
NiDan or anyone doing a plugin, some random thoughts: :) As far as I can tell, they completely removed the old message-based ipc thing, and I couldn't find any WM_COMMAND or WM_USER being passed around...
Click to expand...

the old system of WM_COMMAND and WM_USER was completely removed and the wasabi system was created. there is a winamp3 plugin that does exactly what you want (emulate winamp2) search the winamp.com forums and you'll find it. Run that plugin and almost every winamp2 plugin will work like they do now.

right now i completely agree with you. winamp3 just doesn't do it for me.
wasabi is almost as complicated as win32... that's an achievement in of itself.

it's still a beta so they may put the WM_ stuff back in for the release version.
 
You must log in or register to reply here.
Back
Top