Hi there.To tell the truth, I'm a little surprised. Considering FamiTracker popularity, I thought there is already a decent plugin for popular media players, but the only thing I found is stand-alone player project, which IMO is not the best way to go.

I believe many of us use players like Winamp, Foobar and XMPlay and create playlists of many mixed module formats.I personally use XMPlay (it can use its own and Winamp plugins) and listen to over 30 music formats shuffled together, since majority of trackers and (even very exotic) formats have their own plugin. Unfortunately, FamiTracker isn't one of them and I can't include many awesome .FTMs in my regular listening sessions, which makes me sad ;) And it's a pain in the ass to launch Fami for every single module and play it manually.

So I guess it's right about time for this kind of plugin, isn't it? :)Not the .NSF but .FTM one, maybe with nice pattern display for XMPlay (like some plugins, i.e. HivelyTracker).What do you think?

I don't think this is the right place to ask for a plugin. Plugins for things like playing other module files are often handled by third parties. For FamiTracker, all jsr is responsible for is the main branch of the official program.

There also may be a potential shitstorm brewing, so be prepared.

I have permanently switched to 0CC-FamiTracker. If and when JSR decides to update vanilla FamiTracker at this point is entirely out of the question for me.YouTubeTwitter

In someway, this could be useful, but the file assiociation would sorta screw up.

If such a plugin exists, FamiTracker could simply have an extra option in the Windows Explorer context menu as "Play in FamiTracker" instead of directly opening it in Winamp/XMPlay/Anything that supports Winamp Input Plugins

slowly ceasing to exist."8BitZ caresses his keyboard as he orgasms to the sounds of Winamp."-retrodpc, 2015

Personally I think FTM files should always be associated primarily with FT itself rather than any other programs. Of course the user can decide how to associate their files, but a "Play in FT" context menu option seems overkill imo. "Play in Winamp" or something similar seems like a better option for me (of course this is just based on opinion).

How about compatibility between each FTM file version? And what about modules that use multiple chips/channels?

This said, it actually IS possible to make WinAmp plug-ins because cpow did release a library to work with FTM modules. Technically, you could even replace the uFMOD library with cpow's when you decide to make a keygen & use an FTM module. This said, I wouldn't expect this to happen anytime soon. When it does, all praise to the one who pulls this off.

AceMan wrote:

FamiTracker is not a player and .ftm is a project file, not song file. Create .nsf files if you want to listen to them in player.

That's not how it works in module/tracker world

Actually, that is exactly how it works in the scene. Programs like FastTracker have been programmed in such a way as to revolve around the extended module's protocol to be able to display it like a project file, when in fact the XM file itself is actually a firmware file type for the Amiga's audio chip. FTM, however, is not a firmware file type, for if it were, we wouldn't need to convert to NSF to be able to inject into homebrew NES games, or to burn onto flash cartridges.

Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!(Lousy modern technology!)