My friend who betatests Maschine said something is finally happening with the M+ updates… No idea what that means for non-betatesters in terms of release dates, but stuff has came out of beta pretty fast earlier… I’d wager we will see a new update with a month, if not sooner
7 Likes
Interesting. I’m a beta tester for them as well, haven’t heard / seen anything myself. Good to know something is moving.
1 Like
It’s announced and confirmed as version 1.6 which is in beta since this week 
So my Machine + will be here on Tuesday. Thanks to all the nauts that answered my questions so far.
I have another question or two:
Just as I do with my Push 3, I plan to use in controller mode while in the studio, but not if I’m doing a live set. My intentions for live would be to use Maschine + and Push3 as two separate grooveboxes triggering different things.
For example, I would most likely have drones and audio stems on Push 3 and drums/rythmic things on Maschine+
Here are the questions:
-
Can you easily move multiple projects from Maschine software to Maschine + standalone?
-
Is there anyway to have a Maschine 3 project work on Maschine + standalone or should I avoid Maschine 3 if I plan to go back and forth from controller to standalone?
Thanks!
- “Easily” is a bit of a red herring here, which needs some elaboration
- Forget using Maschine 3 for now, it wont be available on M+ standalone for a while
So, about those project transfers. It is possible to open a Maschine project made on M+ on Maschine desktop, and vice versa, but only if all software versions of all included apps and plugins match. This not only means that Maschine versions on the desktop and M+ must match, this also means that all plugins one uses on both must also have matching version numbers for best interoperability. So, you need to make sure all of these have same versions on both desktop and M+:
- FM8
- Massive
- Monark
- Raum
- Phasis
- Reaktor
- Kontakt
Keeping all of these at the correct versions means you need to turn off automatic updates in Native Access, and you’ll need to manually keep tabs on these versions whenever a new M+ OS update drops, since M+ OS updates sometimes also update the included plugins. Typically, the versions offered for desktop users are a bit newer than what M+ has
In addition to version parity woes, you also need to keep track of your samples. This can also be a bit confusing, since saving a M+ project “with samples” option enabled still doesnt include all recorded samples. These will need to be manually copied from within the SD card, under “Recordings” subfolder located within the “Native Instruments” main folder.
Once all samples a project needs is copied, all the same Maschine expansions are installed on both desktop and M+, complete version parity of the app and plugins exists then yes, projects will be interoperable (As long as you dont use USER Reaktor or Kontakt stuff, which also needs to be present on both systems…)
There are quite a bit of moving parts on a system as complex as M+
8 Likes
Indeed I still do not fully understand how samples are stored. For example when you store with samples do you have to so this every time or only at the first save and then „Shift settings“(?)
Normally, each new recording (sample) is done in a temporary folder (recording) then if you record the project with the new samples, Maschine will store them in a folder with the project (you must therefore copy the project file and the associated samples folder later if you want to switch from the computer to M+ for example) Maschine then keeps in memory the path to the samples of this new folder, no need to redo the process, but make sure to do it with each new samples and that the folder is Always with the project.
I no longer know if Maschine deletes the temp folder, I think, otherwise you have to go check in the temp folder.
Note that if you make a sample and do not save the project, the new sample remains in the recording folder.
1 Like
Thank you for taking the time to explain this so well. I really love this place.
Everything regarding Maschine 2, current plug in versions, native access updates, etc. makes total sense after reading it. I will plan to follow these directions once it arrives.
I do think since it has the whole NKS thing, I may use some arturia plug ins for synths and effects and figure out how to flatten those to audio before moving back from maschine to maschine +.
The file management, sample situation definitely has me confused, even after reading your detailed response about 5 times.
Is there a Maschine file management for dummies book? 
1 Like
Cool, custom Chords feature update in the next few days.
1 Like
Not for standalone tho IIRC, just for the m3 SW
My latest JAM with the Perfourmer and the Maschine+ in standalone mode (Mastered in Ableton)
6 Likes
Hi guys,
I’m checking this out mainly as a drum machine / sampler. I used to use the Mk3 a few years ago but moved it along for various reasons, I ultimately liked it back then. I’m wondering how this has progressed since then, can anyone link me up to any good new overviews of this device, or offer opinions on where it is now as an ecosystem and experience.
I want something direct then I can fill with Roland drums and sample quickly to and make some straight up underground bangers. I don’t need huge CPU just a good responsive drum machine / production centre than can take some simple fat patterns and is nice to perform with.
I have fantasies of getting away from the computer so always looking at ways to achieve this!
1 Like
‘Drum Machine’ and ‘Sampler’ are completely different things… and to think of Machine+ like this is setting it up for a potential fail.
I think Maschine is THE best (groove)box for musical/creative inspiration if you actually play (whether that’s on pads or keys).
Loading up a bunch of Roland samples and making music would be easy on it.
I think Digitakt (II) is probably a better drum machine sampler.
I think the current MPC is a better sampler.
I think the Roland TR8S is a better drum machine.
But, Machine+ is hands down the best all round groovebox.
8 Likes
Thanks, yeah I’m using Ableton Move at the moment, which is amazing, but it dawned on me that everything I really like about the Move seems to be magnified on the Maschine. Composing on the pads is part of that.
I guess I’m just a bit bored of the inevitable Ableton. I’m happy with the tracks but I spend all day working on a computer as it is. It’s just a bit, tedious to then spend my free time doing the same thing.
The Perkons changed everything for me, and I guess I’m just chasing other avenues of hands on expressive immediacy that happens to keep the computer as far away as possible.
2 Likes
probably just my imagination but it seems like most maschine beatmakers nod their head back/up on the one, and most mpc users nod their head forward/down on the one?
5 Likes
what the fuck… i make beats on maschine and my head goes back on the one…
1 Like
It’s funny. I own all the pieces you mentioned and I agree. Although I didn’t get deep in to sampling on the MPC compared to SPs. I use the Maschine+ as my midi brain. I even recently mapped out the TR-8S from the M+ and am super exited to not be limited to the rudimentary Roland sequencer. My next goal is to delve in to sampling on the M+ but I’m worried the family of SPs will get jealous and smother me in my sleep.
3 Likes
Love the observation 
1 Like
That’s interesting about mapping the TR-8S. I’m curious - what is it you prefer about the Maschine sequencer? Feels to me that the Roland has some things the Maschine doesn’t, like easily creating polymeter on its various tracks, substep/probablility settings on each step, etc
1 Like