I've encountered a really weird glitch just now...It might not be a problem with Famitracker, but it probably is.
I have .ftm module (4-channel N163) that contains 40 songs (mostly sound effects though) and everything has been working just fine up until now. In the exported nsf file, one of the songs randomly ends in the middle of a frame that had a D00 effect on row F (don't know if D00 caused the glitch) and it jumps to garbage noise notes, or continues on with only playing the triangle and pulse 1 before finally stopping.
Is this because I've reached a size limit in either .ftm or .nsf size? (the .nsf is 75,3kB)
If you want to take a look at the ftm or the nsf files I'm going to PM you.
I've found a bug with the sample editor! When I try to delete the first part of a wave, FT somehow duplicates the part after my selection instead. The first image shows me selecting the blank part of the sample and the second one is the result after deleting the selected section.
I've noticed that if you hold the horizontal scroll bar while playing a song that changes its BPM somewhere(Fxx effect), it doesn't update in the status bar. It's not a major issue, but i found it curious.
While I was playing betasword's DoX covers in v0.4.1 I got a crash and it posted a MiniDump.dmp file. However, since I just downloaded the FTM into Firefox's cache it appears that it was not created or named properly. I searched for other MiniDump.dmp's but none matched today's date. To make this easier I propose a couple things:
1.) All minidump.dmp files be put into a FamiTracker subdirectory "minidump" with naming scheme similar to minidump_famitrackerversion_filenamewithoutextension_mmddyyyyhhhh.dmp
2.) An option that auto-purges minidump files 3 months and older.
3.) Perhaps even an error-reporting service that uploads the minidump to you. Server-side you can ignore all non-current minidumps.
I would have made a thread for this, but it appears that I do not have such a privilege currently. What assholish thing did I do this time, praytell?
That sounds strange, maybe it didn't have the rights to create a dump file in the cache folder or something? Anyway, adding some sort of timestamp would be a good idea to easier identify files, so I think I'll do that. Information about the version etc is available inside the dump file at the moment. And an automatic service would be nice, but it would take some effort to add and I think the current way works good enough, and sometimes it's necessary to follow up with questions regarding the crash.
I don't know why your permissions was gone, but I've restored them.
Bizarre... Checked my timestamp and everything. Weird shit is going on with my computer these days. I've taken advantage of Black Friday deals today and bought myself some new PC parts to build a new one. Finally gonna upgrade to Windows 7 as well. Might install Linux first and do a GRUB bootloader so I can have Windows XP as well for my parallel CopyNES.
I found a bug while trying to work around an emulated one, and found another while trying to make a file to report this bug.
(this is the file to compare these to. just mute all but channels 5 and 6)
The first bug is a bend issue when using an arpeggio macro in your instrument. I tried to force an instrument down an octave to hear the difference without transposing everything with that instrument down an octave, and I heard stuff like this. In this exact example I changed it from a sharper saw-like wave to an organ-like wave by just changing from 16 to 32 samples, and wanted it to stay the same pitch, so I also added a +12 arpeggio macro to the instrument.
Second bug didn't apply to the generated ftm... it was just in the instance. I copied the melody and echo from the original module and, instead of playing the two channels separately, it only played the echo channel, but in both channels.
_______________________
I've posted what I came back to post. I feel accomplished.
I'm getting a weird bug where the first N163 channel plays really quiet, tinny sounds instead of the wave I want it to play. It doesn't play sound in jam mode either. The same bug is present no matter how many channels are enabled. All other channels sound fine though.
The ftm actually plays fine for me...but I know about this bug, it happens to me every so often as well, with the exception of Namco 1 being completely silent rather than just very quiet.