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
It may seem odd, but after looking at the asm export from Famitracker,
it handed me 5 channels, plus DPCM samples.
I'm a little confused because the channels are not matching up to the actual tracks.
The regular sound channels are $4000, $4004, $4008, and $400C
but I don't know which co channels in the ASDM go to which channel.
Famitracker handed me the channels that I attached in a picture, but NES-wise, I only had channels 0, 1, 3, and DPCM active:
I'm not sure why it handed me 5 sound channels, but how do we feed the bytes through the channels?
For channel 0, do we hand the bytes to it like this?
$4000 byte 1, $4001 byte2, $4003 byte3, $4004 byte4 and then loop it again?
Its a little confusing because they don't have documentation on it. Maybe in the next release the author of this program can add comments in the exports to let us know what to do with the binary data.
As far as the ASM export goes, I don't think it's correct because NES only has 4 sound channels, but the export gave 5 audio channels and mixed up the data sequence between the channels.
alright, what is the byte sequence in the binary exports?
what NES channels do the bytes go to from the binary export?
What is the byte order of the bytes in the .bin exports?
Do they have a set sequence.
What is the syntax of the bytes?
I'm wondering how it is encoding them but I can't find documentation on how to decode the bytes from teh binary export.
I started different topics because the questions spanned over different topics so maybe it could help others find what they're looking for because I know 100% by fact this is something 11 million programmers are asking Famitracker about.
What is the byte sequence the binary export is writing the bytes in?
Simple question, but not even the author of Famitracker knows. I checked NESDEV but they're not quite covering the $4000 register with using Famitracker binary or NSF exports.
Gamecube is easier to program than the NES. Famitracker is more or less for PC only it seems. They should make it compatible with 6502 instead of making a new PC based language format inventing additional channels and what not.
There is no documentation for how to translate Famitracker's binary music data into APU register writes. That would actually be kind of ridiculous to write a specification for. The NSF driver does this translation, and it's what you need to use for this purpose.
PatternCompiler.cpp contains some comments describing some of the binary format, but this only tells you how the Famitracker pattern data turns into the binary data. This is not particularly useful for playing the data back on the NES.
The thing that translates famitracker binarty data into register writes is the [url=http://famitracker.com/downloads.php]NSF driver program. This program compiles with ca65 and can be integrated into an NES program. I've already linked you to [url=http://famitracker.com/forum/posts.php?page=1&id=3681]this guide on how to do this.
There is no "new PC based language format", nor are there any "invented" additional channels. The NSFs produced by Famitracker can and do run fine on an NES (I don't want to say 6502, because the NES is more than just a 6502, and the additional features are strictly relevant to playing audio).
