Hello - i’m having a hard time controlling the Bluesky MX with the MC6. I’ve been using the MC6 for a few months now and had no trouble with my other pedals: Eventide Space and H9, and strymon timeline. I’ve set up different MIDI channels etc… and feel very confident with the programming. But the MX is not behaving the same.
For example, I want to trigger patch 4A in the MX. I would expect that it would work with a Press action, PC Program change of 9. Instead, when I engage the MC6, it drops me into patch 50A. Why?
Then I have a preset button on the MC6 that is programmed with a PC Program change of 1. That works great … So I use “copy” in the morninstar editor for that exact Msg, paste it into a different preset and when I engage the MC6 for that new location, it drops me into patch 50A. That makes no sense to me since i just copy pasted something that works fine in one preset into another preset. Why would it behave differently? I’m going back and forth between the two presets in the MS editor and can’t find any differences, yet engaging these two different preset from the MC6 gives differently results. Totally confused.
Thanks in advance for any help.
Hi,
Are you sending any other messages together with the pc and did you check the midi monitor to confirm what midi messages are actually send by the MC?
No other messages in that midi channel as confirmed by the midi monitor.
The first 3 instructions are correct. It’s the next 3 that don’t change the MX correctly. The MX is the last in the MIDI cabling chain. I’ve checked the MIDI through settings on the Timeline and H9 to only be thru.
Is it possible that the H9 passes incoming pc# through to all channels, or that the BigSky’s RX is set to omni? If it’s 50A + 50B for the BigSky that pc 100 send to the H9 would explain the jump to 50A.
That makes sense. The H9’s settings show thru only but maybe there’s a secret setting I didn’t see. I will likely rewire the midi cables to start with the MX first and eliminate any compatibility issues.
Turns out I was an old version of the MX … I updated it and this particular issue went away. It was especially weird because it was happening after rewiring the midi cables to start with the MX. It was clearly changing based on the midi channel 3 instructions even though it was set to midi channel 1.
Now I have a different issue. The MX doesn’t come on when it should. See image.
After contacting Strymon, this seems to be a bug. CC 102 @ 0 kills the ability to reengage a preset for a PC to turn on a preset if the preset is in the current bank. It works fine if the PC triggers a preset in a different bank.