View Issue Details

IDProjectCategoryView StatusLast Update
0002528MMW v4Playerpublic2013-12-10 00:41
Reporterjiri Assigned To 
PriorityhighSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Product Version2.5.3 
Summary0002528: MM Not Compatible with latest Winamp 5.3+ Unicode Input plug-ins.
DescriptionThere are reports of problems with the latest WinAmp plug-ins, see http://www.mediamonkey.com/forum/viewtopic.php?t=10771. We should check out if there's really anything needed to change in MM.
Additional InformationThis Is referenced to all Winamp Input plugins from Winamp 5.3 and above that uses Winamp Unicode Structure Described in Winamp SDK 5.32
TagsNo tags attached.
Fixed in build

Relationships

related to 0003325 closedpeke Handling Custom/Advanced Messages and setups Introduced in Winamp 2.72+ 

Activities

peke

2006-09-29 21:08

developer   ~0007956

Last edited: 2006-09-29 21:18

I have localized the problem and it looks that it can be clearly reproduced in case of using in_!mpg123 plugin downloaded from this page
http://otachan.com/in_!mpg123.html Version for Winamp 2 works perfectly and version for winamp 5.3+ do not work it just skips thru playlist due to use of this library http://www.win32lab.com/fsw/mp3infp/

More info:
http://www.hydrogenaudio.org/forums/index.php?showtopic=18530&st=200

peke

2007-01-10 03:25

developer   ~0008404

It Looks that we need to make support for new export Function winampGetExtendedFileInfoW which is used to gain info for decoder/in_plugin

We should include check in MM for winampGetExtendedFileInfoW Function and make MM To Export/Import it in Case Input plugin sends _EXTENDED_ Msgs to MM (Check WA_IPC.H for descriptions). Most of Extended info is handled in Taginfo.cpp and MM do not use plugin features to write tag Filename is essential to be available to set thrum winampGetExtendedFileInfoW which should make those plugins work.

I have uploaded sources to FTP, assigned to Jiri to determine what we shell do next and shell we proceed with change of WinampPlugins.pas, MP3Utils.pas, playlistmanage.pas

jiri

2007-01-12 10:54

administrator   ~0008418

Ok, can you try to make some simple implementation of winampGetExtendedFileInfoW support in WinAmpPlugins.pas, so that the plug-ins work fine in MM?

peke

2007-02-05 14:05

developer   ~0008526

Ok specs are, when I finish implementing of function itself I'll need your help Jiri to change APP MSGS handle accordingly so that MM could receive them correctly and all should work.

jiri

2007-03-09 16:45

administrator   ~0008755

I see something implemented in SVN Revision 2375, Peke please describe what it does, how well is it tested, etc.

peke

2007-03-09 22:21

developer   ~0008760

In Revision 2375 I have Updated SVN with updates that on plugin Loading MM test for Existence of Extended Input Plugin Functions exported and flag that plugin as extended. Also On play MM Fill info and calls That function to initiate and fill extended Info. I didn't closed this as it do not work completely, but SVN is updated as no changes to MM behavior/functionality is compromised.

Maybe a debug of in_!mpg123 sources can revive something I missed in filling that info.

jiri

2007-03-10 19:17

administrator   ~0008763

If it doesn't do anything useful yet, then I'd prefer if you remove it from the sources for now and only add it back later when it fully works. Currently it can introduce bugs, without any positive effect...

peke

2007-03-19 02:54

developer   ~0008837

SVN Updated and Changes Commented to avoid introducing bugs.
Will debug much closely with MSVC++ 8.0 to see why it didn't work like it should.

peke

2007-03-27 04:49

developer   ~0008897

It Looks that all problems relating to New Winamp plugins after though test of in_!mpg123.dll both for WA 5.32 (in_!mpg123_118ot112.1.7z Ver. 1.18y ot112.1 for WINAMP Ver. 5.3 or newer) and older version for WA 5.24 and less (in_!mpg123_118ot109.2.7z Ver. 1.18y ot109.2)

All come to simple solution to detect and include this in MM for determine what type of plugin is used as input plugin.

#define IN_UNICODE 0x0F000000

#ifdef UNICODE_INPUT_PLUGIN
#define in_char wchar_t
#define IN_VER (IN_UNICODE | 0x100)
#else
#define in_char char
#define IN_VER 0x100
#endif

After these changes winampGetExtendedFileInfoW referring to Unicode version of App.message 290 and need to be Unicode formated which current MM winampGetExtendedFileInfo will fail and plugin will not work.

I'll update All needed Units and Add WAUnicode Property so that MM Will be compatible with WA 5.3x+ input plugins

peke

2007-03-29 17:29

developer   ~0008921

SVN Updated and tested with http://otachan.com/in_!mpg123_118ot112.1.7z that didn't worked in MM 3.0 Alpha 3

jiri

2007-09-20 16:19

administrator   ~0010837

Just tested with in_mp3.dll from the latest WinAmp and it doesn't work, because it needs IPC_GET_API_SERVICE which we don't have implemented. It looks like they are making this too complicated, implementing this probably isn't a simple task and so I don't know whether we will be able to still support in_mp3.dll (and possibly some other native WinAmp input plug-ins) in the future.

peke

2007-09-21 01:04

developer   ~0010853

I get same conclusion, Winamp API in MM is too old and we need to think whatever we shell do if we want to support newer plugins, there is issues with Configuration, and with VIS_* that embed in Winamp UI.
I looked WA 5.34+ SDK and tested few new features.

peke

2013-12-10 00:41

developer   ~0038636

Winamp will cease to exist as of December 20'th 2013