MC6 PRO Bug Fixes and New Features

[james]

As more users receive their units, we’ve received some bug reports about the firmware and the editor. The editor fixes will be pushed automatically. For the firmware, we’ll release the firmware here with all the latest bug fixes before publishing an official release.

I’ll also add some new features here instead of waiting for the next v3.12 firmware.

Known bugs not fixed yet

None

---

2023-03-16 Beta4

2023-03-16 MC6-Pro Beta4.hex (1.1 MB)

Use Beta Editor with Beta Firmware: Morningstar MIDI Editor

Bug Fixes

• Engage Preset message type bug. Does not show 128 banks.
• Fixed USB Host issue communicating with editor via WIDI uHost
• Bank arrangement feature indicates that it saved successfully, but still loads default data, which means it is not being saved.

---

2023-03-08

Use Beta Editor with Beta Firmware: Morningstar MIDI Editor

2023-03-08 MC6-Pro beta.hex (1.1 MB)

Bug Fixes

• Fixed issue with connecting to editor via USB Host port (WIDI uHost).
• Fixed issue with controlling high-speed USB devices via the USB Host port (e.g. HX Stomp, MC6 Pro)
• Fixed Omniport MIDI Out Type A (Standard)/ Type B bug

---

2023-03-04

Use Beta Editor with Beta Firmware: Morningstar MIDI Editor

2023-03-04 MC6-Pro beta.hex (1.1 MB)

New features

• Added more color options
• Added ability to change preset color using the Preset Utility message type
• Enhanced toggle page message type to include options to Page up, Page down and jumping to specific pages
• Added screensaver. After 1 hour of no activity, screens will darken until a new event takes place i.e. switch press or expression movement

Bug fixes

• Editor colours are now more reflective of actual colours on the controller
• Expression % color does not follow new color scheme when changed
• Using Engage Preset to trigger a Preset with Set Toggle will hang and reset the controller
• Select Exp message for Bank Presets not saving correctly for Msg1-Msg6

---

2023-02-24

2023-02-24 MC6-Pro Bank Jump Bug fix v2.hex (1.1 MB)

Bug fixes

• Fixed Bank jump does not respect toggle page setting in the bank jump message.

[32pedalboards]

Uh so yea, “Press” should actually work when “Pressing”, as of right now, actions only perform once released. There is actually no functional difference between “Press” and “Release” actions. Am I missing something obvious?

[cVarsity]

There’s some overlapping when you start using one preset for multiple functions. If you’re using a Long Press and a Press in the same preset Press gets sent even when holding it down. Instead you can use a Long Press and a Release, which is different from Long Press Release so it won’t get sent after holding.
As you have it programed they work the same, but it might be in your best interest to just use Release for anything that you want sent on just one foot tap. I spent a while troubleshooting my first complicated patches cause I was mixing press and release

[moley6knipe]

@32pedalboards - you have msg1 one set to position 1 and msg 2 set to position 2, and toggle mode on. I think you might want both messages in position Both and toggle mode off?

[PGORE]

I was working on the MC6 Pro today and noticed something unusual.
6 footswitches each programmed with Toggle On - each separately mutes one of 6 tracks on the Aeros using a simple press action.

Each has Mute_x (position 1) as short name and Unmute_x as position 2 name. Each is color coded to draw attention to the track that is muted.

Scenario -
I mute track1 (it shows position 2 name Unmute_1) and is muted.
When I then mute track 2, it shows position 2 name Unmute_2 BUT changes the display name of track 1 back to Mute_1 (lost color coding)… AND leaves track 1 actually muted.

In essence - the muting functions seem to be intact but the display is operating separately from the midi commands. Ultimately, with this many tracks… I’d like to have the color coding be retained so I can keep track of what is muted and what is not.

I tried replicating this on my MC8 and it works as expected. All switches can be in either position 1 or position 2 display scenario.

Is this a bug or am I missing some settings somewhere.

