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
FamiTracker
1) just like how you have the "remove unused patterns" feature... it would be cool to have "remove unused sequences"
2) it would be nice to have a "remove redundant commands" feature... so that when you have data in the instrument # column, vol, and effects that repeat... they're all automatically removed - to me its easier to see whats going on in the song this way and i already manually do this
3) option not to include DPCM in NSF export... like... not save any of the DPCM patterns and not include DPCM playback in the NSF since it doesnt use it (saving space)
4) the instrument select field... the columns are bunched together as vertical groups of 7's - i know this is an anal request but it would be nice if they were grouped as 8 per column... [b]there appears to be room for it[/b] - i have been hoping for this for years
5) VRC6 channel interpretation of normal 2a03 instruments... why not have the VRC6 channel interpret 2a03 instruments by ignoring the extra VRC6 features when replaying 2a03 instruments?
if any of this is unclear... ask me and i'll try to explain w/ different words
2) -- i really like that idea, it's something I do a lot as well to save editing tonnes of the same values later if one thing needs to be changed. though i dunno how easy or hard it would be to implement something like that.
5) -- yes, and vice-versa. that's actually how i thought expansions would work before VRC6 was first implemented. it'd be very useful from the perspective of cutting down on superfluous instruments. it's the same for other expansions too, like FDS -- very often i just want a blank instrument and to treat every channel equally (and control any other aspects of the sound via the patterns) rather than make carbon-copy instruments per expansion... it can get messy, especially working at lower speeds where you can't do as much in the patterns due to lack of space.
ain't redundancy a bitch? totally naffs up the workflow.
Haha, I've also noticed that the instrument list doesn't use the extra space and I don't know why. Maybe it allocates it for the scroll bar or something.
The DPCM export option would be useful. I've had plans on improving the export function overall for some time now, but most of the time has gone to removing bugs so far. The rest should be easy to add. (I'll need to think about the instrument interpretation though.)
Fairly sure Dave has said something about this in the past, but some option that would auto cycle through FDS instruments, or consolidate FDS waves to one instrument setting would be nice.
For example, instead of making each instrument tied to a wave, make waves into a setting like how "volume" "arpeggio" etc are defined currently for 2a03. Makes it nicer if you want to use different volume envelopes on the same wave.
Also if this were the case, you'd be able to make another part of the instrument that'd string along different waves, like
yeah, wave envelopes are a good idea. ideally it'd be handy if fds waves were tied to Vxx as well. that would also cut down hugely on instruments and improve workflow significantly. i'm just trying to think how that would work though... a separate tab for setting up the waves, numbered 00 to FF, alike the DPCM tab? that'd obviously need to be done before any instrument envelopes or Vxx could work. and with a range so large, it would be difficult to visualise as a graph... so i don't know how that would work, since all the other envelope screens thus far have had like 16 possible values max. it's doable but it'd be really fiddly unless it was streamlined somehow.
then i guess there's FM envelopes and effect column control x_x which i can see being problematic to implement. but yeah basically separating the parameters as much as possible is the best idea.
One way I've thought of is to store all waves in an array and then add an index selector along with the wave editor (like envelopes on 2a03), then it would be easy to use the Vxx command. Envelopes for selecting waves would still be a little problematic, the problem with a glitch each time the wave is changed is still there. (Try switching between two instruments @ speed=1 and export to NSF and listen).
