Once again, a heartfelt thank you to @JustinValer and everyone who’s been working on getting all these amazing features on the Machinedrum. Your effort and dedication is so much appreciated! 
2 Likes
As someone who sold his MCL,
(And after having conditionals and individual track length on the MNM)
Seeing all these posts on X.13 thread instead of MCL thread…
I got seriously disappointed, thinking I was about to have those features on the MD like on the MNM. But oh well… I guess I’m getting spoiled hihihi
2 Likes
I gather these are seperate projects? If so wonder if they will have a go at MD or not stepping on each others toes
1 Like
@JustinValer - you are a nutter. Many thanks!
1 Like
Getting individual track length natively on the MnM was unexpected and quite the gamechanger. Not that I dislike the MCL, but if the MD could ever also have indiv track length natively that would be a dream. I often use the MD standalone on the couch and the need for a dongle for that is not ideal.
5 Likes
I’d really love individual track length natively on the MD. I got the MCL mainly for that, but also to explore all the other features. I really admire the scope of the MCL work, but I underestimated the time I’ll need to get oriented enough to eg easily save and reload kits in patterns (this is my bad to be clear, MCL is a deliberately galactic flexible tool and I admire it for that, moreso when I get a break from life to explore it).
3 Likes
Ok ok ok follow up post, I spent a few hours and now flying with mcl. As always with learning a new thing I now can’t even remember what it was that I thought was hard.
2 Likes
How wow 16 more LFO \(^-^)/
I was just working on a track that needed swing 4 days ago and discovered earlier MCL versions had sacrificed that. Can’t wait to upgrade my MCL (^–^)
1 Like
Is this for MD or MNM? I’m a bit confused by some comments around this. Thanks
Machinedrum enhanced mode with MCL
4 Likes
I just upgraded from X.12 to X.13 and found a big problem with external sync. Currently the MD is receiving clock from my AR but the tempo is going wild and patterns are completely out of time when I press play on the AR. If I set the clock to internal it’s steady. The clock on the AR is a stead 140 without deviation. I can check this because further along the chain is a A4 which show the speed of the clock coming in to the machine from external and it’s all over the place. I find this baffling because X.13 is supposed to “Fix external MIDI clock sync regression” whatever that means but it’s clearly introduced a problem!
Also Transport is not passing through the MD - when I press play on the AR the MD plays (out of sync) but my MM and A4 don’t play. When I press play on the MD those two machines do play.
This video shows the clock on the A4 receiving a signal via the MD
Help! How easy is it to downgrade? Do I just load up X.12 again?
I’m having the same issues when receiving clock from the MM or A4 so it’s definitely an issue with the MD. Urgh 
Haven’t been able to replicate what you’re seeing. I have my A4 connected to the MD via MIDI in and OUT, clock is stable both ways.
Would be worth doing a soft-reset on X.13 after upgrading to see if that clears any latent setting.
In your video, is anything else connected to the A4 or MD?
Please test in isolation. A4 → MD to start with, then slowly introduce the rest of your setup until the problem appears.
2 Likes
I was troubleshooting last night with Waftlord on the discord server and I tried pretty much every combination and got the same results. If the MD is receiving external clock the timing was going crazy. My initial setup chain is:
AR MKI
MD MKII UW
MM MKII
A4 MKI
It’s handy that the A4 shows the BPM even when receiving clock, whereas the MD and MM just show “EXT”, but you can see the tempo LED on the MD flashing erratically.
I tired getting an external clock from Logic into the AR too and that made no difference. In the end I downgraded to X12 but I wish I’d thought of the MIDI reset thing before. Everything is back to normal timing-wise, but I’m having to use MIDI-Thru on the MD for the transport controls to pass through (When I press play on the AR, everything plays), but because of this when I press play on the MD, the two machines further in the chain don’t play. I can live with this
I installed X.13 and had the same issues as @Arsey_Rob. I’ve had my MD (UW mk2+) synced to my Squarp Pyramid for years with no problems. But after updating to X.13 the playback on the MD went bananas. It acted as if the clock was consnantly speeding up and slowing down and was totally out of sync with everything else. I did a soft reset, but that didn’t help. I downgraded to X.12 and now sync is back to normal.
1 Like
Would be useful if someone can help troubleshoot on the discord because I havent been able to replicate the issue. It may be a configuration setting/combination I’m not running or haven’t tried.
2 Likes