Thanks
P

[james]

Can you share your bank data file so I can load it into my
controller to check?

[Gerovi]

Just updated as my mc6 pro was jumping to the second page/presets. now when I open the browser does not show the name of presets or allow me to make changes as swap presets

[mm_Jay]

Couple of oddities I’ve noticed in the editor.

1. It doesn’t always show me bank names (left column)- sometimes I just get the numbers.

2. The editor doesn’t show the correct state of the Omniports. They show as “Aux” when you first connect, even when the device menu shows something else (e.g. MIDI Standard). If you make a change through the editor and disconnect/reconnect the device, you’re back to Aux again.

[mm_Jay]

Omiport issue here:

I’m having issues getting MIDI out of the Omniports, unless I’m doing something wrong. Set them to MIDI Standard (via the editor or directly via the device), and my connected device doesn’t respond. If I take the same cable and plug it into the 3.5mm MIDI out jack (using a 1/4" to 3.5 mm adapter) the device works fine. Tried all 4 ports / MIDI configuration options.

[james]

@mm_Jay

I’m having issues getting MIDI out of the Omniports, unless I’m doing something wrong

What MIDI device are you controlling? For Omniport, the device needs to be restarted for the new settings to take effect. After you save the omniport settings, you can just disconnect from the editor and the controller will trigger a reset.

@mm_Jay

It doesn’t always show me bank names (left column)- sometimes I just get the numbers.

Will look into it. So far i’ve not been able to replicate.

@mm_Jay

The editor doesn’t show the correct state of the Omniports. They show as “Aux” when you first connect, even when the device menu shows something else (e.g. MIDI Standard). If you make a change through the editor and reconnect, you’re back to Aux again.

I’m not able to replicate as well. Possible to share a screen recording of this issue?

@Gerovi

I open the browser does not show the name of presets or allow me to make changes as swap presets

Does the issue still persists after restarting browser and controller? Just to clarify, you are able to connect to editor but not able to save preset changes?

[Gerovi]

@james

Does the issue still persists after restarting browser and controller? Just to clarify, you are able to connect to editor but not able to save preset changes?

I just opened the editor and there was an update, now everything seems to be working again

[automatic]

When I press D + F per manual on the MC6Pro I don’t see a menu. Do I need to hold them while powering on or not implemented yet?

[PGORE]

I get menu when pressing together even when on

[mm_Jay]

@james

What MIDI device are you controlling? For Omniport, the device needs to be restarted for the new settings to take effect. After you save the omniport settings, you can just disconnect from the editor and the controller will trigger a reset.

Bluguitar MIDI1 adapter. I can’t get it to respond to any MIDI messages from the Omniports. (Whereas it responds perfectly from the 3.5 mm MIDI out jack, using the same commands. Also worked from the MC6 Mk II Omniport.)

I have restarted the MC6 Pro multiple times, so it’s not that. I’m stumped.

@james

Will look into it. So far i’ve not been able to replicate.

@james

I’m not able to replicate as well. Possible to share a screen recording of this issue?

Sure- here (hard to see, but note the Omniport settings when I’m on that page):

MC6 Pro Editor Behaviour

[spamilton1]

I’m having an issue where it’s crashing the pedal and causing it to reboot. I have preset setup to effectively launch preset A in 7 different banks, see attached image

[james]

@mm_Jay

Bluguitar MIDI1 adapter.

Let me check when back in office tomorrow. It doesn’t seem like a MIDI-standard type of implementation, since it just uses a TS cable. When we test the omniports, it is mostly to MIDI-standard ports (i.e. with a built-in isolator), apart from the more popular Chase bliss or Meris MIDI ports (these don’t follow the MIDI Standard).

The reason why the 3.5mm port might work while the omniport does not is because the implementation is different i.e. the 3.5mm port is hardware implemented, while the omniports are software (which is why we can do MIDI OUT, Exp in, Aux In).

The reason why the MC6 omniports might work, while the MC6 Pro omniports does not, is because they use different processors and software implementation. I can’t guarantee it will work for all non-MIDI Standard devices but it should work for all MIDI-standard devices.

You can check that the omniport is sending MIDI by connecting the omniport to one of the MC6 Pro MIDI Input i.e. the DIN5 or 3.5mm TRS input, and then sending a MIDI message. When the MC6 Pro receives a MIDI message, an indicator will show on the right-most LCD: MC6 PRO

Again, let me test this in office tomorrow.

@automatic

When I press D + F per manual on the MC6Pro I don’t see a menu. Do I need to hold them while powering on or not implemented yet?

D+F will bring you to the menu, unless you have Looper Mode on, or switch sensitivity set to the highest setting, then it is harder to detect a dual switch press unless both are pressed at exactly the same time.

You can also access the menu by holding switch D before powering up the controller.

@mm_Jay

Sure- here (hard to see, but note the Omniport settings when I’m on that page):

Noted on the issue. Does pressing “Load Settings” not update the settings there? Let me try to replicate the issue again and update.

@spamilton1

I’m having an issue where it’s crashing the pedal and causing it to reboot. I have preset setup to effectively launch preset A in 7 different banks, see attached image

There are a few scenarios where using engage preset might hang the controller. The most obvious one would be an infinite loop i.e. engaging a preset to engage the same preset and that continues in an infinite loop. AFAIK, there is one related to engaging a preset which uses the Utility “Set message scroll” message type as well. The only way for me to check would be for you to do a data dump and then send me your controller backup file (help@morningstarfx.com) so I can load it into my controller to check. Just add a link back to this thread URL so I know the context.

[automatic]

@james

D+F will bring you to the menu, unless you have Looper Mode on, or switch sensitivity set to the highest setting, then it is harder to detect a dual switch press unless both are pressed at exactly the same time.

You can also access the menu by holding switch D before powering up the controller.

I do see the menu when holding D at power on. I don’t see a place in the editor to set switch sensitivity (1.3.4) I looking at controller settings page.

[mm_Jay]

@james

It doesn’t seem like a MIDI-standard type of implementation, since it just uses a TS cable.

I should have elaborated- yes, it’s an odd device. It should take a DIN connector but I’ve wired it so it uses TR from a 1/4" to pins 4 & 5. (And sends to the device downstream via a 1/4" connection.) Anyhow- it does work from the 3.5 mm out so I will just stick with that.

