MC6 PRO Bug Fixes and New Features

[Belloposto]

James,

I found a solution.

Mute/Solo with Aeros Loop Studio

I’ve been working with new MC6 Pro and migrating my control settings from an MC8 - had a conceptual idea that I should be able to use a single page of MC6 Pro to Mute/Unmute OR Solo/Unsolo all six possible tracks of an Aeros Loop Studio Loop. Note I think the solution below will work for 3/6/8 foot switches with adjustments of course. This is a solution that allows you to stay on one page to control the tracks of your Aeros with a single press or long press. [image] Release action launches Mu…

[kospan]

i am having a similar issue with the omniports but with one pedal (Jackson Audio Bloom - no response at all, tried everything). The Strymon Iridium works just fine. Will try to fix Bloom issue by testing it with other cables and report back. (It could be a Bloom issue…)

[keg8605]

I recall the bloom being quirky to get going. I think it has something to do with the manual mixing up whether it receives on the tip or ring. I just sold mine, I’d search here or the facebook group for “Bloom”.

[kospan]

ok so a quick update on this issue. I managed to get the Bloom responding to CC messages through the 3.5mm port. Tried everything through the omniports but no go.

[james]

Just tested with our Jackson Bloom and it works fine. Have you tried with other Omniports just to check? All Omniports are independent so assuming one is “faulty”, a different port will still work fine.

Omniport setting should be set to “MIDI OUT - Standard” and the controller should be restarted after saving.

Just to add, the 3.5mm MIDI OUT and Omniports uses different software implementations though it should all work the same. Omniports need to function as MIDI OUT, Exp/Aux in and hence it is implemented differently from a standard MIDI OUT port which is hardware serial (just sharing for additional info).

What is the length of cable used to connect the Omniport to the Bloom?

[kospan]

many thanks for the info James. i will do a re-check on all omniports and get back to you. i am using a 60cm TRS cable which works well with the Iridium.

[kospan]

I tested all omniports with the cable that is working with the Iridium. None work with the Bloom. But the 3.5mm port works perfectly, so i’ll leave it there for now! (i’m guessing it’s a Bloom issue).

[FatBassLine]

Cant get the omniports to send midi type B. Trying to control darkglass photon.

[james]

@kospan @FatBassLine Can you try this firmware? I saw a logical fix but cannot test it yet until I’m back in office on Monday, but if you can give it a go, let me know if it fixes your issue.

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

The firmware should be stable. If ever you need to revert back to the original firmware, you can find it here: Releases · Morningstar-Engineering/MC6-PRO-MIDI-Controller · GitHub

[james]

Updated beta firmware released today with use new features and bug fixes.
Please refer to first post: MC6 PRO Bug Fixes and New Features

[kospan]

@james thanks James, i tried the firmware, it has not fixed the omniports issue with the Bloom.

[FatBassLine]

I tried new firmware but it didnt fix the midi type b through omniports. Thanks for responding so fast!. Love the new controller.

[Vindes]

@james

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

All of these work well for me after limited testing.

Any chance we could get the “change preset color using Preset Utility message type” added to the “Update Preset Message” section of the SysEx API interface?

I thought I managed to reverse engineer it using op5=36 when I got “Success” ack messages back, but in limited testing the MC6 seemed to be ignoring them despite the “Success” indicator.

[jsook]

I’ve noticed a couple issues with the editor, not sure if these are known bugs yet

• sometimes changing pages in the editor doesn’t actually change the information that’s displayed (names and messages stay the same)
• same with banks
• sometimes the name of a preset doesn’t show up (just black background) until I engage it and it toggles to the toggle state

[james]

@Vindes

Any chance we could get the “change preset color using Preset Utility message type” added to the “Update Preset Message” section of the SysEx API interface?

Yes, we will add it in. Currently the feature is not there yet.

@jsook

I’ve noticed a couple issues with the editor, not sure if these are known bugs yet

Thanks for the feedback. Are you connecting directly via USB or using an interface like the WIDI Jack?

[jsook]

I’ve been connecting directly to my computer with a usb C cable

[james]

Thanks for the info. Will check it out - likely an issue in the editor

[james]

Updated beta firmware released today with a USB Host bug fix.
Please refer to first post: MC6 PRO Bug Fixes and New Features

[Jwc197]

Hi James and All,

A few things I’ve noticed (if there’s a better place for me to put these items let me know - first time poster here)…

1. When editing bank settings, an engage preset message (on “enter bank” for example) only allows you to pick presets from the first 32 banks - thinking that might be a holdover from old code when we had less banks…

2. I’m having issues with midi message converter. Sending PC commands to the MC6pro via CME widi (Jack connected to 3.5mm ports) will change MC6pro banks, but the PC commands do not show up for me in the midi monitor at all (I can see the action that occurs as a result but not the midi command itself), and the midi message converter does not appear to have any effect on these messages.

Thanks!