I recently bought a M32 and Moog DFAM and been using them consistently for a week now. Today my DFAM suddenly started behaving oddly when synced to my Mother 32. It was working perfectly yesterday, but now it randomly skips or holds steps whenever I press run on the Mother 32. You can see a video here: https://youtube.com/shorts/yBD_8NdUbZA?feature=share
Setup:
Mother 32 ASSIGN OUT → DFAM ADV/CLOCK IN
ASSIGN output is set to default
Mother 32 firmware: 2.0.1
I’ve tried multiple cables, but the issue persists. I even tried cleaning the the ports with contact cleaner. Even if I start the DFAM on step 8, it still jumps or holds steps randomly when running from the Mother.
I’m really sad this is happening, especially since I just decided to start building a modular setup for myself. Has anyone seen this before or have suggestions for what might be wrong?
From the video, it looks like the M32 is definitely running faster than the DFAM. Are you sure that you’ve not assigned clock/2 or clock/4? In that case, starting or stopping may lead to a break in the clock output rate that needs catching up, which would look exactly as in the video.
I’ve tried using clock/2 and clock/4, but neither works properly. Even when the DFAM starts on time and doesn’t stutter to begin, it still skips a few milliseconds on each step, which makes it really annoying to use. When I clock the DFAM from another piece of gear, it works as expected. It’s definitely a problem with the assign output from Mother 32.
I just heard back from Moog after a few emails, and apparently this is something that happens with many Mother 32 units. They insist it’s not a fault, but I wish I had known this earlier. From what I’ve seen, it’s a pretty common issue. Huge bummer.
I have a DFAM and 2 x M-32s and have the same problem. I bought ALM’s Pamela’s Pro Workout to clock the modules. Interestingly Patreon’s Braintree56 had the same problem and Pamela’s resolved it for him, as he has said in one of his videos. Not for me. And there is no pattern. Sometimes all three start at step one, but more often than not, the DFAM starts a step ahead, or one of the M-32s is out of step by one beat. I use a D-Thing with the DFAM, but the problem is the same with or without it. I don’t understand how Moog can consider it not to be a problem. This equipment is a considerable investment. The issue was also reported on the forum in February 2021.
I was reading this post as I had some issues as well. I am not sure if it’s the same issue but for me one was running ahead of the other and they where not in sync.
What worked for me is to set in setup mode, also running firmware. 2.01
Page 1 Assignable output to option 2 (clock)
Page 3 Analog clock mode to option 3 analog clock mode (was set in 4 before when issues appeared)
Page 4 to option 4 4 ppn
Page 5 option 4 to 4 ppn
Running third party single patch cable from trigger out on mother to advance clock on dfam. Set it to step 8 on dfam, put it to run and then run mother 32.
No idea if this has the smallest chance of helping you but if it does let me know.
For me it doesn’t make sense as the tempo isn’t used but it made a difference for me.
Thanks Jelle, today just found your response. Thanks for reaching out. I actually did all the controlled tests again. For the two M32s errors are totally random. On different occasions when I trigger with Pam’s Pro, sometimes they both start on step 1 and on other occasions both can start one step behind the other.
I also took Pam’s out of the equation and when I use one M32 as a clock for the other, the latter’s tempo was a multiple of the former. The variables affecting this were Sequencer Clock (set up page 1) and ClockDivision values (adjust Tempo whilst holding down KB & STEP). I will copy and paste your advice and have a look tomorrow and let you know. Thanks again, Mike.
Hi Jelle, I finally got the solution with Pam’s Pro Workout. With the two M-32s clocked by Pam’s, I reduced the levels of the Pam’s signal output from 100% to 25%. (Pam’s also controls reset to step 1). Now the two and the DFAM (with D-Thing) now reset and all start on step 1, when I engage Pam’s to start. I have the DFAM clocked by the Pam’s PPEXP1 expander, which does not have any parameters to change. Prior to the changes, I started Pam’s on several occasions and randomly, one of the three would be one step out of sync or rarely, they would start together. This has plagued me for over a year, so I am beyond overjoyed!
