NSF Import Support (suggestion)

[TheHiddenTotemPole]

I really wish there was NSF (Nintendo Sound Files) support too make it a lot easier to remix those old NES soundtracks without needing to source out a midi sound file so use the pain process of listening to parts of the song and finding out which notes matches. I feel as though this is properly a pointless or too demanding feature to add...

[Epictyphlosion]

I think something like .ftm or .occ import would be a bit more reasonable. Importing an NSF file would be like a register dump; a long, very fast module with lots of empty space.

[H4shtagInclude]

I agree with you, it would be a lot better to have famitracker file or midi file support rather then a sound data format like vgm or nsf.

[Accuracy-Matters]

I on the other hand would like to see NSF/VGM importing in the form of a "high speed register dump"
For my purposes, NSF import for FamiTracker was already extremely useful for not only learning how the target track works for covers but also allowed me to do register-accurate "ports" of tracks
If Furnace could get this feature that spans across numerous systems I would be unbelievably happy
(It would also make ripping instruments, samples, patches etc. from a variety of sources way easier)

[H4shtagInclude]

Yes! It would make Furnace the definitive music tracker for all retro video game consoles and computers .

[Epictyphlosion]

@Accuracy-Matters Fair enough. I know the n163import tool only imports the first two minutes of music, which is annoying considering that it can import expansion audio while NSFimport can't. Plus it's interesting to import actual game soundtracks to see what techniques they used and learn from them.

[NARFNra]

Yeah, as Accuracy-Matters mentions this actually was supported by a specific version of Famitracker made at one point, if you just wanted a register dump so you could see exactly what a song was doing at a specific time. I think it would definitely be nice to see this supported for more systems and by a more modern program, but I thought I'd mention it for anyone who might be unaware.

[Accuracy-Matters]

Said version of FamiTracker is fairly old now, and there's a few specific things that weren't emulated in FamiTracker at the time
For example, triangle length, hardware length counter and hardware decay/retrigger envelopes weren't implemented in vanilla FamiTracker but are present in forks
So NSF Import opts to approximate these effects which leads to problems (and requires visually studying registers in programs like NSFPlay, which can be time consuming depending on the soundtrack), since Furnace has a much higher effect channel limit it can do much better in the way of register-accurate imports