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
Currently, when you make an N163 instrument, any of 16 available waves you make on that instrument will all be assigned to one slot. In the example ftm, Instrument 00 has them all allocated to position 0.
I request that each different wave could be allowed to have its own slot position in memory instead of all 16 being assigned to one slot.
First frame of the ftm shows what I'd like to work. Second frame shows the current workaround; you have to make a new instrument for each and have to be careful to leave any volume/pitch/arpeggio macros off so they won't retrigger.
[edit: d'oh! forgot the .ftm]
I see what you mean, but I don't see the problem with the current workaround, other than that more instruments must be used (but that's part of the design). Using macros shouldn't be a problem here since they shouldn't retrigger when changing only the instrument number.
I noticed however that the second frame has some issues after exporting, I need to check that.
Wxx - override instrument wave memory position for this channel
WFF could turn off the override and go back to using the instrument's settings.
This way you could manually allocate each channel its own position, and not have to duplicate instruments to work on different channels, or have to avoid macro interference, etc.
Might be a lot easier for new users as well, who could be advised to put W00,W20,W40,W60 at the top of the pattern and not use WAVs over 32 samples long, etc.
Edit: of course having an "auto" checkbox next to the wave position in the instrument, on by default, would be even easier to use. (Should also probably limit wave length to 32 if 4-channel, 16 if 8 when this is checked.)
That's a really good idea, but in the current convention, if the effect is 7-bit long (00-7F), then the eighth bit values (80-FF) are usually repeats of the 7-bit values (00-7F). ([url=http://www.youtube.com/TheEighthBit]Put your hand down!)
_______________________
"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
Well, even if it was I don't see why that "convention" has to apply in places where it would prevent something useful. However, wave position is actually an 8-bit value at the hardware level.
Depending on how many channels you are using, your channel control registers overlap with the wave data, so at the very least (1 channel) you couldn't practically use WF0-WFF because they overlap the first channel. So... WFF is already off limits anyway.
_______________________
"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
.png)