Here's another one for you: double-clicking an instrument to open the instrument window during playback sometimes (but not always) causes that instrument to stop playing until playback is stopped then resumed. I can't say for sure whether it's the channel where the cursor is located or just the instrument, nor can I seem to get it to happen all the time... But I thought I'd bring it up.
Oh something related to that...Sometimes FDS instrument test plays the default wave even if I alter it or simply choose a preset waveform, it still plays the default waveform.
It didn't give me a crash report from Famitracker, it froze and stopped responding, and I had to kill the process with Task Manager, anything specific though I should look for?
_______________________
B00daW wrote: Memes are are like cheese; perishable.
Follow me on SoundCloud! http://soundcloud.com/thislinkisnttaken
Ok then I get it, no crash file is generated unless it actually crashes and displays the crash dialog. This problem is known however, Famitracker can hang under some situations when changing expansion chip. I found this problem after 0.4.1 was released but is now fixed.
It's possible to trick famitracker into thinking a key is held down when it's not with auto-arpeggiation on. Do this:
1) turn on auto-arpeggiation
2) Go to noise and hold down a key that plays a pitch
3) Click on the DPCM column while holding down that key
4) Now go back to noise and press other keys. Even though you are only holding down one you will get arpeggiation
5) To end the glitch, press the key you pressed originally
i confirm this, altought i didnt know how to get this glitch done. sometimes, when I ran famitracker, it made auto-arpeggiation and i was holding only one key. or maybe i just didnt notice that i did the same thing you said.
i confirm this, altought i didnt know how to get this glitch done. sometimes, when I ran famitracker, it made auto-arpeggiation and i was holding only one key. or maybe i just didnt notice that i did the same thing you said.
I would not be surprised if there's more than one way to do the glitch, since it requires the program to realize the key gets pressed but forget to process its release.
I got a funny error message: "Failed to save file: The operation completed successfully." When I clicked save as, went to a different dropbox directory, selected a new name, saved it then quickly after saved again.
This file ends with a D03 command on row 002, something that used to be a problem in the tracker in 0.3.x but exported to NSF fine. Now it seems the reverse is happening: it works correctly in the tracker, but the NSF is broken. Here is the resulting NSF.
