DPCM Doesn't play when playing exported .nsf

[DarkZapOTron]

I exported all .NSF versions you can export from Dn-FamiTracker, and none of them played DPCM at all. However when I exported from the original FamiTracker DPCM played fine. Just in case it helps, the song I was playing uses DPCM and Namco-163.

[Gumball2415]

what version of DnFT did you use to export the .nsf? also, may you provide a test module for debugging?

[DarkZapOTron]

I used version 0.5.1.1. Also, you mean test module as in .ftm?

[Gumball2415]

yes, the .ftm or .dnm file which can reproduce this bug

[DarkZapOTron]

https://drive.google.com/drive/folders/1_kpgxjX1AJwfaLGu04cFrLvWgovvFyLY?usp=sharing

[DarkZapOTron]

it sounds fine in Dn-Famitracker, the issue is just in the .nsf on the everdrive

[DarkZapOTron]

I created the song in the original FamiTracker from 2015, could that be the problem?

[Gumball2415]

it shouldn't be an issue. my current speculation is that it has to do with either DnFT's driver or NSF compiler.

[DarkZapOTron]

Yeah, it's probably one of those. Also, I just checked the .nsf on an .nsf player and it had the same issue.

[DarkZapOTron]

Thanks for helping figure out the issue could be!

[Gumball2415]

the NSF driver is partially compiled to a kernel binary "shell" (or "glob" as i've called it) in a header file.

the caveat with this is that compile-time definitions are fixed, especially for the amount of N163 channels; this is set to eight channels.

in 0CC, this was simply patched by writing a single byte to the identity table wherever the DPCM channel was indexed, but this breaks whenever the driver changes or is updated due to being a fixed address.

https://github.com/Dn-Programming-Core-Management/Dn-FamiTracker/blob/02b40e91c5b6c03c4927e8ec1630dc09b7e28528/Source/Compiler.cpp#L852C1-L854C3

indeed, when the driver was modified/patched in Dn 0.5, this patching was liable to break sooner or later.