Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
My life would be easier if I could comment my FTMs as if they were program code. I know that this idea has been suggested before (at least once by me, in fact), but now I will offer implementation suggestions.
First, each channel could have a Comments column beyond its fx4 column (so you'd have to expand it to see it). The column itself could be quite wide, maybe sixty characters or more, since it would remain hidden most of the time. When a channel has a comment in it, even when the column is hidden, that channel could have some kind of graphical indicator on its header while the cursor is on the row with the comment.
Alternately, there could be a Comments "Channel" that would appear to the right of the furthest-right audio channel. It wouldn't have the same layout of a normal channel, of course, exchanging the usual array of columns for one big "column" that's basically just a text entry field for each row. The Comments "Channel" could be expanded to make more room for longer comments in the same way that the audio channels' additional effects columns can be shown and hidden.
The primary advantage of the first idea is that each channel would get its own comment column, while the second idea consolidates them into one location. The first idea does suffer from the fact that comments would likely remain hidden most of the time, but that's a minimal concern.
On to break points. It would be swell to be able to insert a break point in a tune when you're working on something that's not at the very end or beginning of a long piece. If a break point were set in a row, the tracker would automatically stop playback when it got there. Additionally, there could be navigation options to move directly to the next or previous break points. Break points could be set and cleared by clicking/right-clicking/control-clicking/etc. in the row number gutter on the left side of the tracker. Break points could also show up in the frame number gutter on the left side of the frame navigation pane.
On a related note, since I am implementing NSFe for NSFPlay, I have added an additional NSFe chunk called 'text' which simply contains a null terminated string of any length.
This would give the user space to write whatever they want about the file, just like how .IT files have a space for a message. If Famitracker kept a message with the FTM file it could be exported to the text block as NSFe, and it would also be a great place to write notes temporarily.
B00daW: That would be really easy for anyone to add since the sources are available, preferably with an effect that is unused on some channels (for example Zxx)
I've been having thoughts along the lines of 'I should implement X in channel Y at time Z, but it would take a while and I'd rather postpone it later'. I thought about a system where I could write on that spot in the channel a note to myself to try ABC later, rather than having to keep a zillion possible improvements in my head. Yeah, a text file could be an alternative, but that's less wieldy (you'd have to glance over to it to just confirm/deny if there's a note, let alone what it is!)
I like the idea of having a comments channel, I could write stuff like 'chord progression is/should be blah blah blah' and 'add arps here?' and stuff