Winamp 5.55 SDK

[Benski]

http://dev.winamp.com/wiki/Plug-in_Developer#SDK_Documentation

http://download.nullsoft.com/winamp/plugin-dev/WA5.55_SDK.exe

Much thanks to DrO for providing additional documentation for wa_ipc.h

Much of the new functionality in the SDK is not yet documented. Please use this thread for discussion, and we'll add information about topics discussed into the SDK.

[edit - DrO 21/01/2010]

Below are a number of threads which have been kept as stickies in the past and may be of some use when developing plug-ins along with what is detailed in this thread and the sdk itself.

Winamp 5.04 SDK (Installer Rev #3) (soon to be deprecated but has information still!)
Winamp Application Programming Interface
Language Pack Guide
Useful Info -> What info should you know when making plugins?
Empty general purpose plug-in project.
ml_pmp SDK
Input plug-in transcoding extentions.

[DrO]

As benski mentions, somethings still aren't fully documented (there's still some merging of the wa_ipc.h i'd had prepared to be merged in and a few of the other wa_*.h files) and also some of the example projects need to be cleaned up still but this will give you a good idea of the new apis.

-daz

[whoami]

Hmm, hmm, hmm.... huh?

Where did wa_msgids.h go?

[DrO]

wa_msgids.h was never an official header and is something i created myself. will look at making it official with benski before final.

-daz

[dllmain]

I stumbled upon the line

int (*sf)(int key); // DSP_HDRVER == 0x21

in DSP.H. What should this function do and return?

[salnet]

If I try to open the main.rc in lang_b folder, I get errors of not found resource-files:

The error repeates with a lot of more files.
I use Visual Studio 2005.
Eventually someone could upload these files?

Edit:
I have now extracted most of all the not found resource-files from actual beta-release of 5.25 (812). The only file I've not found is manifest.xml. Eventually someone could upload these files?

Many greetings from Germany
salnet

[Benski]

I've attached it. Note that the version is listed as "5.0.1.1". Our build system automatically patches this file before each release. It doesn't really make a difference, but to be correct, you can modify it to be the same as the Winamp version&build number (e.g. 5.2.4.703)

[dllmain]

The the new IPC_UPDATE_URL command

#define IPC_UPDATE_URL 3012 // pass the URL (char *) in lparam, will be free()'d on done.

confuses me: What does it do without a browser?

[DrO]

a number of the newer apis are really just for internal processing between some of the native plugins to winamp.exe and aren't really for anyother use. i'm sure what that one will be explained if it is of any real use nearer to/in the final 5.25 sdk

-daz

[salnet]

Originally posted by Benski
I've attached it. Note that the version is listed as "5.0.1.1". Our build system automatically patches this file before each release. It doesn't really make a difference, but to be correct, you can modify it to be the same as the Winamp version&build number (e.g. 5.2.4.703)

@Benski!
Thanks for that file.

Now I've got another problem:
When I want to compile the language-file, I get the following error:

.\main.rc(16) : fatal error RC1015: cannot open include file 'wasabicfg.h'.

The file wasabicfg.h doesn't exist in SDK. Also missing: afxres.h

[DrO]

there shouldn't be any reason for that file to be needed and with a few modifications i can happily build the language file (moved tips.txt into a resource folder and disabled all of the icon, bitmap and cursor references). basically i'd just comment out those lines if they're still giving you issues (like in the modified version i've attached all files of)

-daz

[dllmain]

I noticed SAAdd and VSAAdd are returning
int now instead of void. What values do
they return? Does this change cause stack
trouble if an input plugin calls one of these
functions expecting it to return void?

[shaneh]

Return values arent stored on the stack, they are in eax. The return value would simply be lost. Im not sure if theres any compilers that would assume the value of eax would remain unchanged after a function call. Although I guess its possible if the function was declared to return void.

[Benski]

They've always been functions that return int. They were just (incorrectly) put as a returning void in the SDK header files. It removes any possibility of something going wrong re: the return value.

[rhywek]

Would you be so kind to provide zip version of the SDK? I won't have access to Windows machine for some time. Also sending executable files by mail is not reliable (virus protections, etc.).