Well I have tested several scenarios now: changing midi ch of controller and 8 step, using specific CC’s and PC messages with each boot up, performing factory restore and swapping with other midi control devices.

With the Evolution controller, the 8 step mostly failed when sending CC’s over knobs and faders to control rate, depth, glide and step slider values but also occurred when sending CC 34 assigned to a button to toggle start and stop after many presses and another assigned to CC 118 with various values for preset load. The 8 step continued to act normal on boot up and eventually got stuck each time, all without ever rebooting the controller.

I then used a Roland EF-303 as a controller with the main knobs set to send CC’s for Rate, Glide, Depth and Expression ’24, 25, 28 and 4 respectively’ and set step length as the expression control selected.
These knobs all worked well without trouble with the exception of Rate control (24) which was only able to control when setting expression control (4) to the rate setting. I never encountered an issue with midi start/ stop/ reset messages (not CC form but midi standard messages) but then I decided to set the 8 step pattern length to 1 and assign my EF-303 step modulator to CC 16 as to obtain a midi controlled 16 step sequence, this did not work great as I hoped and most (95%) values sent were ignored.

I then swapped to a Roland MC-50 sequencer as the main controller. All midi standard start, stop and reset messages worked beautifully. I then created events in the sequencer for standard program change messages and located the events at around 50 ticks before each measure change. This was about 80% successful for the first 5 min and then became worse as I went along where it would even sometimes change to different programs than triggered.

All in all, I’d say the midi on my unit is not solid except when using standard start, stop and reset messages. I can continue testing more scenarios but it’s getting quite upsetting and I’ll likely be sending it in. This was my first EHX pedal and it hasn’t been the most pleasing experience as expected but I won’t hold it against the company too hard.

In most of these cases I have been sending isolated messages and even at slow tempos as you say and particularly in the case of the MC-50. The midi clock sync is spot on but messages other than standard transport ultimately get lost..It’s also worth noting that I’ve swapped several midi cables to rule that out as a factor.

I use to own a Behringer FCB1010 midi foot controller board which I wish I could plug up at this time to see how well that would integrate but as I said my 8 step is being returned. I am looking to exchange it in hopes that I’ll have better luck. Then maybe a second 8 step if all goes well.

Bonus Tip to others reading:
I do like using it as a pseudo LFO (Glide:9 for Triangle wave/ 0 for square, Last Step:2, Slider 1:0 Slider 2:127 Depth and Rate:as you desire) :coolsmile:

The UC33e does not have a clock output so there was none during my early tests with that. The 8 step did however continue to respond to clock output during the other tests/message failures.

” the fact that it continues to respond to MIDI clock after it stops responding to MIDI CC is a little puzzling.”

To say at the very least. I will be sending the unit to you guys directly and maybe you can confirm that I’m not crazy. I understand how controllers can sometimes skip values in messages sent being encoder based but I don’t get this level of error with my other gear. Sounds like your stress test is going well and I wish you luck. I also greatly appreciate your cooperation and the fact that you are taking a deeper look into possible flaws, it’s quite reassuring.