[v1.5.0] MASCHINE MK3/MIKRO MK3 Ableton Live 11 MIDI Remote Script (Unofficial)

... and / or a small manual?

 

I am so glad that it worked and thanks for the information! As for 1.4, I don't think it will have a Chord function just yet, I have to think about it and it's complexity. Thanks!

 

Yes I will work on that as soon as I release 1.4 (soon), because I have to include that to the manual too.

 

Hello everyone,

This is just a preview of how the Manual will look like, I will make many pages to cover all the modes (CLIP, SCENE, TRACK SELECT, DRUM, KEYBOARD and possibly a new "RACK" mode for JOG WHEEL controlling up to 16 macros of the selected rack or device parameter).

I have no idea how long this might take. I could easily write a manual in markdown or simple text but I don't know how understandable that would be, however.

Please let me know

 

Hello Elton,
That looks good!
Besides explaining that single functions like CLIP, ... TRACK SELECT etc. I would add a small example of the intended workflow, e. g.:
- search for the right sound,
- set the tempo
- arm the track
- switch to pad or keyboard mode
- start the metronome
- record a single clip
- stop recording ... and be happy

With your script I can use Ableton's own drum racks / kits, NI's VST2 plug-ins like BATTERY 4, MASCHINE or even Toontrack's EZdrummer 2 all within Live 11 and that's great.

What puzzles me is the MIDI Mapping of the respective drum sounds generated by all that fancy tools to the "right" pads.
However I think that this question is far beyound the the scope of your work. Obviously everyone has to investigate that topic and find a solution that corresponds to one's individual needs.

 

I had the same issues and I somehow managed to do some routings between Maschine and Ableton. I might prepare a preset for this and share it perhaps on a dedicated thread here at Maschine Area. I mostly use drum rack but when I use Maschine Expansions (Maschine as VST2 plugin), I do the routing for that.

Thanks for the suggestions about the workflow in the manual. I am thinking the same about it.

 

