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
When bankswitching will be truly available? 'cause I'm using [b]lot[/b] of bass samples (22 samples for 16310 bytes!) and I cannot use them all because the music data size limit is then exeeded, and suggest me to bankswitching it...
Looking forward to seeing the next one released! Couple of questions:
1) Is there an updates/changes-log inside FamiTracker itself? I couldn't find anything. If not, and that information is only put on the website when each version is properly released, then...
2) Is there a possibility that the things you're working on/new features to the WIP version could be listed in this thread? Or would that ruin the surprise?
Basically because I've downloaded the WIP version and I don't know/can't tell what's different from the current version :P.
And, seeing as I'm posting, I may aswell make a few general comments. Ace program! It didn't take me long to learn, and I'm enjoying using it a whole lot. Pleeeease please keep working on this, I'm really looking forward to seeing it progress and add more functionality.
Here is a stupid (read : simple) fix you may do before releasing the new wip!!! I even spotted the problem just to explain how it is simple
Hxx and Ixx commands work well but something is special about it, the first parameter ( H[u]x[/u]x and I[u]x[/u]x ) does the same thing in Famitracker and on NSF. But when you set it to "1" however, in Famitracker it does the same thing as if you set it to "0" and on NSF the sweep is slower than on Famitracker, as if in Famitracker you have set it to "2" and it is valid to all greater values. It may be confusing the way I say it but in short it is a simple incrementing problem when converting to NSF ( or replay in Famitracker )
Anyway, test it yourself if I'm not self-explanatory!
And, perhaps an even simpler little fix, which you or anyone else may have already picked up on (it is largely inconsequential anyway), is that when you go to close the program, it asks if you wish to save even if you have just saved and made no further changes.
Jarhmander: I found the problem of DPCM samples, but the NSF compiler was correct. The real problem is that samples can only be stored at certain aligned addresses in NSFs, and using samples that doesn't exactly fit into those will waste some extra space in NSF files.
Normally this isn't a problem, but in this case where 21 samples was used and also filled the whole space, it overflowed the NSF sample area and made the way the tracker stored the samples a shortage.
The way to attack this would simply be to calculate how much space samples would actually waste in NSFs. I'll add it to avoid this kind of problems.
I also made some adjustments to the Ixx & Hxx commands. But make sure not to use my NSF player for testing, is the sweep code is a little inaccurate.
Dave: I don't have much to hide. =)
I've been working on improving the keyboard editing and will keep doing so.
Other things are expansion chips, but it's progressing slowly as I'm rewriting the NSF driver code.
I often use "Step 2 or Step 4" while composing, but now since the arrowkeys jumps the same steps I can't navigate with the arrowkeys, without changing steps... Please let us (that wants to) use arrowkeys with step 1 while step is set to another value!
Now I have to try it some more! Thanks for the update!
