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
I messed up my computer and therefore can only use famitracker in Wine, but when I go to add MMC5 or another expansion chip to something I create, FamiTracker just crashes. Plus, when not crashing, lag increases steadily.
Plus, there are, like, 3,000,000 extra bugs that aren't there in XP.
And to add to it, I'm already pissed off very extremely. This is just bringing me closer to watching 300 for the enjoyment of seeing blood.
Any help to this, or maybe a release of an adjusted version?
Famitracker uses MCK. Which is windows. Plus, I'm not good at compiling programs, which is required in order use a linux C editor. Unless I magically remember the name of the one I used to use. Which probably won't happen.
(And before you say "click configure, then install", please note I always follow the steps directly, and it never seems to compile it)
You can't use C language to edit FamiTracker readily because FamiTracker's an MFC application; it's a program that uses libraries intrinsic to Windows only (& can't be ported to Linux without a full rewrite).
You need Visual Studio or some other Windows-based IDE to compile MFC applications, sadly.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
I guess you could remove some of the features that use Windows-only libraries. Or you could just install windows in a dual-boot setup, but that seems a little excessive.
_______________________
If there is evil in this world, it lurks in the hearts of man.
--Trinicus D. Morrison
The Final Fantasy IX 8-bit project: 3 complete
http://famitracker.shoodot.net/forum/posts.php?id=1624
Need I say again that I messed up my computer and can't use windows anymore? I already have it on double-boot, it's just messed up terribly because I was stupid enough to try and install a second windows installation without a product key.
I only have a few minor bugs with FT in wine, but they're possible to avoid/get used to... I never had any problems with expansions at all so this is a little weird.
[quote=xolroc]I guess you could remove some of the features that use Windows-only libraries.[/quote]
Whole user interface. You can make a new tracker with comparable efforts.
I get a weird lag issue on Wine too (But it's obviously something Wine needs to patch up, not Famitracker). It sucks up >100% of CPU the whole time it's running. Granted I have an old computer (3Ghz Pentium 4 w/HT, Ubuntu 10.04) but it's not THAT old; it should be able to handle Famitracker just fine. An even slower Windows XP machine uses only 5-10% - while playing lots of expansion channels.
That's the only thing that makes tracking really difficult under Wine for me. I only get a few minor annoyances besides that, and way less than 3,000,000 bugs
I'm just wondering if anyone else got the same issue, and if they found a fix or at least the source of the issue? Maybe it's some side effect of HyperThreading going awry? that's my only guess.
I want to write a custom tool to convert a FTM file directly into music data for NES game development. I find it tedious to edit a FTM file, then manually export using the text exporter, then run yet another conversion utility. My idea is that the FTM file(s) would be the only source that I would keep in revision control. My build script would invoke my tool to directly generate ca65 compatible ".s" files from the FTM files. Those ".s" files would then get assembled and linked with the rest of my game code.
I would happily share the source code (I'll write it in ASNI C) to any such utility that I create with the Famitracker and nesdev community.
I understand that the internal format of the FTM files is "only documented in the source to famitracker" and "subject to change" and that changes are generally not backwards or forwards compatible.
As such, I would greatly appreciate access to the 0.3.6.b4 version of Famitracker's source code, or to know that 0.3.5 (the latest src available on this web site) uses the same FTM file format.
I humbly suggest that on the next major release of FT, that the FTM file format be converted into something ASCII (so that it can be parsed in perl or python easily), or that version info be added to the binary FTM file, so that direct conversion tools can use the correct conversion / extraction logic.
I would be willing to take a stab at this code change myself in a few months (I'm kinda busy atm), if such a change would be welcomed.
I say all of the above without actually looking at the existing FT code. I've studied the FTM files with hex editors. I'm no stranger to writing utilities to extract meaningful data from binary blobs, even without the source code to the official blob generating utility... But real source code is very helpful and saves lots of time on reverse engineering and block-box testing efforts.
) 
I've studied the FTM files with hex editors. I'm no stranger to writing utilities to extract meaningful data from binary blobs, even without the source code to the official blob generating utility... But real source code is very helpful and saves lots of time on reverse engineering and block-box testing efforts.