Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
FamiTracker
[color=#555555]I noticed this problem with this tune I was making. I don't know if it's my methods or what, but — when trying to play an NSF that contains (used or not) any DPCM samples after exporting it with the 0.2.7 W.I.P. that also has the .NES export feature, it refuses to play.
I've tested the attached NSF with FCEU, NotSoFatso, and Nestopia. It doesn't work in any of them.
Oddly enough, exporting my song to NES format seems to let it play without error in Nestopia and FCEU. ¯\(º_O)/¯
Deleting all DPCM samples from the file and exporting the NSF as usual seems to fix this problem.
I haven't tested the stable 0.2.7 release, unfortunately. I'm not sure, but I don't think it would happen.
EDIT: well, since the above bug has been fixed in recent WIPs, I believe I shall hijack my own thread and post about a different possibly-bug.
This one's been around since 0.2.3b at least, possibly earlier -- basically, the [b][[/b] and [b]][/b] keys play incorrect notes in FamiTracker. On my keyboard, pressing [b]P [ ][/b] (in that order, using the default octave) should result in E-5, F-5 and G-5 appearing in the pattern editor. What shows up instead is E-5, F#5, F-5.
I know I'm being nit-picky here, but if you rearranged they notes so that F-5 was on [b][[/b] and F#5 was on [b]=[/b], then you could add a G-5 to the [b]][/b] key!
There's currently no note on the [b]=[/b] key, even though it SHOULD be the next black note on my (typing) keyboard. Like I said, though, this is only a possibly-bug, meaning that it most likely only really affects QWERTY keyboards.
Any chance you could consider submitting this cosmetic change to FT's functionality, though?
RE: Bug: NSF exported with DPCM samples will not Posted: 2008-08-30 12:02 (Last Edited: 2008-09-22 21:26)
[color=#555555]Just tried 0.2.7 (not the bugfixed version, the stable release from the Downloads page) — it plays now. Apparently, something happened between one of the betas that I'm using — whichever was one of the first to be able to export a .NES file — and the original 0.2.7 to cause this bug. [i]I[/i] still no clue what's causing it, but hopefully this'll help. :D
