Mk2s have a +drive upgrade option, mk1s do not.
As for UW upgrades I have seen/heard mds with non uw faceplates playing samples….
Do we need to flash over Midi IN or the usb connection?
create folders on the MCLs SD card, then it’s flashed using Turbo midi
I found a bug: If you have PRG OUT set to anything but “–”, right before a pattern change, the last step of the pattern doesn’t play.
I think he meant how to flash MCL. You just plug MCL into the USB port and use XLoader. I selected MegaCMD. From there everything is obvious and it worked without a hitch, MCL rebooted itself.
1 Like
Bug: When loading a project, the MD mode is set to Enhanced but erroneously displayed as Extended.
Suggestion: Leave the current mode and LEDs alone.
Also suggestion: Add dots to every 4th column in Mix mode. Would make it easier to figure out which trig keys correspond to which tracks.
Apologies beforehand if I’m misunderstanding.
But wouldn’t leaving the MD in whichever mode it is in cause a lot more potential confusion if people forget to put it in enhanced mode manually than there being a semantic mismatch displayed?
1 Like
I just think it’s simpler and it’s how I would have done it. I don’t think there’s a strong, objective case to be made that would be worth the effort. That said the default mode on connection with the MD should be Enhanced.
EDIT: OK, I just realized I posted my suggestion with the intent to defend it if I was asked. The reason is that you don’t know what the user is up to and shouldn’t assume. The UI in this case is split between two devices and despite the tight integration the user doesn’t think of them as a single device. Thus operations they might be up to on the MD shouldn’t be interrupted by MCL, even if the user themselves initiated some function on the MCL. It should do what they requested and nothing “extra”.
I might be wrong about this, still new to MCL. I put it in the same category as apps popping up when you boot Windows, stealing focus, after you’re presented with the interface.
MCL takes over all sequencing and sound storage duties in enhanced mode, effectively unifying both devices as one. with latest fw all interaction with MCL can almost be done via MDs interface. sure there’s bells and whistles that require interaction with MCL, but to differentiate modes is crucial imo as i wouldn’t know if i was coming or going without those two lit LEDs.
3 Likes
You still must be aware of the MCL’s storage model at all times. It also has its own MIDI routing.
It goes without the saying the mode state and LED’s must always be coherent, as there isn’t any other visual change AFAIK.
Update to this: I realized this is happening for me most of the time even with PRG OUT disabled. Don’t think this was happening before the update. Can anyone confirm?
From the LOAD PAGE, what value of QUANT have you chosen?
It is/was at 16.
More bugs found.
In extended mode : If the sequence buffer on MCL is shorter than a pattern on MD and you cycle tracks in step edit mode, the current page is reset to the first page.
In piano roll, notes placed at the last step of the sequence do not have the selected length if it is shorter than a step, but get extended to the end of the sequence.
The default speed of piano roll tracks is 2x. Is that intentional?
I am no longer able to rename projects. When I try it says not renamed and puts me in the root folder. Happens for any project no matter what is the current project.
When you select clear in the piano roll context menu, you don’t have to confirm the action by selecting trk or all, unlike copy and paste. Just opening and closing the menu can clear the track if that is the selected option.
think i can answer a few of these.
only enhanced mode can be used for MCL functionality. (but digging deeper into what you’re saying iirc in enhanced tracks do default to page 1 on track select)
higher resolution for midi input recording
yup, holding GLOBAL now toggles MCLs SHIFT menu allowing fast access with MDs cursor keys, releasing fulfils the chosen menu option.
3 Likes
Confirmed: Rename Project is broken. I’ll release a fix in the next day or so.
4 Likes
Hmm, makes sense.
That’s not the issue, it’s that clear is inconsistent with copy and paste in how you don’t have to confirm it.
Yeah I think I’ve seen this before. Will take a look.
4 Likes
I just cannot work out how to upload the firmware on a Mac. I have the Arduino IDE software installed (don’t know what it does tho or if I need to do anything with it) and the hexloader. I’ve tried the setting as described and then seleted upload and closed the hex file. But nothing appears to happen.
Does anyone have a walkthrough for the non technical amounts us (me!)
I would be very grateful!
There might be an issue with newer versions of MacOS…
If you’re comfortable with terminal, you can try uploading using this one liner:
FILE=~/Downloads/mcl_4_1_0.hex; DEV=/dev/$(ls /dev | grep usb | grep cu | tail -n 1); AVR_DIR="/Applications/Arduino.app/Contents/Java/hardware/tools/avr"; ${AVR_DIR}/bin/avrdude -C${AVR_DIR}/etc/avrdude.conf -v -V -patmega2560 -cwiring -P${DEV} -b115200 -D -Uflash:w:$FILE