1
MilkyTracker Bug Reports / Minor glitches in Space-debris and ascent.s3m
« on: December 05, 2009, 23:33:05 »
Okay, here goes;
In ascent.s3m, every now and then when there is a porta-to note, usually a series of 300 (following a 302 or something like that) it exaggerates the portamento effect (strangely, not on the echo track though). Even more weirdly, when I playback the pattern to double-check, it plays it fine... but then the problem recurs on the next pattern or two. This happens quite a lot in ascent.s3m.
Space-debris:
Pattern 1B(21) and 1C(20); start playing from 1B so you can get the lead-in correctly, and something weird goes on. I'm not entirely sure what is going on here, because the channel in error is #3, which is playing sample 11. In my copy, sample 11 is extremely short (a4 bytes) yet the tracker is using command 934 which is an extremely large offset. Some double-checking is in order here, so just take this as an FYI.
In ascent.s3m, every now and then when there is a porta-to note, usually a series of 300 (following a 302 or something like that) it exaggerates the portamento effect (strangely, not on the echo track though). Even more weirdly, when I playback the pattern to double-check, it plays it fine... but then the problem recurs on the next pattern or two. This happens quite a lot in ascent.s3m.
Space-debris:
Pattern 1B(21) and 1C(20); start playing from 1B so you can get the lead-in correctly, and something weird goes on. I'm not entirely sure what is going on here, because the channel in error is #3, which is playing sample 11. In my copy, sample 11 is extremely short (a4 bytes) yet the tracker is using command 934 which is an extremely large offset. Some double-checking is in order here, so just take this as an FYI.