Playing presets with sequences using external midi is not working [somewhat solved]

The MF has this nice preset 193 which comes with a sequence and I want to play it via Midi IN from my groovebox (I tried both a Dirtywave M8 and a Polyend Tracker+). But it does not work correctly and shows erratic behaviour.

My groovebox has a DIN Midi connection to the MF Midi in, the preset 193 is selected and the sequencer button is active. When I play a key on the MF keyboard, the sequence plays just fine. I checked the setting of Midi routing and Midi should go into the arp/seq. Both boxes send clock and transport via Midi and the MF is configured to receive both from external Midi. Also the notes come on the correct channel.

My groovebox loops over a C-5 and a G-5 with no note off and enough time in between for the sequence to run. The results are heavily mixed:

  • [a] Most of the time the two notes are just played solo. The sequencer seems to run through, but it does not make any sound.
  • [b] I can switch to arp, wait for a note to be sent and then switch to the sequencer and it plays fine until the next note is sent (back to [a]). But it always plays the sequence as if It received C-5.
  • [c] when I change the LED dim settings on the MF, it behaves like [b] for a short time and then falls back to [a] again (what?? this is very crazy …)
  • [d] on rare occasions the MF stops to make any sound. Only switching to a different preset and then switching back and waiting a couple of seconds “heals” this.
  • [e] on the Polyend Tracker+ I was able to get somewhat repeatable successes IF I send a CC 64 (Sustain) on each note. But I have to change the value each time I press play on the PT+ to make it work.

All devices have their most up to date firmware. I have reset the settings on the MF to no avail.

Please: any ideas?

Make sure the Utility menu “MIDI Seq/Synth” item is set to “ArpSeq|Local on”:

Utility → MIDI → MIDI Seq/Synth = “ArpSeq|Local on”

The other value “Synth|Local On” bypasses the sequencer.

I have set it exactly like that.

And just to be sure, I tried all four combinations, but to no avail. I am quite sure that I am missing something here, but I don’t know what. I will experiment a bit with Midi via USB, maybe that works differently.

On the Dirtywave M8 it seems to be the clock signal. If I send it via Midi (regardless of 5pin or usb), I have the effect of [a].

If I configure the M8 to only send notes and transport via Midi, it works. But I have to manually set the clocks to the same bpm. This is absolutely doable and though strangely unexpected somewhat acceptable.

The Polyend Tracker+ is no success. Even without clock signal from it, the sequence will not start. It will not even look like it’s playing and sticks to [a]. I was not able to consistently recreate [e] so PT+ is a fail with no workaround known to me here.

I’m a little confused by the results here too when I start messing with another sequencer/arp connected to the MnF. I’d need to look at the MIDI (DIN and USB) output of each to see what actually going on, but that might not help your situation since you use different gear. Perhaps you can do that on your end.

BTW, the MnF can also can control its sync source and whether it receives transport messages - however, you seem to be on top of the config stuff, so you probably know all that.

With that I’m out of ideas, sorry.

Still thanks for the suggestion. I tried Renoise to monitor the USB MIDI events and it displays (most? probably all!) of them quite nicely. This way I was at least able to see that both devices send the same note on/off commands and the culprit must be something else. For M8 it was the clock, for PT+ … who knows. Maybe someone in the polyend backstage forum: