-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New *.nsf-export algorithm question/bug? #242
Comments
as of this time of writing, no version of FT or any FT fork supports Dendy mode. can you clarify whether your exported NSFs are NTSC-headered or Dual region headered? FT has options to export NTSC, PAL, or both, with the NSF player discerning which one to use. |
I've generated NSFs from FTM-file (look at archive) manually, it's NTSC headered. |
can you also clarify on this? on my build of Mesen2, the tempo and pitch slows down as expected. |
... i see the problem with NSF export on PAL see issue #223 for details. |
I have lastest Mesen2 autobuild. |
punesemu/puNES#346 |
yes, it's an issue with the PAL play rate not being set correctly, as seen in #223.
This means that PAL and Dendy NSFs play at the erroneous 60Hz rate that Dn-FT exports. This is a planned fix in PR #214. |
as for puNES, i don't think it's within Dn-FT's jurisdiction to fix an external emulator's implementation. |
Thank you |
Hi! I need to ask you about new NSF-export algorithm, maybe you can help me.
Classic versions of Famitracker and 0cc-Famitracker generate standart *.nsf-file, NTSC-headered.
If you play it on emulator in PAL or Dendy mode - tempo will slowing down, and this is absolutely normal.
But new version of DN-famitracker does something strange.
It also generates standard.nsf-file, NTSC headered, but it:
Maybe you know what's really happened in the new NSF-export algorhitms or it's general DN-Famitracker bug?
nsf_test.zip
The text was updated successfully, but these errors were encountered: