in_mad v2 Winamp MAD MP3 input plugin Options

[MoSPDude]

Hi, this is a long awaited (although not fully finished) conversion and improvement of my previous updated in_mad plug-in.

The notable new features/fixes (that I can remember from notes) include,
* Re-written/ported to C++ to 'enable' better WA5 compatibility
* Fully Unicode GUI
* Icecast mp3 streaming fixed
* WA5 Global Configuration supported
* Improved basic and advanced editing
* Slightly improved ID3v2.3 support
* 32 bit output uses full internal 28 bit representation
* Advanced-style Basic formatting for WA2
* Non-Unicode backward compatible for WA2 (not fully tested)
* Multi-lingual dialogs (once someone translates!)
* Re-designed APE tag support including Unicode

The playback and EQ backend is mostly the same except ported through to C++ and into a class structure.
However some things are incomplete,
* New Binary editor disabled
* EQU2 tag editing and writing disabled

The latest DLL can be downloaded from http://www.zen23652.zen.co.uk/in_mad_2b.zip.
Source code is now separate from http://www.zen23652.zen.co.uk/in_mad_2b_src.zip

This post has been edited by MoSPDude: Jan 12 2008, 12:44

[MoSPDude]

Hi Emre,
I've dropped back to FPM_INTEL (as in my previous in_mad) mainly to see if this helps with peoples problems. As far as I know VS2005 does support 64bit signed int properly however. I kept OPT_ACCURACY on in both cases. I personally didn't notice a difference in speed, though I'd need to test it further. In mad.h, it strongly recommends against FPM_DEFAULT.

If anyone has noticed any major differences as such (eg. improved the stuttering) please feedback.
Cheers

Edit: As this is the first time I've tried FPM_INTEL in Visual Studio, it appears to not take account of OPT_ACCURACY as it did using GCC. I'll have a look into it.

This post has been edited by MoSPDude: Mar 4 2008, 09:23

[Emre]

Hi Emre,
I've dropped back to FPM_INTEL (as in my previous in_mad) mainly to see if this helps with peoples problems. As far as I know VS2005 does support 64bit signed int properly however. I kept OPT_ACCURACY on in both cases. I personally didn't notice a difference in speed, though I'd need to test it further. In mad.h, it strongly recommends against FPM_DEFAULT.

If anyone has noticed any major differences as such (eg. improved the stuttering) please feedback.
Cheers

Edit: As this is the first time I've tried FPM_INTEL in Visual Studio, it appears to not take account of OPT_ACCURACY as it did using GCC. I'll have a look into it.

Hi MoSPDude,

I did some tests with ffdshow's libmad component. i get source code via svn (rev 1882) and i did some modifications in libmad project files. i compiled ff_libmad.dll with vc2005 express and vc2008 express.

for speed test i used foobar2000 with haali's foo_input_ds plugin.
directshow filter chain: source mp3 in matroska container -> haali splitter -> ffdshow audio decoder (libmad)

test results with foobar2000's decoding speed test plugin (cpu core2duo e6550~2.8ghz):

FPM_INTEL VC8 : 115,674x
FPM_INTEL VC9 : 116.268x
FPM_64BIT VC8 : 76.676x
FPM_64BIT VC9 : 77.104x
clsid's build (rev 1882) FPM_INTEL ICL10 (SSE) : 124.217x
xxl's build (rev 1878) FPM_INTEL VC7 : 113.877x

i can't sure about this test accuracy but it seems FPM_64BIT ~%34 slower than FPM_INTEL.

cheers...

[j7n]

Hi, MoSPDude.

The last version (with ini-file) interrupts playback every time when I call the file info box. It walks the MPEG stream and updates average bitrate number. And when it does so, playback stops for half a second. Does not matter if I have opened infobox before on that given mp3.

Also, although I have selected "fast playtime calculation" and display "file average rate", it does not display bitrate from the Xing frame. Instead average bitrate of frames played so far is shown.