Will Winamp ever be ready for prime time?

[DJ Egg]

Ahh crap, right...

Well, I had a simple solution.... until now.
I'll have to think of some other method to maybe backup and replace the whole in_ffsox folder instead (see Koopa's post).

Can't you just always name the files avcodec.dll, avformat.dll, etc? Or does the version # also have to be in the filename?

Also, am I correct in assuming that any extra FFmpeg files placed manually into the in_ffsox folder should be ok,
because they won't have been compiled with MINGW?

[EDIT]

RE: reply below

Ok, fair enough.... bear with us...

[pbelkner]

Originally Posted by DJ Egg

Ahh crap, right...

Well, I had a simple solution.... until now.
I'll have to think of some other method to maybe backup and replace the whole in_ffsox folder instead (see Koopa's post).

Can't you just always name the files avcodec.dll, avformat.dll, etc? Or does the version # also have to be in the filename?

Also, am I correct in assuming that any extra FFmpeg files placed manually into the in_ffsox folder should be ok,
because they won't have been compiled with MINGW?

One of the core ideas of the FFSoX plugin is that users can substitute the FFmpeg DLLs from Zeranoe's frequent builds (http://ffmpeg.zeranoe.com/builds/). That allows the user to always use the most up to date FFmpeg version without the need of rebuilding the whole plugin. The DLLs from Zeranoe's builds contain the version number in the filename.

AFAIK Zeranoe cross compiles from some Linux using MINGW.

The version number in the filename is also important because it distinguishes binary incompatible versions.

[pbelkner]

Originally Posted by Koopa

We are already aware about it, also you can put some additional files from ffmpeg to the in_ffsox folder, iicr.

The problem is, that a simple rename does not allow wildcards.

I'm trying to find a solution for that and will provide the code change to the devs then.

That sounds promising, thanks a lot

[DJ Egg]

Done

in_ffsox.dll and the Plugins\in_ffsox folder will not be touched by the BindImageEx Optimizer as from the next release onwards :-)

I just need to know the filenames of any other incompatible plugins now....

[pbelkner]

Originally Posted by DJ Egg

Done

in_ffsox.dll and the Plugins\in_ffsox folder will not be touched by the BindImageEx Optimizer as from the next release onwards :-)

I just need to know the filenames of any other incompatible plugins now....

That's very good news! Thanks a lot, DJ Egg