Maschine 2.0 & Ableton

I've come up with a method to 'drag and drop' a drum kit into Ableton and have it play back your Maschine kit without messing around changing individual sound MIDI settings in Maschine. It transmits the MIDI back to Maschine on a certain MIDI channel chromatically from C1 (which is the default group MIDI input setting in Maschine). I'll post it tomorrow when I'm not so tired and I've tested it a bit more.

 

looking forward to seeing this.

sowari

 

I've decided to "cheat". I have my drums on 1.8 (happy with that for now) keeping the old functionality. I then have my vst's fed through 2.0 for now and hopefully I can sus out whats going on with the encoders and macros.

It wont be the most efficient and flipping between 1.8 and 2.0 is a bit of a hassle but at least Im getting the functionality back in the direction I wanted.

With this thinking, I suppose you could play out a beat on 1.8, recording the midi directly into Live and then just copy the clip over to 2.0.

 

Macros thing now sorted - they now load as they should do which is great. Not sure what was going on there.

My template is now per the above. Pretty similar to what everyone was using with 1.8 & Live. Within 2.0 is it possible to have automation recorded on each of the groups mapped to the corresponding Lives track? I worked out how to record automation on the main Maschine track within Live. Or at least, I worked out that is where it maps to when I switch automation on to host but what I was hoping for would effectively be x number of automation groups, one for each track in Live. Is that posible? At the moment, all of my automation sits on the master track in Live.

 

View attachment MAS2MIDI.als.zip

I'm about to fly out the country for a week, so I thought I'd post the .als anyway.

Drag it into your project, and set the output of the MIDI>MAS track to your Maschine Plugin track, choosing the MIDI channel you want to output the pattern to Maschine on.

Then drag and drop your MIDI from Maschine onto the 16 tracks labelled [1] C1 to [16] D#2 - these refer to your 16 pads in Maschine. If all 16 pads in Maschine have a note in, then you can just drag to [1] and it'll be formatted right. If there are less than 16 pads with notes in the original Maschine pattern, then you'll have to rearrange the clips in Ableton because the export 'bunches up' the clips.

Go to the GROUP > CHANNEL > MIDI > INPUT in Maschine, turn ACTIVE on and select your MIDI channel as per MIDI>MAS in Ableton. You should now hear your kit playing.

What does it do? There are 2 scale devices on every channel, the first one lowers the pitch 128 semitones and the second one raises the pitch to C1 or D1 or whatever. This means that the notes all play the same pitch so you won't have any chromatic notes playing different instruments in your drum kit. They all then get bussed to the MIDI>MAS channel, which has the effect of merging all the MIDI to a single channel (because Ableton is rubbish like that). Consequently you are then putting out a single MIDI channel with 16 chromatic notes back out to Maschine.

If you want to edit all 16 tracks in a single piano roll, then you can record the clip into MIDI>MAS, then delete the 16 pad clips.

 

Good Work!

It uses up all 16 midi channels though. If you want to trigger another kit you can do it but if you want to trigger a sound, say a bass, (in keyboard mode) then the drum pattern will trigger the bass, no?

Or is there something I'm missing?

 

No, because the drag and dropped MIDI is bussed to the MIDI>MAS track, Ableton merges the MIDI onto one channel. Consequently you are only sending back MIDI to Maschine on a single channel (which you select in the MIDI>MAS track).

 

Awesome yeah I see. I set it up wrong the first time.

Thats a great workaround. Thanks for sharing!

 

No worries man.

 

I just posted the below in this thread. http://www.native-instruments.com/f...intrument-in-Cubase-causes-midi-feedback-loop

IMO, this new MIDI behavior is correct. If you try to send MIDI in and out on the same port, you will get a feedback loop. I think the reason this problem did not happen in 1.8 was that Maschine's sequencer did not send MIDI out unless you selected a MIDI out module. When you did that, I think the MIDI in was thereby disabled, thereby avoiding the feedback loop. There's a tradeoff it seems: With the new MIDI functionality they've given us, the old trick (of recording MIDI from Maschine's pads into your host's sequencer, which in turn triggers Maschine's sounds) NO LONGER WORKS. That's fine with me, because I'd rather have the more powerful MIDI offering, which allows Maschine to send MIDI from its sequencer. See also: http://www.native-instruments.com/f...e-s-sequencer-give-out-midi-notes-to-the-host Maybe they could add a "host performance mode" button or something, which would allow for sending and receiving MIDI on the same port but internally route the MIDI in such a way as to avoid a feedback loop. They key would be to allow users to turn that on and/off. The option. The flexibility.

That said, I PRAY they do not change the new MIDI functionality too much, because it's way more powerful now.

 

Perhaps 2.0 is more powerful but it has become far less useful for myself and a fair few others it would seem. It's verging on being a deal breaker for me but thankfully my workaround using two instances of Maschine (1.8 for drums, 2.0 for vst's) is working well enough for the time being though with some obvious inconveniences.

Like you say, the key would be to provide the option or to be more flexible but perhaps this might be an issue with how the 2.0 architecture was designed and built. I dunno, but hopefully something can be done.

 

Today I tried again more then an hour to setup Maschine 2.0 into Live in order to drag & drop Midi from Maschine groups into Ableton. Again no Luck with this idea.
Why do things so complicated?
Is this even possible to achieve at the moment or are we forced to wait for a fix?

 

Wait for a fix.



( )

 

having problems mapping Maschine 2.0 to ableton's drumracks.

can't seem to make it work like 1.8. where the 16 pads in push are playing the corresponding sounds.

Now when I select the first pad's sound eg the kick in maschine 2.0. Push's pads will play only that sound but pitch up as it goes from pad 1 to 16 and not different sounds.

anyone knows a fix on how it can work like 1.8? Cause this is really making me stop using 2.0 after the upgrade. Thanks for any info.

 

sadly for me i won't be using 2.0 because of the bad midi problems as everyone else is complaining about.

the amount of stuff you have to do just to drag a pattern from maschine to ableton is just stupid.

1.8 for me.

 

I've reverted back to 1.8, spending more time making music than messing around trying to fix what seems to be a feature in 1.8 many would like to have function exactly like it had.

1.8 for me too

 

i am confused here

are you trying to set Push to play a kit loaded into Maschine 2?

or trying to get the Maschine Pads to play sounds in an Ableton Drum Rack.

if you are trying to get Push to play a Maschine kit, use the Group MIDI In.

sowari

 

Yes... trying to get PUSH to play a Maschine kit. Sorry I'm not a native English/American speaker. So a little difficult to put my thoughts across.

Can you elaborate on the GROUP MIDI IN?

Thank you so much
どうもありがとう

 

this:



and 8.2.1 Triggering Sounds via MIDI Notes in your manual.

sowari