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
I noticed the NSFs I've created with FamiTracker seem to have a problem with the NSF2Midi, the Triangle channel comes out sounding like the channel's whole frame is full of the same note. I created a test NSF with only one single note (see Z sample) in the channel and it sounds terrible in the NSF2Midi (listen to the X sample). "Regular" NSFs sound normal and don't have the same issue (listen to the Y sample). Now this isn't a major flaw but I'm wondering whether this could be somehow fixed via FamiTracker (or if FamiTracker has some sort of flaw) or if it is NSF2Midi's fault.
Oh, and hello to you.
Edit: Methinks I put this up in the wrong section, not sure if this qualifies as a bug or anything. You only live once though so I'm gonna take a chance and bet on 83!
I actually just tried this right before reading this, and I'm having this same problem too.
I wanted to hear one of the songs I made in Midi form :P, but the triangle channel just doesn't come through...
It's the same with S3M2NSF actually, if you convert any of those NSF's the triangle will have the same result.
There really isn't any way to fix it short of re-coding the way FamiTracker handles the Triangle. It's almost as if the Triangle is being reinitialized every single frame, and since the way the tones sound when the tone plays the same note after each other (it blends everything into one long note) it only makes sense, especially since the Triangle can be timed. To get tracker-specific results, you'd probably have to reinitialize the tone every frame to get the proper results.
Only thing you can do is erase the Triangle track in your midi sequencer and simply re-compose it. That could be a problem if you've got a song like Megaman with tons of Triangle tom sounds.
