Mother 32 clocking DFAM: inconsistent M32 clock output or is it the DFAM?

[tick-tock]

I am seeing inconsistent behavior when clocking a DFAM from a M32.

1) When sending clock out from my M32, the 1st step is received like a quick pulse and throws everything off, effectively, sending 2 clocks on the 1st step. This behavior seems to start after I change a pattern and reset. This doesn't happen when I run a sequence after M32 initial power up.

2) When stopping a sequence then restarting, either the behavior above is observed, or the DFAM just sits for a few clocks (sometimes as many as before its own sequence kicks in.

FWIW, firmware 2.0.1 and I have Delay Pattern Set turned off and Load Saved Timing also set to off (toggling these doesn't make a difference). Also, it makes no difference on the M32's pattern, it could be the default blank one or any programmed one.

Is this the M32 or is this the DFAM?

[tick-tock]

sorted: it's a bug in FW 2.x. Moog knows about it and is working on it.

[Mos982]

I don't want to revive an old argument but this issue is still relevant. I am experiencing the exact problem mentioned above. It's impossible to play these instruments consistently in this way. How can we trust them in any performance? It was said that Moog was working on this issue 2 years ago, has a solution still not been found?