Has anyone had success with Meris prEditor via MC6Pro?

Hi there, have been going round in circles for days but the Meris prEditor refuses to connect to an Enzo X via the MC6Pro.

Have the following setup…

  • Morningstar reference doc: Meris
  • Have updated the MC6Pro, Enzo X, and both editors to latest versions
  • Enzo X: 1.2.2 (b1)
  • prEditor: 3.0.22
  • MC6Pro: 3.13.6
  • Morningstar Editor: 3.13
  • Enzo X is connected directly to MC6Pro DIN MIDI In/Out (have triple checked in/out ports)
  • MC6Pro is connected directly to Mac via USB-C
  • Morningstar Editor successfully connects to the MC6Pro via USB-C
  • MC6Pro has the following MIDI settings…

  • The Enzo X is on Channel 13…

  • Am trying to connect prEditor using these settings…

  • I see no messages in the MS Midi Monitor when trying to connect prEditor - should I?

  • Have quit the MS Editor incase it interferes with prEditor
  • Have restarted the Mac and tried again (and again, and again)

Can anyone see what I’m doing wrong?

Any pointers in the right direction much appreciated - I must be missing something basic.

Cheers, Ben

Was using the Desktop version of the MS Editor. Switching to the Chrome version, and prEditor now starts loading presets (with the Chrome MS Editor open) although, it’s crazy slow…

But then it disconnects…

Then it starts loading but disconnects again…

Can anyone see anything wrong with the setup that might cause this behaviour?

Or how you troubleshoot this stuff?

Any help much appreciated. Cheers, Ben

Hi,

Your Din5 midi in goes through to Din5 out. That creates a midi loop which might cause issues.

@GuitarWolf Legend! Thanks heaps. prEditor now loads the presets and I can interact with Enzo X without the connection dropping. Cheers

I’m using these same settings and the LVX won’t connect.

LVX is set to channel 7, MIDI is set to OUT and not THRU.

I can click the “Bypass” button in prEDITOR and it’ll turn on and off the selected effect, but the device icon always says “not connected” and the connection modal always comes back when I click “connect”

Turns out I think my HX stomp was blocking sysex messages in between. Good to go now.