NSF has never had a Dendy spec. 2 is "undefined behaviour"... however...Sour wrote:It looks like I broke this a long time ago when fixing the playback speed when Dendy timings are selected. Haven't fixed it just yet since I was wondering, what should this return for Dendy timings? Would returning 1 like for PAL be good enough? Or would it make more sense to have another value for Dendy (e.g X = 2)?rainwarrior wrote:One more thing about NSFs: if using PAL region the INIT should have 1 passed for X, not 0.
I did actually decide yesterday that I should add a nes NSFe chunk to address this:
If unspecified, I think "normal" expected Dendy behaviour is X=0 but use PAL speed. (i.e. NTSC version of tunes played too slowly). That's really what most Dendy games would do.
(Most NSF rips are single platform only and ignore X as a parameter anyway. With homebrew, especially Famitracker, X does often matter, though, and there an unexpected X=2 may cause problems. Better to use X=0 by default there than throw something new they weren't written for.)
The added NSFe chunk will accomodate stuff made specifically for Dendy, though, in which case if that's specified pass X=2.