By thw way`:
I noticed that the last Live 11.0.1 update obviously deleted the folders `_NativeInstruments` and `Mikro_Mk3_Unofficial`. I had to copy that folders into their parent folder `...\Resources\MIDI Remote Scripts` again.
Do you have the same experience? If yes then it's worth mentioning in the manual as well.

 

Thanks for telling me!!

I didn't update yet to v11.0.1.
I will update the manual and installation guide in order to use the Live 11's new path for Remote Scripts which is under User Library (also the new "Templates" folder for Sets lives there too).
v1.4.0+ will no longer have "_NativeInstruments" folder, the script has no dependencies from there anymore due to the mass rewriting and refactoring that I made lately

 

Hi Elton,

Just bought your script to use with the bigger MK3, and after some mucking around (and using your Controller Editor template as a starter) I have it all working beautifully. So nice to be able to finally use Live 11 with the MK3.

A couple of questions:

- If I'm Session View I hit the MK3 REC button to enable session record so I can record an idea into a clip slot. Then without stopping Live I can normally disable session record by pressing it again. This doesn't seem to work in this script? I miss this!

- The old Live 9 Legacy script had a plugin mode where if the Plugin button was pressed the MK3 encoders became the 'Blue Hand' instrument/effect macro knobs. This was SUPER awesome so just wondering if you could hack that part of the original script into yours? If you do this would make your script fantastic for both the Micro MK3 and the standard MK3. Fingers crossed you can port that across!

- Is there an undo/redo in your new script? The Legacy script had them placed at Pad 1 and 2 if the shift button was pressed.

GREAT work so far! Keep it up.

Cheers
Jed

 

Thanks for purchasing and using the script.

Unfortunately, I do not own the MK3, thus I cannot test and develop encoder "Plugin mode" in the script
As for the Undo , Redo, etc, please press "RESTART" + "PAD 1" or "PAD 2" (restart is the undo button)

In the upcoming release, more RESTART + PAD combinations will be available, such as transpose semitones or octave, nudge, clear selected or all notes, clear envelope, quantize and quantize 50%, etc.

As for the Disabling Session Record without stopping live, I faced the same issue and I developed something in the script but I didn't release it yet, as I was unsure about it.
So the idea is to just press record button again to stop the recording mode (either Arrangement or Session).
By the way, you can trigger Arranger Recording by RESTART + REC button combination.

I will consider this recording issue and will plan to release it soon

 

Elton, you are a star!!!! I just bought your template and it's brilliant. Seriously, this is a huge deal for me. I've been struggling for MONTHS to get my mikro to work in Logic as a simple midi controller, without going through Maschine as a plugin which I find very cumbersome and not a creative workflow. A few days ago I discovered Ableton and I'm totally sold, I love it. And now here is a terrific solution to using my mikro in Ableton. I can't thank you enough !!! I'm so happy I'm going to go write like 10 songs right now... Cheers!

 

I am so glad for you! Thanks a lot

 

Hello Elton,

I'm just implementing a small Ableton Drum Pad template for my Elton powered MMMK3 in order to use NI's BATTERY 4 and Toontrack's EZdrummer as VSTs within Live 11.

I looked for an efficient way and found JesterMgee 's splendid tutorial:

Jason, for that video you deserve further 100.000 clicks. In that context this is the best tutorial I've seen so far!

It seems that MASCHINE's "standard" is to allocate C3 to pad 1 whereas Live's DrumRack pad 1 starts with C1. However that's not an issue because one can easily shift Live's DrumRack matrix and it's key note from C1 to C3.

At 7:30 Jason starts explaining how to name and color the pads.
I found that the colors of MMMK3's pads differ from that what I see on my screen or what you can see on JesterMgee's Push.
That's not a big issue because it's more important to me to have different colors for the kicks, snares, hihats and so on. However it would be nice to have similar colors on the pads as well.

Elton, do you think it is possible to align Live's and MMMK3' pad colors using your script?

 

Yes!
The colors are automatically generated based on pad name, for kicks or bass it is Red, snare is Blue and so on. I will make a change if the chain doesn't have a color, I will use this automation, otherwise I will use the chain's color. I used to make that way because most drum racks that I create don't have colors for each pad, that's why . I will try to make this change ready for v1.4.0

Thanks again!

 

Hey there, MK3 owners!
I would like to ask, can you record a short video of how all of this is looking on Maschine MK3 screen? No need to go deep, just like couple of pages of script is enough.
If you have a little bit of time, of course

 

Hello,

An update to this:

I realized that the chains (pad colors in Live's DrumRack) always have a color, defaults to track color, which means, in the script I managed to handle this by having two "modes" in Drum/Pad mode of the script, as follows:

SHIFT + PAD MODE => Enters the Drum/Pad mode of the selected track to use automatic coloring based on pad name (feature as-is in v1.3.0, for example Kick or Bass names are with Red color, etc).

PAD MODE (without holding shift when entering) => Enters the Drum/Pad mode without the abovementioned automatic coloring, instead it will use the chain's color, just as you wanted

I will include this to the manual as well. This is planned to be released on v1.4.0 alongside with a lot of new content and improvements.

Note that if you already are in the Drum/Pad mode and want to switch between automatic coloring or showing color of the chain, you must go to another mode (i.e.: PATTERN mode) and then go back to Drum/Pad mode either holding SHIFT or not (depending on what you want the coloring to behave when switching)

I will try to find a way to "remember" the last selected mode (either automatic coloring or giving color of the chain to pads) when the selected track changes (i.e.: going from a non-drum rack track to a drum, and vice versa)

Edit: Found, a better approach (which also works well technically) is to toggle between modes by entering DRUM mode while holding SHIFT (Restart button). I will include this in the manual.

Sorry about this long and confusing post, please let me know what do you think.

Cheers,
Elton

 

Decided to simplify it this way:

When entering the DRUM mode for the first time, I check the visible drum pads (selected 4x4 pad grid), I check their colors. As soon as I find one pad, whose chain's color is different from the default one (track's color), I immediately make the default coloring "strategy" to be the "use chain colors and not automatic based on pad name". In short, if a drum rack (most user-made presets) chains that have no custom colors, the MMMK3 will have it's default coloring strategy "automatic colors based on pad name".

To change the mode, simply do the SHIFT + PAD MODE combination when in DRUM mode, the colors will trigger automatically and, of course, this selection will be remembered when selected track changes, device changes, etc.

This is the algorithm for the automatic color based on pad name, so you can have a reference on how to name your pads:



For example, "kick, bd, bassdrum, 808, sub or bass" words in a drum pad name will have a RED color in the MMMK3, and so on.

I will include these details in the manual as well.

DeepThumb

Thanks again for the idea of adding support for "Chain color to pads" on DRUM mode!!

 

Hey Man I have a Maschine Jam too and updating to live 11 you can understand my frustration when I see no script for it and unfortunately I have 0.1 understanding of programing so it would mean the world to me if you can share your work with me and I can pay you a few boxs if you need to

 

Hey Man I have a Maschine Jam too and updating to live 11 you can understand my frustration when I see no script for it and unfortunately I have 0.1 understanding of programing so it would mean the world to me if you can share your work with me and I can pay you a few boxs if you need to

 

Yes! I don't understand why NI and / or Ableton don't outsource the development of that scripts. Elton shows how fast one can get decent results.

If it was my business I would give him every Maschine HW and licence for free and pay him an appropriate fee. Job done ...