Page 1 of 1

Mother 32 + DFAM sync problem

Posted: Fri Aug 22, 2025 7:56 pm
by zinoomordep
Hi everyone. :(

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?

Thanks!

Re: Mother 32 + DFAM sync problem

Posted: Tue Aug 26, 2025 2:45 am
by synthpeter
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.

Re: Mother 32 + DFAM sync problem

Posted: Wed Sep 03, 2025 10:45 pm
by zinoomordep
synthpeter wrote: Tue Aug 26, 2025 2:45 am 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.
Thanx for the response!

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.

Image