Question 1

Which Port should I use to connect to the Editor?

Accepted Answer

Overview

In the Editor, we display all open MIDI ports in your computer, and you can choose the port that best suits your setup.

Which MIDI port to use

For most users, if your setup isn't anything complicated, you'll just need to choose the lowest-valued port for your device.

A MC device exposes 4 virtual MIDI ports to the computer (which is why there are 4 ports for each device) but only will communicate with the editor using Port 1 (on macOS). On Windows, you might see a different port name, such as input-0/output-1. Choose the lowest valued port.

The reason why we display all the MIDI ports in the editor is because many users have different use cases. Some users may have connected their MC DIN MIDI Input and Output ports to a USB MIDI interface with the intention of using the DIN MIDI Ports to communicate with the Editor, instead of using the USB port. In this case, they will need to select the USB MIDI interface they are using in this list.

Using the Manual Port Select

The MIDI Input and Output ports in the computer are separate, and are mapped algorithmically together. On the rare occasion that the input and output ports are mapped wrongly, the connection will not work. This problem might be

Question 2

Editor connection troubleshooting

Accepted Answer

If you do not see your device in the Editor

If you are using the Web Editor, check that MIDI has been enabled in the browser.

MIDI settings in Chrome

If you are using the PRO series, check that you have connected the USB cable connected to the USB Device port, and NOT the USB Host port.
Check that your USB Cable is not faulty
Check that your Browser is updated to the latest available version
Restart browser
Restart computer

If you can see your device in the Editor, but have issues connecting

Check that your Editor version matches your controller firmware version.

The Editor at editor.morningstar.io is constantly updated. If there is a new firmware released, the Editor will be updated to suit the latest firmware, and there might be communication issues with older firmwares (depending on whether we worked/improved on the communication protocol).

We always publish the firmware version that the Editor is suited for at the bottom of the editor:

Editor version

If you need access to the older editors, we also always have the links to previous versions available at the bottom of the editor.

If you are using the WIDI Jack to connect to the Editor, check that you have it set to the correct TRS MIDI Type.

There is a physical switch on the WIDI Jack that switches the c

Question 3

[New Feature] Preset Renderer

Accepted Answer

The Preset Renderer feature allows you to visualise the Preset colors and text on the editor itself.

You can enable this feature in the Editor Settings:

Editor Settings - Preset Renderer Be sure to click on Save to save the editor settings after enabling this feature.

Thereafter, when you navigate back to the Preset Settings page, you should see an updated interface:

Preset Settings - Preset Renderer

When you hover your mouse over the relevant sections, you will see the parts being selection.

Click on it to edit the colors:

Clicking on the Preset text will allow you to edit the text colors.

We hope this will improve your experience when editing your Presets in the editor.

Question 4

Using the MC as an interface for the Meris LVX/Mercury and prEditor

Accepted Answer

Using the MC as an interface for the Meris LVX and Mercury with the prEDITOR

The Meris prEDITOR allows you to quickly create presets, move them around, select your favorites, duplicate, swap, delete, assign your left and right favorites, import/export, access globals quickly and organize libraries.

https://www.meris.us/product/preditor-editor-librarian/

You’ll need to update the Meris devices to the latest firmware.

Hardware Connections

Connect the 5 PIN MIDI OUTPUT on the MC to the MIDI INPUT on the Meris
Connect the MIDI OUTPUT on the Meris to the 5 PIN MIDI INPUT on the MC

||| If there are other devices in the MIDI Signal chain, please make sure that these devices are set to pass MIDI THRU, and these devices can pass SysEx messages through. Some devices like the HX Stomp and Microcosm do not pass SysEx messages through, and having these devices in the MIDI Signal chain will not allow this feature to work

Software Settings

On the MC6MKII, and MC8, you need to enable Cross MIDI Thru in the Controller Settings so that the MC will pass incoming MIDI messages from the DIN5 port out to the USB port and vice versa.

For the MC Pro series, the MIDI Thru routing should be as such:

In the prEditor, select the MC MIDI Port and your In and Out port:

![](https://storage.crisp.chat/users/helpdesk/website/e8bd1d589d920800/image-20240308-100312_vfwjnf

Question 5

MIDI Clock is not working

Accepted Answer

MC is connected to the Editor

If you have updated to the v3.12 firmware, the MIDI clock being generated from the controller will time-out for 3 seconds if it is connected and communicating with the editor.

Please try disconnecting from the editor when using MIDI clock. **

MIDI Clock Port Settings

There is also a new feature under the Controller Settings >> General Configuration section called MIDI Clock Port Settings, where it allows you to select specific ports to send MIDI Clock from. Please ensure that the relevant ports are selected, then save the settings and restart the controller. Saving the settings once is essential if you just updated the firmware.

Check that your MC is actually generating the MIDI clock

MC6 PRO

If MIDI clock is being generated, the BPM indicator on the right screen should be ${color}#ff0000 and the BPM dot should be blinking

MC8

If MIDI clock is being generated, the BPM indicator should be blinking.

|| If the MC stops generating MIDI Clock after starting it, it may be because the MC is receiving MIDI clock from an external source. You can turn on the IGNORE MIDI CLOCK setting in the Controller Settings.

Question 6

How to have only one preset toggled at any one time

Accepted Answer

For many use cases, you may just want the controller to indicate the last used Preset, so you know which preset is active.

There are a few ways to do this.

1. Clear All Preset Toggles function in Bank Settings

In the Bank Settings, there is the Clear All Preset Toggles function that you can utilise. If turned on, this function will clear the state of ALL Presets in the Bank, except for the last engaged Preset. This would be the most straight-forward method to use if you want to apply this logic to all the Presets in the bank.

2. Toggle Reset Groups

The Toggle Reset Group feature allows you to put Presets into groups, and the Preset Toggle Reset logic will apply only to Presets within each group.

In the example below, I have Preset A, B and C in Toggle Reset Group 1, and Preset D, E and F in Toggle Reset Group 2

3. Use the Set Toggle Message Type

If you have something more complicated in mind, you can utilise the Set Toggle message type, which lets you Engage, Disengage, Toggle or Shift the state of other presets in the bank.

![](https://storage.crisp.chat/users/helpdesk/web

Frequently Read Articles

Browse All Categories