Speed 1 @ 60Hz is:
60 updates per second
1 update per row
so 60 rows per second
60 seconds a minute
3600 rows per minute / 4 rows per beat = 900 beats per second
So Speed 6 @ 60Hz is:
60 updates per second
6 updates per row
so 10 rows per second
60 seconds a minute
600 rows per minute / 4 rows per beat = 150 beats per second
And Speed 6 @ 50Hz is:
50 updates per second
6 updates per row
so 50/6 rows per second
60 seconds a minute
500 rows per minute / 4 rows per beat = 125 beats per second
This is kind of messy, but ehh, if anyone cares, that's how you get the 2.5x thing.
_______________________
"im going to continue making this crazy stuff then after a while my style will be so sick that you will be like damn suuun that shit is so sick i dont even get it. i will be like bro its ok.. you dont have to." -omgdonut
Not seeing it, but it'd probably take too long to explain further.
Oh, here's one:
You know how when the frame editor has focus you can press Enter to start/stop playing?
When Follow mode is disabled, if you're currently playing the song, then click a different frame and press Enter it stops playing, when I would rather have it start playing from that frame (similar to what happens when Follow mode is enabled). However, you still need the ability for Enter to stop playing the song, which complicates matters....
Also, when Free Cursor mode is enabled, I would like if it didn't allow the cursor to scroll all the way to the top/bottom of the area -- i.e. give it a margin of 1 or 2 rows (beyond which you can see the next row in that direction).
There seems to be a bug with the release envelopes. Sometimes as I'm setting release commands in the pattern, I can hear the release envelope of my instrument again.
All keyboard shortcuts (e.g. F5 thru F8 - play/stop) only work when the control focus is on the Pattern editor, Frame editor, or Instrument editor. They do not work if the focus is on a textbox (such as song info) or dropdown list (such as song/octave select).
Some of these shortcuts (like Save) are things you expect to work from anywhere/everywhere on the window, regardless of control focus.
Yeah, as for dropdown lists, you also can't click on it, and then use the scroll wheel to quickly select dpcm pitch for example. I don't know if the removal of this feature was intentional or not, but it made testing dpcm samples for different pitches very easy.
In the Instrument editor, if I define an arpeggio (pitch, hi-pitch, duty, etc.) with a release sequence (e.g. / 0 12 absolute arpeggio) and start hitting notes on the editor to test how it sounds, nothing happens unless I have also defined a volume curve with a release sequence (it can't be just any volume curve; it must include a release sequence).
I haven't been able to reproduce this, in either 0.4.2 or 0.4.3
Stratelier wrote:
Oh, another quick one: in the View menu I have my Frame editor position set to "Left". Now if I toggle the Status bar on and off, the Frame editor (unlike the Pattern editor) does not resize to fit the new space (it may leave empty space below the horizontal scrollbar at the bottom, or cut that scrollbar off entirely). Resizing the window fixes it.
This is known but I don't know how to fix it so I'm leaving it for some while.
Stratelier wrote:
If I have my cursor positioned in the middle of a song (say, frame 05) and at row 00 of that frame, I'm in Follow mode and then I hit F5, the window doesn't repaint properly as the song starts playing: As the window scrolls upwards line by line, it retains remnants of the frame I was at instead of the one it's actually playing. And it only happens if I'm at row 00 of the current frame (any other row number, and when you hit F5 Famitracker repaints the entire window as it starts playing).
This will be fixed.
za909 wrote:
There seems to be a bug with the release envelopes. Sometimes as I'm setting release commands in the pattern, I can hear the release envelope of my instrument again.
Haven't seen this one either. Do you have an example file where it occurs?
There seems to be a bug with the release envelopes. Sometimes as I'm setting release commands in the pattern, I can hear the release envelope of my instrument again.
This happens to me too. There's no problem with the actual playback, it's a bug that only happens as you're placing the releases on the track.
I'm not sure if it's a bug, an intentional feature, or just unimplemented, but when using a MIDI keyboard with an instrument wiwhich has a release envelope, releasing a key doesn't trigger the release envelope like a computer keyboard does, it just cuts the note.
I've noticed this since I started using a MIDI keyboard. 0.3.7, I think.
EDIT: I hope that was worded correctly. My 5 AM grammar skills aren't usually this bad.
Also, I might've mentioned it before but while a song is playing, if you mute a channel it ignores any instrument/volume/effect changes that may occur while muted -- when you unmute the channel it plays using whatever instrument/volume/effects it had before muting. This is noticeable if you have a channel that alternates between instruments at times.
jsr wrote:
Stratelier wrote:
In the Instrument editor, if I define an arpeggio (pitch, hi-pitch, duty, etc.) with a release sequence (e.g. / 0 12 absolute arpeggio) and start hitting notes on the editor to test how it sounds, nothing happens unless I have also defined a volume curve with a release sequence (it can't be just any volume curve; it must include a release sequence).
I haven't been able to reproduce this, in either 0.4.2 or 0.4.3
To be more specific:
[tested against 0.4.3]
1 - Attached is a test file, examine the instrument.
2 - Notice the arpeggio and volume definitions; both include a release sequence. When you hit notes in the Instrument editor you can clearly hear them both in effect.
3 - Toggle the volume envelope off and start hitting notes again, now the arpeggio release sequence doesn't occur at all.
4 - (This only affects the Instrument editor; in an actual song the instrument plays as specified.)
jsr wrote:
za909 wrote:
There seems to be a bug with the release envelopes. Sometimes as I'm setting release commands in the pattern, I can hear the release envelope of my instrument again.
Haven't seen this one either. Do you have an example file where it occurs?
You know how when you add a note to a channel FamiTracker plays that note? It also plays cut/release commands. This can be an issue sometimes if you're editing a song while it's playing (in non-follow mode).
Oh, I just found an interesting one: If a channel contains multiple release commands in a row, any release sequences that have finished will not retrigger, but any release sequences that are still playing will. Is it supposed to be that way?
Also, I might've mentioned it before but while a song is playing, if you mute a channel it ignores any instrument/volume/effect changes that may occur while muted -- when you unmute the channel it plays using whatever instrument/volume/effects it had before muting. This is noticeable if you have a channel that alternates between instruments at times.
This is actually by design rather than a bug. I can look into improving that.
Stratelier wrote:
To be more specific:
[tested against 0.4.3]
1 - Attached is a test file, examine the instrument.
2 - Notice the arpeggio and volume definitions; both include a release sequence. When you hit notes in the Instrument editor you can clearly hear them both in effect.
3 - Toggle the volume envelope off and start hitting notes again, now the arpeggio release sequence doesn't occur at all.
4 - (This only affects the Instrument editor; in an actual song the instrument plays as specified.)
Ok I get it now, I misunderstood the first report. This is also by design, release sequences are never triggered in the case where there are no volume sequences, to avoid never-ending tones when previewing instruments. (That may still happen though, with volume sequences that doesn't end with a zero.)
Stratelier wrote:
Oh, I just found an interesting one: If a channel contains multiple release commands in a row, any release sequences that have finished will not retrigger, but any release sequences that are still playing will. Is it supposed to be that way?
Not really. I don't recommend doing that as it seems to be inconsistent with NSF export as well.
Also, I might've mentioned it before but while a song is playing, if you mute a channel it ignores any instrument/volume/effect changes that may occur while muted -- when you unmute the channel it plays using whatever instrument/volume/effects it had before muting. This is noticeable if you have a channel that alternates between instruments at times.
This is actually by design rather than a bug. I can look into improving that.
Can the Mute button just mask the channel volume to zero?
jsr wrote:
Ok I get it now, I misunderstood the first report. This is also by design, release sequences are never triggered in the case where there are no volume sequences, to avoid never-ending tones when previewing instruments. (That may still happen though, with volume sequences that doesn't end with a zero.)
Yes, it definitely does happen if a volume release sequence does not end in zero.... even if the volume curve is something stupid like "/ 15".
IMHO, if there is no volume release sequence then the Instrument editor could simply play the release sequence out to the length of its longest component and then simply cut it off (similar to how it does when the instrument has no release sequences at all). It's subtly annoying to design an instrument for a specific purpose only to see it not testing the same as it actually plays in-song.
jsr wrote:
Stratelier wrote:
Oh, I just found an interesting one: If a channel contains multiple release commands in a row, any release sequences that have finished will not retrigger, but any release sequences that are still playing will. Is it supposed to be that way?
Not really. I don't recommend doing that as it seems to be inconsistent with NSF export as well.
My testcase was a volume release that was about 10 frames long and an arpeggio release about 5 frames long -- using the default speed/tempo (6 frames per row) if I had multiple release commands the arpeggio did not retrigger but the volume did. If I sped the song up then everything retriggered, while if I slowed the song down nothing did. Really weird, that.
But yeah, that's moot. I did have one case where I wanted an instrument to do multiple releases in a row and was disappointed that they didn't retrigger -- I was able to work around it by delaying a note the whole row down (and immediately releasing it the next), so the note effectively starts playing at its release sequence instead of it starting point.
Is Sxx in the VRC7 meant to be improved? In 0.4.2 it acts as if I left a note release and in 0.4.3 it acts as if I left a volume of 0. (I prefer its function in 0.4.3; I don't want the function to change in the next version).
_______________________
It's 2026. You shouldn't be here....... YouTube Dropbox
Okay, here's another bug that involves the VRC7 and this also affects NSF export. Attached is the FTM file. I turn off the auto-portamento while using Sxx command and one row after. Both times the bug occurs.
The FTM uses notes mainly in P7F. Putting P80 fixes the issue.
The bug is that it plays random notes with 3FF a row after each row is executed and seems to have a release command used as the random buggy notes are played. In NSF it sounds more high pitched and with constant tone (at least that's what I found in Nestopia)
_______________________
It's 2026. You shouldn't be here....... YouTube Dropbox
I have a similar VRC7 problem. If I cut a note with Sxx early, a higher pitched note is played instead. The attached song has this in FM channel 3 starting from frame 4 where I'm using S02 to cut the duplicated notes early.
.png)
.png)