@james

You can check that the omniport is sending MIDI by connecting the omniport to one of the MC6 Pro MIDI Input i.e. the DIN5 or 3.5mm TRS input, and then sending a MIDI message. When the MC6 Pro receives a MIDI message, an indicator will show on the right-most LCD

Yes, that works perfectly. Thank you.

[james]

@PGORE

What is a concern is that the color coding for position two activates when I press the first switch (whether release or long press release)…

Just to confirm, you only want it to toggle when you do a Press/Release, and not on a Long Press Release? The preset will toggle when any message executes as long as the Toggle Mode is turned on. If you want it to only toggle on a specific action, you will need to turn toggle mode off and then just add a Toggle Preset message with the action you want to toggle with:

This will cause the preset to toggle when a press/release action is executed, and the preset will not toggle when you do a long press release.

@PGORE

wouldn’t it be cool if I was able to use different short names for Mute and Solo and unmute and solo… that seems like a pretty advanced feature for the future.

Might need to elaborate as I’m not 100% clear on the request. But if you need to change the name based on specific actions, there is a Preset Rename message type that you can use. This will temporarily rename the preset:

[automatic]

I don’t see a place in the editor to set switch sensitivity (1.3.4) I looking at controller settings page.

This is in the chrome editor. I do see the sensitivity setting documented in the MC6Pro manual. I’ll verify I can find it later when I have the unit hooked up again.