This has been bothering me for a long time, but now that I'm supposed to make an OST for a game,
it's getting really tedious that when I export my song to .nsf to record it without N163
aliasing noise (because it still lowers the quality slightly even with 4 channels) and correct DPCM
volume, about 90% of the time I get a glitchy .nsf with the N163 channels using wrong instruments
sometimes. (the problem is NOT me failing to arrange waves correctly in the RAM)
Maybe waves aren't arranged correctly in the .nsf files because when it's supposed to switch from an
instrument that is at 96-128 to one that is at 0-31, it switches to a wave that's not in any instrument
in the module (so it probably overwrites something wrong by accident).
The weird thing is, that after the first frame with wrong waves, it fixes itself in the next one.
I really hope this will be fixed soon, because it's very unreliable at the moment.
It's good that you're finding bugs, but if you need to get an OST done, I'm wondering why you chose the N163 beta? Why not use something more capable like Schism/Modplug/Milky Tracker? In a regular tracker you can do all the same stuff as the N163, but without any of its problems. (Also they're not in beta, they're finished and ready.)
