Maschine set workflow??

Hey guys,

Quick question for you! Over the next year or so, I’m hoping to phase out traktor from my sets completely. At the moment, part of my sets are finger drummed out, while the rest consist of normal DJing. My long term goal is to have completely finger drummed sets with maschine.

At the moment, I can change files in maschine while playing on traktor. With respect to work flow, I’m confused about is how someone like Jeremy Ellis goes about playing an entire finger drumming set in maschine. Since each maschine file has 8 pages, will I need 2 maschines and 2 laptops to pull this off (will I have to load a new project on one laptop while playing on the other?). Is it possible to have a stable run of two instances of maschine on the same laptop? I’ve seen people completely stop the music to load a new file while playing with maschine, but that isn’t something which really appeals to me.

Any help is greatly appreciated!

Maybe i'm confused by your question, but in Maschine you have Groups and then Patterns within those groups.

With the new Maschine software (2.0), you can have unlimited groups. Each group can then have at least 16 patterns (probably more, never tried myself).

Needless to say, the limiting factor in terms of sounds available for a live setup of machine is probably the user's ability to stay organized.

Quote:

---

Originally Posted by ekerstein

Maybe i'm confused by your question, but in Maschine you have Groups and then Patterns within those groups.

With the new Maschine software (2.0), you can have unlimited groups. Each group can then have at least 16 patterns (probably more, never tried myself).

Needless to say, the limiting factor in terms of sounds available for a live setup of machine is probably the user's ability to stay organized.

---

You hit the nail the head, I didn't realize there are unlimited groups in 2.0. Looks like I'm going to have to buy the upgrade. Thanks for your help.

Organization is definitely a concern of mine. Having a million groups in a project file is probably really messy.

Hey Guys -

I'm working on live performance video course for maschineskills.com as we speak. Izn, I'll send you a dropbox link via facebook to some of the videos once they're edited - maybe we can get a blurb!

I would definitely upgrade to 2.0, and use soloing to keep only a few groups active at once. This is how I handle having so many groups. It is also a good idea to have multiple instances, especially because Maschine does crash from time to time. If you have Bitwig, the crashes won't bring down your DAW or your system. In fact, Maschine is pretty good about automatically switching to an active instance, so it will be barely noticeable.

Quote:

---

Originally Posted by botstein

Hey Guys -

I'm working on live performance video course for maschineskills.com as we speak. Izn, I'll send you a dropbox link via facebook to some of the videos once they're edited - maybe we can get a blurb!

I would definitely upgrade to 2.0, and use soloing to keep only a few groups active at once. This is how I handle having so many groups. It is also a good idea to have multiple instances, especially because Maschine does crash from time to time. If you have Bitwig, the crashes won't bring down your DAW or your system. In fact, Maschine is pretty good about automatically switching to an active instance, so it will be barely noticeable.

---

Thanks dude, looking forward to seeing them. I think its awesome that your making this resource. The solution I ended up with for my problem was to just open up two instances of maschine in ableton (each controlled by a separate drum pad). It allows for just that extra bit of flexibility I needed.