Big mess and it's totally not logik

Morningstar Gear MC Pro Series MIDI Controller
1

Hello, have any of you ever seen such a mess?

I’ll explain.

I programmed a bank, the one that @james @GuitarWolf @jason.nguyen helped me with.

First, the preset for the Walrus M1 modulation.

I managed to get it to work the way I want (in message scroll mode):

*Long press to turn it on or off

*Release to scroll between the different modulation effects. Everything works perfectly. With the effect on or off, I can scroll through the presets, and when I select another amp preset (A to E, all “Amp channels/presets”), the Walrus turns off.

Everything is perfect, exactly what I want.

So I move on to the last effect (preset) I want to program, the Strymon Brig delay (preset G).

Just like with the Walrus M1, I program it the same way,

except I get four messages instead of two.

Message 1: release-PC #

Message 2: Trigger message 31 from preset G (it’s the long press to turn the brig OFF)

Message 3: Set toggle + Disengage toggle G

Message 4: Rename preset

I added a message 32 to presets A to E (the same for all 5 preset drives), i.e.

Trigger message 31 from preset G (it’s the long press to turn the brig OFF, the same as in preset G of the brig)

This allows me to turn the brig on and off with a long press, if the effect is on, and scroll from one preset to another. Every time I change presets between A and E, the brig turns off. That’s what message 32 added to presets A to E is for.

Only here’s the thing: this message 32 (trigger message 31 from preset G (long press to turn the brig OFF) must be in position 2, otherwise it messes up preset F (modulation).

I’ve never seen such a mess. A preset intended for MIDI channel 4 on the Strymon brig messes up preset F on MIDI channel 2 on my Walrus.

I just spent all day yesterday, a whole Sunday, going over my presets with a magnifying glass.

I’ve never seen such a mess.

Can someone here explain this mess to me?

message 31 to trigger in preset A to F :backhand_index_pointing_down:

31
312187×1031 177 KB

message 32 in presets A,B,C,D,E :backhand_index_pointing_down:

32-preset A
32-preset A2203×1201 177 KB

the difference between the 2 banks in the video ist this last image.

when i have in pos 2 the walrus works as i prgommaged it

when in pos 1 or both, it’s the delay that works as i want….but all in all

why have a preset programmed only for chanel 4 (brig) has a incidence on midi chanel 2 (walrus) ???:enraged_face:

2

Can you share your backup file so we can better understand what is being sent?

3

@james

at first the one with the modulation as i want

Morningstar_MC8PRO_Bank_Backup_mod ok Delay not_20251014_180033.json (89.5 KB)

the with the Delay as i need. modulation is the same but works not correctly

Morningstar_MC8PRO_Bank_Backup_delay ok make mess in mod_20251014_180105.json (89.5 KB)

4

so…several tests here by me.

I can confirm this is a fuc@ing mess because of the strymon Brig

@james look at this here:

Morningstar_MC8PRO_Bank_Backup_mod nickel test DLY_20251016_140634.json (89.5 KB)

Can you telling me why a CC message regarding Midi chanel 4 (Stymon BRIG) changes the result of what previously worked with chanel numer 2 (walrus M1) ?

Is this type of behavior normal when programming midi ?

@GuitarWolf an opinion?

Look at this mess:

5

So people, i have tried some things

in preset A to E i have programmed a cc102 + value 0 with a release action for the BRIG to make sure the Walrus M1 works correctly.

That was working…as long as the MC8 pro was connected to the editor.

As soon the MC8 pro was disconnected, nothing works again :zany_face: . I have tried different positions, ever the same :poop: .

So i have decided to erase this message and replace it for a release action/ trigger message 31 from the delay preset. (see below)

14
142024×879 139 KB

That was the only way to get work the walrus M1 as expected:

I finally got this to work, but I’d still like your opinion on whether this is normal or not. I think it’s a shame that such a mess can happen.

@james @GuitarWolf

6

Hi,

I might be able to look into this on monday. I’ve had a look at one of the banks you’ve shared using the setlist manager on my phone. That doesn’t really work well but what I can tell from that is that you’ve apparently programmed a lot of redundant messages. That might be one source of the problem.

7

Honestly, I don’t get that impression.

You programmed presets A to E for me (Boss OD-200).

The only thing I added was the state of what the reverb should have. And the status of the Walrus (which must be in the bypass position when changing presets).

Then for the Walrus (modulation), I really stuck to what I was told for the Scroll message.

The only thing missing was really the status of the brig, which should be bypassed.

But please @GuitarWolf check it :blush:

I’ll even admit that knowing the problem is my own would reassure me. But this time, I don’t get that impression.

I ran a test this morning to test a feature.
A bank with nothing inside except a multi-engage/bypass preset A.
Believe it or not, the only effect that reacts as it should is the source audio ventris.
The Brig and the M1 turn on but don’t turn off. There’s clearly a problem with these pedals. But that’s another topic. It was just a test to check if a simple preset works or not…

8

@james no opinion on this?

9

For this, in your video (https://youtu.be/prxLVmSukvA?t=297), you said the issue occurs when you

  1. Long press Preset F to engage your M1
  2. Press Preset A
  3. Long press Preset F again, which does not work.

I have uploaded your backup file and checked the MIDI Monitor to confirm that the CC#31 value 127 message is being sent at step 3.

I suspect it might be something related to the M1 in receiving the stream of MIDI messages which is causing it to ignore the CC#31 value 127 message to engage it. You can try, just to test, removing or setting the actions of the other CC messages to “No Action” in Preset A so that only CC#32 is sent out when you engage Preset A, and see if the issue still occurs.

These are the MIDI messages that are sent when Preset A is engaged:

image
image1233×405 19.7 KB

Just FYI, there is a MIDI Monitor in the edtior, where you can view everything that is being executed when a preset is engaged, to help with troubleshooting:

image
image1306×483 21.6 KB

In your later video, you were sending that extra CC#102 message which fixes the issue. I’ve seen this behaviour before where certain devices need to receive a “dummy” message in order to get it to respond again.

10

it’s not just that.

It’s the fact that this message CC#102 is regarding a completely different Midi chanel. It’s not just any message that solves the problem; it literally concerns another MIDI channel. It’s by sending a message to MIDI channel 4 that it puts things in order on MIDI channel 2. It’s really nonsense.

11

I can 100% assure you that the MC is sending the MIDI messages out as it is programmed. But how the pedals respond to the incoming MIDI messages is a separate issue. If you have a USB MIDI interface, you can connect the MIDI Output to the interface to check the MIDI messages being sent as well.

I don’t have a M1 but I just tested this with the D1 (old version, changed the CC message in your preset from CC#31 to CC#11 to trigger the bypass) and it works fine.

Just to troubleshoot, is the M1 connected directly to the MC8 PRO? If not, can you try connecting it directly, to rule out any other possibilities of issues due to the messages being passed thru from other devices?

In the Controller Settings >> General Config, there is also a MIDI Send Delay parameter. Can you try increasing that setting to 30-50 and see if it helps with your issue?

12

Yes it is connected directly to the MC8 pro.

The problem comes not from the M1. It’s the strymon Brig that causes this mess.