Glad it was helpful! Like I said it's a workaround. I asked Moog about it. I'm still following this up. 😉 In the meantime this is what a very helpful person at Moog told me: "Thanks for reaching out! ... I'm afraid the assignable output is dependent on the sequencer running in order to function. It would be nice to utilize the assignable output without having to run the sequencer. I'll pass the suggestion along to our engineers to see if it can be done in a future update."
Sure! To be honest, I just happened to have some free time on my hands, and I figured it was the perfect opportunity to document this experiment and share it.😉 Your question was really interesting. I contacted Moog and they confirmed that the sequencer has to run in order for the Assignable Output to work. - You can read the reply under the pinned comment above. Anyway, I'm thrilled that you found the video helpful. Thanks again for your comment! 🎹🎶
This is a great video on this concept, I guess I never realized people might be curious about how to do it! Patching the Mother 32 with an external sequencer and then setting the assignable output to random mode gives you a nice synced Sample and Hold circuit using this method.
Hi there, thanks for the video. My M32 isn't behaving properly, and for what I see I believe yours does the same. When you play a sequence of "C" on M32 while the external sequencer is running, the resulting sequence is trasposed. Is not even in another key (for example 3 semitone above or something), there are random octaves and stuff. Your sequence ahs, for example, the first note on another octave. Please do correct me if I'm wrong. Having an empty sequence (i.e. just rests) doesn't solve the problem, cause in that case the M32 won't play at all...
Hi there, thank you for tuning in! Yes, this one is a tricky issue. I believe it has to do with how the Mother-32 handles the start of a pattern when it's receiving both internal and external clock signals. I've noticed it myself, it will retrigger step 1 on every loop, falling out of sync with the Keystep Pro. Like I said in the video, it's more of a workaround. I reached out to Moog, and this was their response at the time: " I'm afraid the assignable output is dependent on the sequencer running in order to function. It would be nice to utilize the assignable output without having to run the sequencer. I'll pass the suggestion along to our engineers to see if it can be done in a future update." Let me know if checking the Tempo settings help. I hope I understood your question correctly - if not feel free to clarify, I'll be happy to look into it further. Also, if anyone else reading this has any insights, please chime in! 👋
That's very helpful. 👍👍
Glad it was helpful! Like I said it's a workaround. I asked Moog about it. I'm still following this up. 😉
In the meantime this is what a very helpful person at Moog told me:
"Thanks for reaching out! ... I'm afraid the assignable output is dependent on the sequencer running in order to function. It would be nice to utilize the assignable output without having to run the sequencer. I'll pass the suggestion along to our engineers to see if it can be done in a future update."
I'm super impressed not just that you responded to my comment with a video, but also how quickly! Thanks so much for testing this and sharing 🙏🙌
Sure! To be honest, I just happened to have some free time on my hands, and I figured it was the perfect opportunity to document this experiment and share it.😉 Your question was really interesting. I contacted Moog and they confirmed that the sequencer has to run in order for the Assignable Output to work. - You can read the reply under the pinned comment above.
Anyway, I'm thrilled that you found the video helpful. Thanks again for your comment! 🎹🎶
This is a great video on this concept, I guess I never realized people might be curious about how to do it! Patching the Mother 32 with an external sequencer and then setting the assignable output to random mode gives you a nice synced Sample and Hold circuit using this method.
Especially since I was searching for something else. 😁 Thanks for watching and leaving a comment. And yes, keep on experimenting.
Hi there, thanks for the video. My M32 isn't behaving properly, and for what I see I believe yours does the same. When you play a sequence of "C" on M32 while the external sequencer is running, the resulting sequence is trasposed. Is not even in another key (for example 3 semitone above or something), there are random octaves and stuff. Your sequence ahs, for example, the first note on another octave. Please do correct me if I'm wrong. Having an empty sequence (i.e. just rests) doesn't solve the problem, cause in that case the M32 won't play at all...
Hi there, thank you for tuning in! Yes, this one is a tricky issue. I believe it has to do with how the Mother-32 handles the start of a pattern when it's receiving both internal and external clock signals.
I've noticed it myself, it will retrigger step 1 on every loop, falling out of sync with the Keystep Pro. Like I said in the video, it's more of a workaround. I reached out to Moog, and this was their response at the time:
" I'm afraid the assignable output is dependent on the sequencer running in order to function. It would be nice to utilize the assignable output without having to run the sequencer. I'll pass the suggestion along to our engineers to see if it can be done in a future update."
Let me know if checking the Tempo settings help. I hope I understood your question correctly - if not feel free to clarify, I'll be happy to look into it further. Also, if anyone else reading this has any insights, please chime in! 👋
Thanks so much for this information! Mark Bensette Aux Bois 🇨🇦.
Thank you!
@@KadForward Your so very welcome 🙏 ☺