MilkyTracker’s XM playback is not very accurate. Several effect commands aren’t implemented and some contain “bugs”.
The FT2 clone should probably be 100%, considering he got hold of the original source and is generally very picky about accuracy. I would assume OpenMPT is also accurate, or at least close to accurate, with the drawback of having a horrible GUI.
EDIT: That being said, I do prefer Milkytracker as well
16-bits version of FT2 is really nice and even supports sampling inside program, which Milkytracker to my knowledge still can’t do… Then again I prefer Schism Tracker for oldskool tracking thanks to its keyboard oriented interface.
I tried to get into OpenMPT some time ago but like Joule said, interface is just horrible with its Visual Basic looks. Renoise does a lot more and its interface is miles ahead. Of course OpenMPT has a very good compatibility with lots of different old module formats so it’s good for playback purposes.
Can someone post a screenshot? Too paranoid (translation: lazy) to install an .exe file without access to the source code from some person I don’t know like it’s 1999.
Disclaimer: Irrational exceptions to the rule a plenty.
I can totally understand why you think that, but the sad truth is that I don’t have anything better to do, and I’ve gotten a lot of positive feedback from making the FT2 clone.
Also yes, my clone should be very accurate since I ported the original replayer and mixer from asm/Pascal to C. I care about small details more than what is healthy, to put it that way.
The source code for the clone is available these days btw, but it’s not going to be a nice read.
How about adding filters and fast bounce track in project? Litlle hacks for more productivity.
Thnx
I’m not going to add more features I think, especially not to the XM replayer. The point of the clone is that what you hear in the tracker is what you’re going to hear in real FT2 and other XM-compatible trackers/players as well. Trying to keep it authentic.
Why not write you own simple tracker to your own specification? If you can’t…learn (you might get more out of computing)? Maybe use 8bitbubsy code as a starting point? Then you’ll start to get an idea just how difficult/tricky and the problems developers face to try and find solutions to (what non programmers/general users think) are straightforward things. People don’t see the bigger picture, only focused on what they want and only focused on what they want to see/hear. I can tell you that what 8bitbubsy has written is difficult and hard work, I take my hat off.