Input Plugin Api Information / Discussion

[sheh]

Are there any docs explaining the more exotic functions, like Vis, DSP, etc.?

The input plugin interface is really a surprise. I expected a simple interface for decoding and metadata, and found out the whole playback plugin chain is controlled by the input plugin. Now I know why various things behave strangely depending on input plugin used.

[thinktink]

Are there any docs explaining the more exotic functions, like Vis, DSP, etc.?

The input plugin interface is really a surprise. I expected a simple interface for decoding and metadata, and found out the whole playback plugin chain is controlled by the input plugin. Now I know why various things behave strangely depending on input plugin used.

No separate docs for the other plugin types you mentioned as far as I know. Just look at the comments in the SDK headers and the example plugins included in the SDK.

[thinktink]

winampSetExtendedFileInfo(W)

[Quandry]

In the documentation "Reading_and_Writing_Extended_Metadata_Information.h" it defines both of the writing function winampSetExtendedFileInfo(W) as both having wchar_t * values but the value parameters for winampGetExtendedFileInfo(W) as char * and wchar_t * respectively.

The following taken from "Reading_and_Writing_Extended_Metadata_Information.h":

code:
extern "C" __declspec(dllexport) int winampGetExtendedFileInfo(const char *fn, const char *data, char *dest, size_t destlen)

extern "C" __declspec(dllexport) int winampGetExtendedFileInfoW(const wchar_t *fn, const char *data, wchar_t *dest, size_t destlen)

extern "C" __declspec(dllexport) int winampSetExtendedFileInfo(const char *fn, const char *data, const wchar_t *val)

extern "C" __declspec(dllexport) int winampSetExtendedFileInfoW(const wchar_t *fn, const char *data, const wchar_t *val)

Is it supposed to be like that or is the documentation wrong on the value parameter for winampSetExtendedFileInfo?

[Benski]

hi.mp3 (or hi.ext) is used to find the input plugin associated with the 'default extension' in the preferences.

the unicode variants of the dllexported metadata functions do in fact take the field name as a char * (ascii string)

[thinktink]

hi.mp3 (or hi.ext) is used to find the input plugin associated with the 'default extension' in the preferences.

...

Oh! Dadgumn was I wrong. Thanks.

...

the unicode variants of the dllexported metadata functions do in fact take the field name as a char * (ascii string)

Excellent (well, not the documentation part.)

[thinktink]

...
the unicode variants of the dllexported metadata functions do in fact take the field name as a char * (ascii string)

Oops, wait a minute, you said "field name." Are you referring to the "data" parameter or the "val" parameter? I was talking about the "val" parameter, "field name" implies the "data" parameter.

[Benski]

ohh. weird. where does it specify that? it should definitely be const char * for winampSetExtendedFileInfo

[thinktink]

ohh. weird. where does it specify that? ...

In the documentation "Reading_and_Writing_Extended_Metadata_Information.h", at least the copy I got from the SDK download if memory serves. I'll double check that.

[thinktink]

...the copy I got from the SDK download if memory serves. I'll double check that.

Scratch that, it wasn't from the SDK, I think it was an archive from DrO's website that I downloaded a long time ago linked in a post above. DrO has taken it down so I can't verify my statement because I seem to have misplaced the archive download, how I don't know since I still have the original SDK download right in my Downloads folder.

[thinktink]

Double whoops, I just had a look at the Wayback Machine. It was "Reading_and_Writing_Extended_Metadata_Information.txt", not "Reading_and_Writing_Extended_Metadata_Information.h", I must've renamed the file so that it would pop up and show formatted in my editor. It was also not in an archive, it was just hosted directly as a txt file on his server.

[animetedzone]

look like someone is stack in the real problem.