There is no skipping. There is a quirk of the key redefine system that you have to release a previous key before pressing a new one, otherwise new one will be counted as the previous one.
Key redefine was a major headache by itself, I'm not plannig to touch it anytime soon.
I can confirm that this is an issue, and it doesn't have to do with releasing the key before pressing another. Sometimes if I track too fast, the program repeats previous input (even if no other key is pressed) and I have to undo that before I carry on. At least I'm guessing that's what Raijin was referring to, and if that is the case, fixing that would be very appreciated indeed.
Yeah jrlepage, that's what I meant. The tracker skips input and repeats notes (even though Shiru said it doesn't skip, it sure does a good job acting like it), but I think that also has to do with what Shiru explained. Judging on what he said though, I guess he'll mess with it whenever he feels motivated enough.
I don't know what happened...but my instruments don't make sound over octave 5 when I press keys in the pattern editor. I can play them back just fine and they work propely in the instrument editor as well. I'm not Beethoven writing music being completely deaf.
Just a short and noobish question? Is it technically possible to create a triangle-ish wave somehow? I've been trying for a long time, but I've only managed to make a sawtooth a square and the closest I've ever gotten was something like an octagon chopped in half...
Quick question. When using the "CH3" noise, and adjust the pitch with square 3, after adjusting the pitch, it doesn't seem to be possible to go back to the original high pitch sound of the "CH3" note. Is this how the SN76489 works?
Also, do you think an option for crash dumps would be useful for you to fix bugs in the future?
The crash dump would generate a file when the program crashes and you would be able to see exactly where a problem is. I thought it would help you fix bugs easier or something, maybe. Though if you don't think so, then I guessed wrong.
I still have no clue how the crash dump would work. Obviously only the program itself knows its own state, so it have to save it, but how can a program detect that it crashed and save own state, being crashed already?
Even if there would be a wonderful crash dump that would show me exact place in my code where the crash happened, if I'm not able to reproduce the crash on my system, I would not able to fix it - i.e. I can't test if my changes fix the problem.
Sorry, unfortunately I am not knowledgeable with programming so I couldn't explain. If you are interested, jsr does it with Famitracker, so he would have an easier time explaining. I am sure he could explain in detail if you ask. Maybe even Delek and rainwarrior would know.
Is it possible to test these kind of things with a virtual machine of sorts?
