Maschine 2.0 as plugin in a DAW w/o internal sequencer

onother problem with studio one:
one track in studio one set to midi chanel 1, output maschine2. A1 in Maschine, group midi is set to midi chanel one 1. fine it works.
next track in studio one set to midi chanel 2, output maschine2. B1 in maschine, group midi is set to midi chanel 2, don´t work.
switch from midi 2 to midi chanel 1 in maschine the sound from B1 is playing. but the B1 group is recieving the midi data on mdi chanel 2 too, the keys are lit up.
it seems maschine2 is not multitimbral in studio one ? !
regards jan

Studio one 2.6.1, maschine 2.05, win 8.1

edit: i tried the same in cubase 7.5 and it works as it should be.

 

Is that not because of limitation with Audrey and RTAS/ProTools though?

Maybe some more clarification is needed by Vathek of what is wanted, but you can send MIDI notes live or sequenced from the pads in Maschine control mode as far as I remember. For some special MIDI control I use, it's pretty important it still does this (and it does). The change is that the old MIDI out module is not required to sequence MIDI.

However, after the exchange here, maybe I have misunderstood the feature need here...

 

what is the work around for this in 2.0?

 

Hmm, all I would like is for whatever I drum on the pads in Maschine to show up as MIDI notes in my host DAW. This was easily accomplished in V1 but as it seems is not possible in V2 anymore. But you seem to be saying it still is, how so?

 

How do you send midi in 1.8 while drumming pads? I thought it HAD to be in midi-mode.

 

Again, unless I'm misunderstanding, set the outputs of all sounds in a group to send to the host on the same MIDI channel and set up a track in the host to receive the MIDI from the Maschine track on the same MIDI channel. Different hosts work differently, but you should now be able to monitor the MIDI from Maschine and therefore record it.

To my knowledge, you could do this in 1.8, but any sequence would not continue to send out MIDI (unless transferred to a sound with a MIDI out module). Basically, 1.8 allows live pad playing to be output as MIDI from a normal sound, 2.0 allows live pad playing and sequences (patterns) to be output from normal sounds.
If that makes any sense...

 

I'm on holiday with no DAW near, but if I recall correctly it had to do with what I mentioned before (sounds to MIDI notes), at least it worked in Presonus' Studio One. Don't know about other DAWs..

 

Really? That would be what I'm looking for! It'll be another 10 days before I'm back in my studio, but I'll check!

 

midi TO pro tools? please assist

Got Maschine studio for Christmas (yay) but having a cow of a time trying to figure out how to get midi to appear in pro tools FROM machine. There is very little about this online, sowari responds in another thread but bascially I jsut am not following how to do it, having read the relevant part of the manual over and over and online searching etc. In short (without trying to justify WHY I need to use Pro Tools sequencer instead of Maschine's software for sequencing, but one reason is FILM MUSIC...I need to keep track of the VIDEO alongside the sequence even if loop based)....would like to create the beats and use the pads on maschine (note repeat is awesome!) but have all that appear as midi notes in PT once I hit record in PT. I just CANNOT seem to get this to work (maschine studio / maschine 2).

COuld someone tell me it can be done (IE I'm just not following) or if it CANNOT be done (so I can get some sleep instead of staying up all night several nights trying to crack this) Thanks!!

 

Have you set your midi outputs for each Group/Sound?

I've got it to work in Studio One with little trouble. I'm on my laptop now, without my controller. But I was able to record each group/sound to it's own track in Studio one by loading a demo song & letting it play in Maschine. It worked as expected & leads me to believe I should be able to hit record in Studio one & trigger my scenes/patterns from Maschine & have it record in Studio One. I also imagine I would be able to mute patterns/sounds & record automation from the controller... but I would think it would record that automation as midi CC & I'll have to figure out which CC is which parameter.

I also tried it in Live & it didn't work. In Studio One I was able to choose Maschine as a source & each individual channel. I can't see a way (yet) to do this in Live 9. I set it to record all inputs & each individual channel... still no joy.

If I get a chance, I'll try it in ProTools 10.

 

This is what I would like to do in Cubase 7 as well. I bought Studio for the spontaneous ability of the controller, which I like a lot. It looses an important part of the spontaneity if you can't record patterns/scenes changes in the DAW from the Maschine Controller itself. This ability is at the top of my list...

 

Hey Guys!

I think this might help you guys out… works for me, and still has similar workflow.

http://www.youtube.com/watch?v=r8_7zRVbDFA&feature=youtu.be

 

Pretty cool, but still a workaround. I just don't understand why NI won't let this be done more easily. I'd be so simple to implement a "DAW sequencer" mode where Maschine sends its MIDI to the DAW and the internal sequencer is disabled. I don't get it, NI. Let people work how they would like, what would you lose?

 

That would not be simple at all. When Maschine is hosted in a DAW, the DAW handles all the midi I/O routing. Each DAW handles this differently and it is up to your DAW and how you setup your tracks what it records and how it records it. The workflow for recording scenes to your DAW simply can't be automatically setup without you creating a DAW template. All Maschine can do is allow external midi from your DAW track to trigger the scene changes as it does now. The rest is beyond the control or scope of the plug-in.

It's up to users to create templates for various DAW's and workflow configurations and share them.

I want to make clear I am not speaking of the missing sounds to midi notes setup that would be done on Maschines side. Also, the other issue discussed here where you could trigger Maschine in control mode without a feedback loop in some DAWs that support plug-in midi out. That worked in 1.8 but is no longer possible. These are things that NI have control over and hopefully we will see improvements to restore 1.8 functionality.

 

I think I was not really being clear. What I would wish for NI to do, is to have an "external mode" or whatever it would be called, where Maschine is simply a drum sampler/synth with a dedicated controller. This must be easy to implement, as it's been done by several companies.

Also it was possible in 1.8 (at least in Presonus' Studio One), so it must be possible in general.

I'm not talking about recording scenes into a DAW or anything like that.

 

I see. That was the last issue I mentioned where you could trigger Maschine's pads from control mode and record it in your DAW without needing to flip to midi mode. The issue here is that when your sounds midi out is not enabled, pad input is also off. If you turn midi out on for sounds, then both pad input as well as any other midi is output and causes a feedback loop. In 1.8 it would send pad input to midi out even if there was no midi out module. All other midi out was off so there was no loop. Hopefully they fix this.

 

It's funny when you are fortunate enough to talk to someone from NI, their standard answer is that 2.0 is more of a new application than it is an improvement of 1.8; they started from scratch. Things weren't taken out of 1.8, they just weren't built into 2.0

Why?

 

It must be because they didn't fully take into account all of the features that were present before. I'm hoping that these get re-added.

 

I seriously want this too, big time. I have no need for scenes or patterns at all because I use a DAW!

 

Well, the tutorial I posted gets the job done. It's about as tedious as setting up 1.8 in Ableton to record MIDI straight into Ableton as well as bussing audio to individual tracks in Ableton. In my book, it works all the same.

I suppose it might be up to preference though. Maybe you guys just want a quick and streamlined process of getting to the same end.

It's true though. Making and saving templates for various purposes will help "streamline" this process for future use. (Once I set mine up I saved it and never had to mess with it again.)

With that all said, I just want to say that I'm not debating anyone here, or anything like that. I'm merely showing you guys one of a few methods of getting that desired functionality. It's up to you to use it.

Much respect dudes!