I do appreciate your feedback here.
I'm using PAD mode (not keyboard mode) right now with full Maschine functionality turned on.
 
> I recommend switching the Maschine controller to regular control mode 
 
You mean turn on MIDI mode where it just becomes a regular controller device (Maschine sequencing turned off) and do this just for recording?
 
Cheers...

Yeah that's what I've done so far if I want to sequence linearly. Maschine then becomes just a VST instrument. Use the browse function in regular Maschine mode if you want to audition sounds. You can also record patterns within Maschine with this workflow and just drag them onto a Sonar midi track if you want to edit them further.

If you figure out something better, let me know :)

Sanderxpander
...
 
if you want to sequence in Sonar, I recommend switching the Maschine controller to regular control mode and making a simple template (I think it's already available) with pads to note numbers. You'll also have to use a certain velocity curve to get the same response, I forget which.
 

This is what I do also. For a given Sonar project I may set up several Pad Pages in my Maschine template to drive different soft synths...as mentioned above I've been working on one for Battery. There isn't that much difference with the new version...well we have a mixer now but mostly just enhancements. Shift-Control is your pal.
 
Regards,

Thanks guys...
 
Well I think I have something slightly different then for Maschine 2 users, although I wouldn't claim it to be revolutionary.

This way you stay away from MIDI mode and get to use the Maschine  (or Cake) as a sequencer without flipping between buttons. I'll make the template public in the next few weeks. As with everything there's probably advantages and disadvantages with this workflow...

Just wish I could find a better way to transpose in PAD mode from the Maschine (like maybe a Maschine "drum map"). Certainly NI could do better here.
 
Cheers...

Looks like 2.1 is going to improve workflow (I hope), MIDI batch returns....
....and it looks like 1.x users holding on for the old features may finally get the incentive to upgrade (release is clearly targeted at them):
http://www.native-instruments.com/forum/threads/official-update-status-maschine-upcoming-2-1.80682/
 
If only X3E would fix the SOLO button issue. 

"A batch function to set all sounds in a group to the same MIDI channel and different base keys in order to export a pattern as a MIDI file."
 
I don't understand how this differs from the option I already have in 1.8 to map sounds to notes/pads.
But then you did mention not seeing that option in your 2.x software? That seems weird. If so, I'm pretty happy for sticking with my older software.

Exactly that, it is missing...

Wow. Ok, that seems like a pretty huge oversight in the statement "Note for MASCHINE 1.x Users: The MIDI page of the Input properties for Sounds and Groups replaces and extends the features of the Sound MIDI Settings and Sound MIDI Batch Setup available in previous MASCHINE versions,
respectively".
 
I can't believe they broke that feature in the upgrade, that would have really frustrated my workflow. That's the same kind of stuff that got 8.5 users so upset with X1. I hope it makes your life a little easier too when they bring it back in at 2.1.

Well clearly they rewrote the software with some features missing, there is different workflow with Maschine 2 just like there is different workflow with Sonar X. Of course some people always look at what is missing (missing is not broken BTW ) rather than what they have gained. Maschine 2 pretty much blows 1.x out of the water in most ways methinks just like X3 and 8.x, but this was the one standout issue which 1.x users were pointing to (and they were justified to do so), and that will be resolved in a month or so. I think they were previously concentrating on bugs and stability rather than features which is refreshing.
 
So next month 1.x users won't have much to complain about other than having to spend $100 on the upgrade (money worth spending IMHO). Right now you could argue 1.x users may have a point (well it's a value judgement) but not for much longer.

I think the 100 bucks is pretty fair, they've been doing big free upgrades for ages. Just surprised that they left out what seems such a vital feature for anyone who wants to use it in a DAW. And it doesn't sound like the most complicated thing to add to the program either, as it's basically an automated version of a user's action, times 16. Glad to hear they're fixing it now. I'll probably upgrade somewhere this year. I don't think there'll be a very big difference for the things I do but I'm pretty excited about the drumsynths.