FTM import has some known issues, for example trying to import files with another expansion chip gives an improper message of the file being damaged and might cause a crash.
Different expansion chips aren't needed. I recently tried to merge some files, all with no expansion, and it told me the "make sure you're using the latest version of FamiTracker" error message.
(FYI: They were Rainwarrior's Classic Chips source files. Debussy's Suite Bergamasque, to be precise.)
Ok yeah, I tried to import a few more of my own FTM's this time to make sure, all just 2a03. Some imported, but with all patterns as "0", and some didn't work at all. They just ended up giving the "use latest version" message.
jrlepage: That is related to the vibrato bug, it was caused by a problem with the build script for the NSF drivers when I did the 0.4.0 build. Sorry for this, I'll provide a fix.
LikeACloud: I'll change that.
I've also fixed some additional bugs, including WAV export and FTM import so I think I'll release another minor update soon.
Here is another bug. I don't know how to explain it well, but sometimes in the instrument editor, when I want a duty sequence number to be 0, it randomly jumps to 1 after I come back to the instrument.
Same here, Raijin. Also, I'm curious, why are some files required to be opened in 0.4.0 and with a simple hex-edit openable in 0.3.7, or even 0.3.5? (Though it goes crazy in 0.3, but anything goes crazy in 0.3. =P)
EDIT: Even weirder, editing the 0.4 output and fixing the header actually makes it compatible with anything down to version 0.3! O.o
EDIT 2: The hex edit doesn't work with MMC5! Also, the header format is being cracked.
_______________________
I have turned into a sausage.
Simple, it was done to prevent people from loading new modules in older versions with missing features. Hex-editing won't work on N163 modules for example.
It makes sense also to condition users to use the latest stable version of the program whenever possible, to prevent issues that might arise if there is some incompatibility between older and newer modules.
Here is another bug. I don't know how to explain it well, but sometimes in the instrument editor, when I want a duty sequence number to be 0, it randomly jumps to 1 after I come back to the instrument.
It occasionally happens with pitch envelopes as well. It gets pretty irritating and inefficient to create another instrument solely so it'll work, especially since if you try to save and reopen, it saves the macro switch with it...
_______________________
[BURNING LOVE] YouTube Twitter (Stay off my lawn, kids)
