In this thread, if I find a bug that still exist from the ealier beta, what can I do about it? Should I still mention it, or what? Things are trying to be kept organized, so thats why I'm asking. If I can mention it, there is another bug that I've run into, recently. Thanks in advance.
I've found that when using the instrument editor, if you try to enter in values for any of the fields other than volume envelope first it will put those values in the volume envelope instead of the one you selected.
So if it does not help, then do not help, otherwise everyone will be creating posts like:
'Then make DPCM samples bigger than 79 bytes before loading them in the DPCM editor.'
'Then do not set the custom engine speed to 25Hz.' (this one is from 0.3.5.)
'Then do not use Yxxs in order to avoid 'bleeding' between samples.'
OK, here's the bug that's still present in this version(Note Release bug):
On a new module, When I create an instrument with note release, and I try entering a note into the pattern editor using that instrument, the note plays indefinitely after I've pressed the key. This also happens if I just press a key on the keyboard in the instrument editor.
It sounds as if the the volume gets stuck at the beginning of the release point setting in the sequence editor, and doesn't go past that. A semi-detailed example:
The note, when entered, will continue to play the note at volume 7, where the release point begins. It will not go pass this and fade out. This will happen, up until you play the song you are composing. The note will finally stop playing. This happens all over again when you enter a new note. Everything plays as it is supposed to when playing the song.
This has happened before in the 0.3.5 BETA, and I think I've mentioned it last time, too.
Qxy and Rxy misbehave on the disk system channel. on 2A03 channels they're toggled (ie. you don't need to turn them off, they're required for every use), on the FDS channel they're held (doesn't switch off automatically, WOULD need to be switched off manually EXCEPT that R00/Q00 doesn't really turn it off... the only way it turns off currently is with a notestop)
i can create an example file later, i'm just posting this now before i forget.
My point is that there is no reason to repeatedly press F12 during playback.
Bugs do not have reasonabilities.
Plus there are times when the module is very fast or it is very complicated (say, a VRC7 cover at 900BPM with all 11 channels extended to fx4), and the computer is utterly slow, then it is reasonable.
My point is that there is no reason to repeatedly press F12 during playback.
Bugs do not have reasonabilities.
Okay then, can you fix the bug where it hurts if I break a bone? My point is that if it only occurs under abnormal conditions induced by the user, then the simple solution is to not cause those abnormal conditions.
_______________________
If there is evil in this world, it lurks in the hearts of man.
--Trinicus D. Morrison
The Final Fantasy IX 8-bit project: 3 complete
http://famitracker.shoodot.net/forum/posts.php?id=1624
Okay then, can you fix the bug where it hurts if I break a bone? My point is that if it only occurs under abnormal conditions induced by the user, then the simple solution is to not cause those abnormal conditions.
If it is a bug, then there is no reason to not fix it.
BETA 3 BUG: When i close Famitracker Beta 3, famitracker crash and a debugger window of Visual Studio 2008 pops up.
EDIT: I was modifying the registry entries of famitracker, i think that those modifications causes the crash; i restore the registry with a backup and works fine for now.
.png){kind=avatar}
