You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question, is it possible to change the tone of each channel individually using the mapper? That is, channel 1 (pin 2 and 3) has tone n and channel 2 (pin 4 and 5) has tone n-5 and so on.
The text was updated successfully, but these errors were encountered:
There is. There's two ways to approach this (it's been a long time since I've actually touched this program, so my examples below might not be 100% correct, but should give you an idea of how it works):
You can make a separate mapper for channel by putting e.g. c==0 for the first channel, c==1 for the next channel, etc. Then each mapper will get notes from only one channel and you can do what you need to do with them there. This makes a lot of sense if each channel is assigned to a different kind of instrument that needs adjusting or something.
You can programmatically change the note value using the note script. E.g. instead of n, you could put n - (5*c) which would make each successive channel get mapped 5 notes lower.
Now, as I've been typing this I realized you might be asking a different question, since "channel" isn't necessarily assigned to pin numbers. The pin assignments are controlled by the "subAddress" part of the scripts. By default I think these are mapped to channels, like maybe c+1 or something. But if you wanted each sub-address to handle just one specific note (like if you were making chimes or a xylophone or something) you could have the sub-address script be something like n-40 which would make note 40 play on sub-address 0, etc.
Hopefully that helps, if you run into something else specific though let me know.
I have a question, is it possible to change the tone of each channel individually using the mapper? That is, channel 1 (pin 2 and 3) has tone n and channel 2 (pin 4 and 5) has tone n-5 and so on.
The text was updated successfully, but these errors were encountered: