MIDI file export or MIDI output ports

I started a similar thread in General forum, but I'll repeat it here in the interest of keeping the idea in play.

Please implement the ability to export MIDI files of patterns created in Maschine or to stream MIDI info to a host when using Maschine as a plug-in so that it can be recorded and edited by other means.

It would be a big plus for many of us if there were a way to easily extract drum patterns from the Maschine software for external editing or use. I know that NI would like for users to do as much work as possible within the Maschine environment, but the fact is that users of drum machines, groove boxes, etc. get a lot of mileage out of driving other gear/software with the patterns they make using boxes covered in blinking buttons.

I do realize that Maschine can also be used as a generic MIDI controller and that's a great benefit, but I'm talking more about opening up the Maschine software so that a user's programming efforts are not confined to that world alone.

It's been suggested that externally slicing audio exported from Maschine is the workaround for this, maybe for some, but it's hardly efficient if the goal is primarily to preserve the note placement, velocity info, etc. that is available via industry standard, love-it-or-hate-it MIDI.

 

+1 I agree. In it's current form integration is very limited. I would also like to see midi in from the host for more than just the selected sound. Which would be needed to use the exported midi files anyway.

 

Expanded MIDI in could be good, as well.

Just to be clear, I'm not talking about using exported/recorded MIDI files to drive MASCHINE at all. I want to have easy access to the patterns so that I can use them with everything else - hardware, other software, whatever.

 

I see what your saying. Needless to say they definitely need to open this thing up for multiple work flows. So much potential.

 

+1 from me too ...

I'd definitely like to at least export Standard MIDI files and, better still, drag out MIDI objects directly into DAW tracks from the Maschine GUI (like Addictive Drums and Styls RMX).

Definitely MIDI Import too is essential since this provides as mechanism to transfer studio produced tracks in DAWs not so suited to live performance for use in Maschine standalone.

Cheers

 

Hosting KoreSounds (or sequencer tracks output to MIDI ports)

Hi Maschinists,

It's a no-brainer suggestion for a future update, however I'd love some means of sequencing KoreSounds from within Maschine's sequencer. There are so many superb sounding KoreSounds in my collection and I've love to not need to open Maschine inside of Live (or other DAWs) in order to sequence with these sounds.

Perhaps implementing the ability to send any Maschine-born sequence data to a MIDI Output bus could provide a quick and dirty means to accomplish this by launching Maschine instances within Kore2 standalone? But then, we'd probably expect to attach commands to each sequence in Maschine to rapidly change from one KoreSound to another (I can definitely see some complications there).

Otherwise simply allowing Maschine MIDI tracks to output to any virtual (or physical) MIDI port and Channel on the system (e.g. MIDI Yoke on Windows) and leave the user to sort out the details (user can launch Kore Performances with Multi's set up) and hope the user has a multi-client audio interface allowing multiple ASIO applications to access different ports on the audio interface simultaneously.

Cheers!

 

for my needs, i want Maschine to send MIDI out to other plugins when i use it in Kore2.

sowari

 

same here,if it can do that i will buy it instantly.

 

+1

I would also like to be able to drag/export out MIDI patterns directly into DAW (just like Stylus RMX and Cubase 5 Beat Designer)

/K

 

I would also like the ability to apply "groove templates" from existing MIDI files.

 

+1
Yes! Midi output to drive other VSTs in your DAW. Holy crap. That would be rad.

 

+1
Machine output to other plugins in Kore 2 or your DAW for that matter.

That would be amazing.

 

Eye, eye, captain - totally agreed.

 

+1,000

The lack of MIDI in and out is a total deal breaker for me and I suspect many others. I think the midi in was limited on purpose for copy protection but I believe this will lose tons of sales alone. No other software instrument has this limit. You can't put that type of restriction on a software instrument and not loose tons of sales because of it.

On the other side, midi out is essential for ANY sequencer. This is also a deal breaker. What is the use of a sequencer with no midi out? That takes away at least a third of a sequencers functionality. The competing products Guru and transfuser don't have this limit. BPM (for the moment) has no midi out but full midi in.

This product is supposed to be more integrated with a DAW and is actually less integrated than hardware. Even the measly 8 audio outs needs to be doubled. BPM gives at least 16 stereo audio outs. This limitation is needless. Plus no drag and drop of midi and audio files to and from host and desktop. No export slice to midi. No acidized, apple loops and rex file support. Very closed proprietary unit. Too limited. NI are shooting themselves in the foot with this.

 

+1 for midi out. It should have full 16 channel out with separate control/recording on each channel.

 

agreed. Maschine NEEDS MIDI output ports both in standalone and VST formats. It would be quite nice to be able to generate patterns to drive other synths / VSTs.

 

+1 for hosting koresounds and sending MIDI data out.

 

+1. MIDI out and export needed.

 

Yé for everything. Midi In, Midi Out, REX support, 16 channels out.
I didn't read the forums before buying it, and i'm very very very disappointed by theses limitations. Awful. Bad. Not pretty looking.

 

+1,111

MIDI in and out, please.