EZNSF tool for building NES ROM from NSF

This is an archive of a topic from NESdev BBS, taken in mid-October 2019 before a server upgrade.
View original topic
EZNSF tool for building NES ROM from NSF
by on (#184032)
I had a really bad bout of insomnia over the weekend, so I decided to get around to making a tool that I'd promised a long time ago.

EZNSF is intended to make it easy to turn an NSF into a ROM you can play in an emulator or on a flash cart, etc.

Basically just make an NSF with Famitracker, edit a little album description text file, run the utility, and out pops a ROM. The default mapper is the newish Mapper 31, which makes NSF bankswitching possible to support. Several good emulators, as well as the Everdrive N8 now support mapper 31, but there is also an NROM output option for those that need it.

https://github.com/bbbradsmith/eznsf/releases/download/1.0/eznsf.zip
https://github.com/bbbradsmith/eznsf

There's a lot more explanation in the readme file. Everything's open source. It requires Python 3.


Edit: if you want to compile several NSFs into one album, there is a more advanced counterpart of this project called ZENSF.
Re: EZNSF tool for building NES ROM from NSF
by on (#186398)
I'm sure I'll be using this a lot when I get an Everdrive! In the thread with loopy's FDSStick you said you wanted to figure out how to build FDS files. I'm assuming since this doesn't support that you haven't been able to yet?
Re: EZNSF tool for building NES ROM from NSF
by on (#186400)
I can build FDS files, the problem isn't how to do it.

I hadn't really considered FDS support for this. It could be done, I suppose, but my primary target was mapper 31. The NROM option was an afterthought, but FDS could be supported in a similar way.

Anyhow, I'll think about doing it if I ever revisit this project, though higher on my to-do list would be writing a mapper 31 implementation for PowerPak. It would be lovely if someone got around to that for me, though. ;)