Talk:NSF: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
No edit summary |
(NES 2.0) |
||
| Line 5: | Line 5: | ||
Yup, I assigned mapper 256, since iNES cannot assign it. And yes, it's required a player (I wrote my own in asm) and commands to switch tracks, but that's all. Perhaps I wasn't crystal clear... :( --[[User:Zepper|Zepper]] 14:31, 30 March 2012 (PDT) | Yup, I assigned mapper 256, since iNES cannot assign it. And yes, it's required a player (I wrote my own in asm) and commands to switch tracks, but that's all. Perhaps I wasn't crystal clear... :( --[[User:Zepper|Zepper]] 14:31, 30 March 2012 (PDT) | ||
:[[NES 2.0]] can assign mappers up to $FFF.F. Yes, that's a [[wikipedia:radix point|hexadecimal point]], used to separate the mapper number from the variant number. No variants are officially assigned though. --[[User:Tepples|Tepples]] 15:00, 30 March 2012 (PDT) | |||
Revision as of 22:00, 30 March 2012
A NSF tune is perfectly playable in an emulator; in short words, a "normal" NES emulator, not something clipped for exclusive NSF playing and behaviour.
Regarding 4015h, well... it's empirical. My experience says that setting 4015h to 0Fh is required in order to get *a lot of* tunes starting playing. I don't remember of *any* broken tune by setting such value. So, it's recommended *to follow* such thing. --Zepper 14:25, 29 March 2012 (PDT)
- Adding NSF support involves a mapper, an executable format, and a piece of shell code to draw the title, artist, and publisher, run the player in a loop, and switch tracks. But you're right that an emulator incapable of playing NSF is incapable of emulating something that runs on an NES, as the PowerPak has an NSF player. --Tepples 20:29, 29 March 2012 (PDT)
Yup, I assigned mapper 256, since iNES cannot assign it. And yes, it's required a player (I wrote my own in asm) and commands to switch tracks, but that's all. Perhaps I wasn't crystal clear... :( --Zepper 14:31, 30 March 2012 (PDT)
- NES 2.0 can assign mappers up to $FFF.F. Yes, that's a hexadecimal point, used to separate the mapper number from the variant number. No variants are officially assigned though. --Tepples 15:00, 30 March 2012 (PDT)
