Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
FamiTracker
In FamiTracker 0.3.5 & above, even though I can open their FTM files in FamiTracker 0.3.0, only the VRC6 & MMC5 instruments function as they should properly under 0.3.0.
The problem I have is that non-blank instruments for the 2A03, as created in newer versions of FamiTracker, don't run correctly in FaiTracker 0.3.0; only the 2A03 instrument seems to break.
JSR; can you please bring back 2A03 instrument compatibility to the next major software update?
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
the solution is: don't use 0.3.0. why are you using that anyway? older projects not working with newer software is understandable and ideally should be fixed; newer projects not working with older software is to be expected and disregarded.
i'm not against compatibility, but developers typically don't support archaic versions of their software, and for good reason. problems like "oh you can't change [feature] to make your software better because then that won't work on my outdated version of famitracker" occur.
Plus, I'm still using 0.3.0 because of the fact that I find it more stable than the newer versions (aside from the fact that NSF compilation for VRC7 tracks isn't quite as one would expect).
If I tried to make a VRC7 song in FamiTracker 0.3.5+, the mixing volume will still sound messed up in most NSF players. Therefore, I don't compose in VRC7. And this is beside the fact that FamiTracker doesn't run well on my 6-year-old laptop.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
0.3.0, 0.3.5 and 0.3.6 also have different ways of handling 2A03 square channels, they mix differently. (Wanna proof? Play the same note on both channels with a blank instrument, using V01 in channel 1 and V03 in channel 2. The three versions do different things with this.)
0.3.0 also has different noise generation, IIRC.
So, yep. If you like to output to .WAV, there ARE reasons to have different versions of this software. (If you only output to .NSF, in which case these reasons are made null and void. lol)
[quote=TechEmporium]Yet 1 year old software isn't exactly archaic.[/quote]
age has little to do with it. it's an old version, simple as that. you shouldn't expect it to work with new modules. if that consideration is always made then it potentially impacts on development and progress (certainly creates a lot more work.)
if you need older versions for whatever reason then ok, but i disagree wholeheartedly with programming compatibility for the sake of supporting old emulation idiosyncracies. the FDS volume had to be changed since it was inaccurate, which made my life harder at the time, but i still always use the newest version anyway.
Yet, the VRC6 instrument always remains intact across all versions of FamiTracker that support it.
Anyways, I'm still sticking with 0.3.0 since I only output NSF & hardly do anything in the way of WAV or FTM files proper. And by this logic, JSR might as well change the FTM file specs entirely in his next release so that you can't open a single FTM file in a depreciated version.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
[quote=ElHuesudoII]0.3.0, 0.3.5 and 0.3.6 also have different ways of handling 2A03 square channels, they mix differently. (Wanna proof? Play the same note on both channels with a blank instrument, using V01 in channel 1 and V03 in channel 2. The three versions do different things with this.)
0.3.0 also has different noise generation, IIRC.
So, yep. If you like to output to .WAV, there ARE reasons to have different versions of this software. (If you only output to .NSF, in which case these reasons are made null and void. lol)[/quote]
i use famitracker 0.2.4
[quote=TechEmporium]And by this logic, JSR might as well change the FTM file specs entirely in his next release so that you can't open a single FTM file in a depreciated version.[/quote]
that's how the vast majority of software works already :J and i think yeah, that's not really a problem if it means that the newer versions work better and bring more advances/quicker updates/etc. the forwards compatibility is probably not by-design right now anyhow (that's why it isn't working properly for you.)
True, but at least have a more unified file spec for FamiTracker instrument files where volume/pitch/duty envelops are preserved for the most basic chip.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
Why are you making 2A03 instruments in the new version and then trying to open them in the old? Why not just build them in the old version? How/why is the newer version involved in this process?
You seem to be having a problem that's kinda... unique. What kind of workflow do you have that requires this regularly?
I'm not making instruments in the new version to use in the old; you guys are making the instruments. :P
It's not a unique problem; it's just that you don't understand what's going on when I try to see/edit what songs you make.
I open YOUR music files in 0.3.0 & only the 2A03 instruments' envelops are wiped clean, even though the envelops are still check-marked, thus muting all 2A03 channels.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
Well, it made sense to me that you have requirements for the music you make and that you might prefer 0.3.0 for that.
What I didn't realize is that you want to listen to other people's new music with it. Why not just listen to it in the newer version?
Actually I'm kinda surprised to hear that there's no FTM version checking on load... a lot of software would just disallow loading of newer file formats in the older program, instead of silently failing like this. I would definitely suggest [i]that[/i] as a feature.
) 
