Maschine still painful when using DAW's

Maschine (VST) wipes out your settings when adding a drum kit. This makes life a pain having to set up the audio everytime we use a drum kit.

For background:
http://www.native-instruments.com/f...ing-settings-daw-looping.257244/#post-1394566

1) What is desperately needed is the ability to save the group settings (that is for example MIDI and audio channel settings only) ONLY to a template, which we can later apply to any newly loaded kit (which will delete any settings it might have had originally).

2) Not only that, we should optionally be able to apply one of those templates to any new kits we might drag into Maschine by default (this would be set up in preferences). As an additional option we could have a tickbox which allows the user to confirm the behaviour. Finally we also need to be able override the behaviour (such as a control drag).

3) We also need a Group audio batch setup facility which will change audio destinations for sounds from Ext. 1 to Ext. 16 in a few clicks.

4) Nice to have - ARA functionality, this is a killer feature and more and more DAWs will support this.
http://en.wikipedia.org/wiki/ARA_Audio_Random_Access

 

The results of 1 and 2 are surely needed, but what I would personally prefer would be an extension of the +PAT functionality to include +FX (option for loading/replacing the Group-level effects), and +ROUT (option for loading/replacing the routing), if you will. This is similar, but just a slightly different way of implementing it within Maschine as it already stands. However, it should also be possible with the mouse.
This way, users just save kits as usual (which include all the current settings), but then the option comes when loading, as with Patterns.

 

Bump

 

I agree . The 1st 3 are really needed now

 

If you want it please press the LIKE button on the opening post..
(Well assuming NI are paying attention, I don't know if they do or not).
Cheers...

 

I'll bump this roughly once a week until they fix this

 

Even at 2.3 Maschine is still a mess when using a daw. Loading a group still resets sounds to midi notes. Input midi "thru" still randomly resets itself . NI ,JUST MAKE A DAW MODE FOR MASCHINE. Please

 

Totally agree, it's a real pain since 2.0

 

Yup. Another bump.

 

Look....take an the development staff and head over the Ableton's office, eat some strudel drink some Hefe Wiess and fix these Machine DAW problems.

 

Weekly Bump...I will be selling my NI products in January 2016 if this is not corrected.

 

I am also incredibly frustrated by the lack of easy integration into my DAW. I love the features of Maschine, but its ended up as a very basic and overpriced midicontroller. Please fix this NI!

 

This!

 

I just ordered Push so I can have some amount of control over my DAW. It does however lack some of the awesome features that made me purchase Maschine. If I had only known then that I would never make a single track in my DAW utilizing those amazing features. C'mon NI, there has to be some way to make this just even a little bit easier without a whole lot of effort.

 

Sequencing inside a sequencer is just too much.

 

Writing entire songs inside maschines sequencer is not a good option. I just want to have maschine send and receive midi to the Daw. I dont see why thats not the most basic of features.

 

Hmm maybe (1) partially resolved in 2.3.1?
'Group / sound routings no longer removed after loading a new group'.
Haven't tested it yet...

 

Yes, we can now change kits without Maschine reseting every the MIDI IN/OUT/THRU. However, the MIDI BATCH is still not remembered so if you change a kit you must highlight all of the sounds in the kit and change the MIDI Batch settings if you want to continue adding to your beat with the new kit. It is a start, but it is still not 100% there. If someone can confirm this for me that would be great.

 

If they allowed us to control the Komplete Kontrol VST from Maschine (and then included the Maschine patches in the Komplete Kontrol VST) it would solve most of my headaches

 

Maschine controller with 2.3.1 is next on my shopping list but I'm holding off buying it until this is sorted out. As another poster has pointed out, a tiny in-plugin sequencer is no good for big production projects making extensive use of audio, third party plugins and other virtual instruments in the DAW environment. Lots of workarounds yes, but fiddly and no decent workflow. It baffles me that DAW integration is so poor in Maschine when NI are probably the biggest producer in the world of virtual instruments that integrate pretty seamlessly .