BrienHBrown
Member
LOVING THE NEW III and have spent a lot of time reprogramming my MFC in MIDI mode to control it with all of the same functionality I had before until the new FCs become available. Outside of missing the benefits of bidirectional communication for synchronized on/off states, tap tempo light, etc., the MFC is now doing everything I could do before with one exception:
I previously used two different IA switches to manipulate a single Pitch block across X/Y states - one switch would turn on the X state for a half-step drop tuning, and the other would turn on the Y state for a whole-step drop tuning. I'm now trying to do the same thing using Channels A and B on the III. I currently have two different IA switches mapped to CC# 121 and have 121 mapped within the III on both the Bypass page and the Channel mapping pages in the MIDI setup section. I'm then trying to send CC Values to both engage the block and dictate the channel. It seems that when I send values 0 - 3, the III works as designed and sets the channels to A-D respectively. However, values less than 64 won't engage the block, only 64 - 127 will engage the block (based upon trial and error, I'm assuming 0-63 Bypass and 64-127 Engage. Unfortunately, all values between 4 and 127 consistently and only set the channel to D, not ABCD repetitively as described in the documentation on pages 45 and 139 of the manual. Therefore, if I want to engage the block by using a value between 64 and 127, I'm currently limited to only channel D, which won't work for my use case (I could use channel D in stead of A/B, but I'd still be limited to only doing either a half-step or whole-step drop, not both at the single tap of a switch.
I could probably use an additional pitch block to figure out a workaround, but I'd prefer to use just one and use the III as I think it is designed per the documentation. Is this just user error and my lack of MIDI knowledge, or could someone please confirm that the III is incorrectly interpreting values above 3 as only Channel D? If this is a bug, I'm guessing it might impact others as well with different use cases.
Thanks!!
P.S. The III is bad ass!!
I previously used two different IA switches to manipulate a single Pitch block across X/Y states - one switch would turn on the X state for a half-step drop tuning, and the other would turn on the Y state for a whole-step drop tuning. I'm now trying to do the same thing using Channels A and B on the III. I currently have two different IA switches mapped to CC# 121 and have 121 mapped within the III on both the Bypass page and the Channel mapping pages in the MIDI setup section. I'm then trying to send CC Values to both engage the block and dictate the channel. It seems that when I send values 0 - 3, the III works as designed and sets the channels to A-D respectively. However, values less than 64 won't engage the block, only 64 - 127 will engage the block (based upon trial and error, I'm assuming 0-63 Bypass and 64-127 Engage. Unfortunately, all values between 4 and 127 consistently and only set the channel to D, not ABCD repetitively as described in the documentation on pages 45 and 139 of the manual. Therefore, if I want to engage the block by using a value between 64 and 127, I'm currently limited to only channel D, which won't work for my use case (I could use channel D in stead of A/B, but I'd still be limited to only doing either a half-step or whole-step drop, not both at the single tap of a switch.
I could probably use an additional pitch block to figure out a workaround, but I'd prefer to use just one and use the III as I think it is designed per the documentation. Is this just user error and my lack of MIDI knowledge, or could someone please confirm that the III is incorrectly interpreting values above 3 as only Channel D? If this is a bug, I'm guessing it might impact others as well with different use cases.
Thanks!!
P.S. The III is bad ass!!