So as of the latest DN-Famitracker update

, apparently some fixes have been made to the .nsf driver.

I'm in the process of testing it myself and it seems we can finally move to v5 now as the .nsf driver is working properly. Obviously it loses backwards compatibility with 0CC-FT and whatnot, but it seems that this version fixed the issues with .nsf exporting.

If anyone else is testing and has found this isn't true, please let me know in this thread as I was planning on updating the Lyceum page sometime this week. Still, this could be pretty important and useful if it does work properly.

i have had issues with it still, note releases do work fine for me now but the 1st note in the noise channel cuts off for me now, can post a comparison in the discord (not sure what other issues there are since i didn't look that far)

this feels like the bad time to mention ive been using dn-famitracker this entire time for my nsf entries, completely unaware there's been any issues with its nsf driver [and i still haven't updated my dn-famitracker]

>Arceus
Thanks for the info. It seems to be working okay on my end but that could be an issue.

>dsm5
haha, it's not that big of a deal. Version 0.5-on have had notable issues with nsf exporting. If you're using 0.4 or older you should be fine. Also, it's only minor things usually. Often nothing happens.

interesting. i still have some issues exporting multi-expansion modules that do export properly from 0.4.0.1, but there is better logging about this now (and perhaps there are other logistical reasons that the export works in that version but not this one):

Error: Instrument, frame & pattern data can't fit within bank allocation, can't export file!
* $323C bytes used out of $3000 allowed

it's a new version though that seems to be trying to clean up any mess, so it's definitely worth continuing to test!

so for that it looks to me like the file you tried to convert was too big, but i could be wrong

yes, it used to say "instrument data overflow" when this happened and nothing else, though the point gets across in both cases i think. my point is that these modules export fine in 0.4.0.1 or earlier, meaning whatever changed somehow balloons the size of the same data.

@dsm5: there are problems only if you are using expansion chips, nsf export for songs using only the 2A03 chip works fine on 0.5.0.0, 0.5.0.1 and 0.5.0.2! I didn't try 0.5.1.0 yet so I don't know if it's still the case for this one...

im using 0.5.0.2, so either way im gonna give updating a shot (i know for a fact i've submitted to expansion chip battols before, but i don't believe it's been many)