You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NSF version 2 specifies the total length in bytes of the program section. This allows NSFe chunks (see issues #39 and #40) to follow it. All chunks but INFO, DATA, and BANK should be copied to the NSFe metadata area. The header should be built from INFO, BANK, and auth if present.
NSFPlay maintainer Brad Smith wrote a tool nsfe_to_nsf2.py to turn an NSFe file into an equivalent NSF2 file with NSFe data. In channel #development of the FamiTracker.org Discord server, he released it under what amounts to the WTFPL:
<rainwarrior> do whatever you want with it
The text was updated successfully, but these errors were encountered:
Do most of #41. If NSF2 is enabled, write the length of the
program, increment the version number, and write most NSFe chunks
after the program. Waiting for rainwarrior to help troubleshoot
why Dendy rate is so messed up.
NSFPlay beta correctly plays NSF2 and shows metadata the same as it does for NSFe.
(A recent commit message mentions errors with the displayed Dendy rate. These turned out to be only cosmetic, and even changing tracks caused it to clear up.)
NSF version 2 specifies the total length in bytes of the program section. This allows NSFe chunks (see issues #39 and #40) to follow it. All chunks but
INFO
,DATA
, andBANK
should be copied to the NSFe metadata area. The header should be built fromINFO
,BANK
, andauth
if present.NSFPlay maintainer Brad Smith wrote a tool
nsfe_to_nsf2.py
to turn an NSFe file into an equivalent NSF2 file with NSFe data. In channel #development of the FamiTracker.org Discord server, he released it under what amounts to the WTFPL:The text was updated successfully, but these errors were encountered: