MegaCommand // MCL 4.43

X2 :slight_smile: would allow for interesting slot structures for sure!

Same problem for me…

Yes, some work needs to be done here.

I suspect this can be solved by adding a pattern/row length feature. Tracks loop until the row length is reached, then they transition to next slot. That way the user only has to set a length for the entire row and not adjust each slot’s length individually.

2 Likes

I think that could be a good solution. But then I wonder if the “QUANT” parameter would still be useful? A bit confusing…

Wow! This project has come such a long way in the last year - the integration looks fantastic.

Looking forward to future updates but it already feels like this project has addressed most of the features that were sorely missed in the original firmware.

Thanks to Justin for all his hard effort. I feel super lucky to have dropped in when there’s units in stock on his website. :slight_smile:

J

1 Like

Hello! Is it too late to buy a MegaCommand controller?? :slight_smile: I can’t figure out any of the links on here lol
Thank you!!

Just picked one up from here.

2 Likes

When in Mixer mode and holding Load and pressing a trig button the Mutes seem to toggle on/off, but when holding the Save button to do the same with the Solo it seems to latch and not toggle. Is there a way to unsolo, or am I missing something?

I’m having some trouble getting my MD (OS X.05C) to recognise the Megacommand (4.04).

A peering message shows up when I turn the MD on and tempo is syncing (master clock from DAW), but MD is not switching to enhanced mode and I’m unable to toggle it on manually.

Load / Save / Grid messages are displayed on the MD when using the Megacommand, so they seem to communicate at least partially.

Any settings on the MD and MC I should look at?

what mk MD is it?

UW+ mk2

Bad midi cables maybe?

1 Like

MIDI communication problem. Try another set of cables. You could try reducing MCL -> Config-> Turbo 1 , but for the MK2 it should work at 8x.

1 Like

Silly me, appears none of the midi-cables that I tried yesterday work correctly for this purpose, they are passing clock but maybe not all the messages it seems… Had to take one from another machine and now it’s recognised. thanks :slight_smile:

7 Likes

MCL 4.10 Released: :rocket:

Download

Changelog

Highlights:

  • Monomachine driver fixed.
  • WavDesigner Fixed,
  • Bulk pattern import
  • Bulk sample send/receive.
  • Program Change In/Out
  • Dedicate MIDI Channel for Poly Voices.
  • Numerous fixes and stability improvements.
17 Likes

HUGE.

Creating sample folders titled with relevant MCL project names and using bulk sample send/receive from said folders now creates a (pseudo rom snapshot) import project specific ROM opportunity for non +drive UW users.
:clap: :headphones: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1: :+1:

edit: you don’t have to title the folders to link to projects, just helps me keep track. :slight_smile:

1 Like

Fantastic update. Certainly couldn’t come at a better time, I just picked up the MCL again. I’m so glad that so many bugs were fixed and the new features and changes look incredible. Great work!

One new feature jumped out at me that I think should be tweaked:

 Config -> Midi -> PRG OUT sets the send channel for Program Change messages, which are sent when loading slots or rows.

Probably shouldn’t send PC when loading a slot. This would cause other devices to change entire patterns when there was only a slight change to what’s playing on the MD.

1 Like

Do you need a UW version still to use samples or has the MCL (don’t have one yet) given any MD sample access?

still need UW

1 Like

Isn’t it that the original just doesn’t have the physical RAM for it?

Wonder if they can be upgraded… :nerd: