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
[quote=tadpole]Nope, it's not compressed. It's just a nsf that contains information on each track's name and length. I think that's the only difference.[/quote]
Cheers
_______________________
"All your base are belong to us"
The thing with NSFe is that many players don't support NSFe playback. I only know of Notso Fatso & FlashNSF that can play them back, but I know there's another one or two that can. The fact of the matter is that NSF files are more widely supported (in spite of their lack of convenient track information).
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
Other than this, is there anything else that makes the NSFe format more convenient or different compared to NSF?
I mean, since it also has similarities to NSF, would it take too much work to add NSFe support to any program?
_______________________
[color=#b0b0b0]This version of Dr. Mustache is outdated. Please download latest version [url=about:blank]here.
[url=https://www.dropbox.com/sh/md3lbsamcj39c9v/t0g5rFmzX_][Dropbox (my FT stuff)]
The only convenient thing about NSFe is pretty much track times and the ability to re-order tracks within an NSF.
In any other respect it is inferior to NSF (in terms of compatibility, file size, etc.). It won't even work with hardware players such as the PowerPak or the TNS HFC series.
_______________________
Follow me on [url=https://twitter.com/jrlepage2a03]Twitter.
I record (some) NSFs on hardware. Feel free to [url=http://www.famitracker.com/forum/posts.php?id=3633]request a hardware render.
_______________________
[color=#b0b0b0]This version of Dr. Mustache is outdated. Please download latest version [url=about:blank]here.
[url=https://www.dropbox.com/sh/md3lbsamcj39c9v/t0g5rFmzX_][Dropbox (my FT stuff)]
Aside from the support issue, there is nothing inferior about NSFe except the lack of engine speed feature. I think it's very much a superior format overall. The extra stuff:
- Track names
- Track times
- Fade times
- Playlist order
- Ripper name can be included
- Comments
- No 32-character limit for strings (and no unnecessary padding).
The file size differences are insignifican.
There is no hardware problem preventing NSFe support on TNS-HFC or PowerPak, they just haven't written the software to support it.
The removal of variable engine speed was done because no real NES games had this, and every single NSF rip has incorrect engine speeds (60Hz instead of the NES' 60.099Hz). Disch was hoping to correct this by removing the unnecessary feature.
Currently, the only editor for NSFe metadata is the NotSoFatso plugin for Winamp. (NotSoFatso was made by the inventor of NSFe, Disch.) You can use this plugin to convert NSFs to NSFe.
Dr_Mustache "would it take too much work to add NSFe support to any program", yes it probably would if you have to learn to program first.
The thing to remember is that NSF files are nothing more than iNES format ROMs with everything other than sound code removed. NSFe files are the exact same, other than the added features that tend to make the format incompatible with the iNES standard.
A great example of that last bit is what rainwarrior mentioned concerning the engine speed of NSF files being off (which is a result of the iNES specification itself being inconsistent). NSFe tries to correct most of the issues that the iNES specs got wrong, as far as I can tell, but that's beside the other peatures (like track listing, comments, removal of character limits, etc.) that would have broken compatibility with the iNES format anyways.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
The NSF format has nothing to do with iNES actually, it's entirely it's own format. And the reason speed is off is not because of iNES, but because that was the recommended speed setting from the NSF documentation.
_______________________
Follow me on [url=https://twitter.com/jrlepage2a03]Twitter.
I record (some) NSFs on hardware. Feel free to [url=http://www.famitracker.com/forum/posts.php?id=3633]request a hardware render.
) 
