I tried to convert one of Blitz Lunar's NSFs and the DPCM gets all wacky, I get some that are the last part of one sample and the first half of another, and stuff like that.
It sounds like it's using bank switching, which FamiTracker doesn't actually support. (It's highly unlikely that any real NES game would bank switch DPCM samples mid-track, so I guess it hasn't come up.)
I should probably detect for bankswitching, though and at least prevent it from posting DPCM events from the wrong bank.
i'm pretty it's bankswitching as well, it's the same way how xamius did one of his fcm7 entries where it was mostly dpcm. i think jsr said he was thinking about implementing it awhile ago, my memory might be wrong though.
Forgot to respond about Skate or Die track 2, though the answer was already given: it's raw PCM. You can tell by the random looking Zxx events. (Alternatively, if you play in NSFPlug, you can see the DPCM channel volume fluctuating.)
If you want to rip those sounds, you can just make a WAV recording of just that channel, I guess.
i'm pretty [sure] it's bankswitching as well, it's the same way how xamius did one of his fcm7 entries where it was mostly dpcm. i think jsr said he was thinking about implementing it awhile ago, my memory might be wrong though.
Are you referring to Haxus? I'm pretty sure that was done in SuperNSF, and that it used raw PCM and not DPCM... :o
Forgot to respond about Skate or Die track 2, though the answer was already given: it's raw PCM. You can tell by the random looking Zxx events. (Alternatively, if you play in NSFPlug, you can see the DPCM channel volume fluctuating.)
If you want to rip those sounds, you can just make a WAV recording of just that channel, I guess.
Ah, okay. I understand what's going on now.
_______________________
Everything moves real slow when it's 40 below.
Oh, that's cool. Umm, I'm going to revise the "Valid NSF Files" section, since they still will import as much as they can. The NSF files themselves are valid, but certain features might be called "invalid". I'd probably call this section "limitations", and I wouldn't say that they "must not contain" these things (because they will still import if the do). There is a list of limitations in NSFImporter.txt.