Maschine Studio and Maschine 2.0!!!

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS
Maschine

Post

ericj23 wrote:So did anyone catch whether it does PDC?

I will probably update anyway, but PDC would make it possible to consider using it for far more than just drums.
PDC is said to be a bad feature to use for something that should be as responsive as possible like Maschine. The recommended practice when third party plugins are concerned is simply not to use latency inducing plugins in Maschine and only use plugins that have very low (or zero) latency.

Post

bunnywrench wrote:
ericj23 wrote:So did anyone catch whether it does PDC?

I will probably update anyway, but PDC would make it possible to consider using it for far more than just drums.
PDC is said to be a bad feature to use for something that should be as responsive as possible like Maschine. The recommended practice when third party plugins are concerned is simply not to use latency inducing plugins in Maschine and only use plugins that have very low (or zero) latency.
So basically your saying that their machine studio can't be used as one, as any latency inducing plug-ins don't work. PDC can be switched on or off in any sensible host, but without it choice of plug-ins to use is massively limited

PS do you actually know that it has no PDC or are you surmising?
I believe every thread should devolve into character attacks and witch-burning. It really helps the discussion.

Post

ericj23 wrote:PDC can be switched on or off in any sensible host, but without it choice of plug-ins to use is massively limited
I thought exactly the same thing. That NI took the time and effort to make a total rewrite to be able to make it 64 bit and not taking PDC into consideration sounds absurd. It has to be there.

/C
Neon City for u-he Repro - 80s pop & Synthwave soundbank
HARDWARE SAMPLER FANATIC - Akai S1100/S950/Z8 - Casio FZ20m - Emu Emax I - Ensoniq ASR10/EPS

Post

Trust me I requested sequencing features many many times, I asked for rx2 batch import and sync in time for loops so many times on both forums and via email.

musikmachine wrote:Well y'all could get involved on the forums, at lot of this stuff is by feature request and they had OTR threads where you could ask about things you wanted. Some of Nis design decisions leave me scratching my head but they've implemented a ton of stuff that users have been asking for.

I haven't seen much around things like groove templates but round robin seems like a pretty standard thing and i wish they'd allow pad layering like Geist but i guess i'll have to use groups!

But i think most of maschine's updates have been user driven from about 1.5, the most requested stuff has been slowly added but things have been left out or changed in 2.0. I think it's a good upgrade if it's got what you want but yeah the forums are worth checking for stuff they changed in 2.0.

Post

It doesn't do PDC. And I don't recommend using latency inducing plugins in Maschine for obvious reasons. Maschine is not a DAW. Being an instrument that gets used live in a real-time environment (albeit one than can host plugins), it should not have PDC since it should be as responsive as possible.

PDC would seriously alter the live playability of Maschine. Compensating for huge latencies and a responsive live instrument don't go hand in hand. It will only serve the people who are looking for a bloated DAW instead of a mean lean live playing machine. In a real-time environment you can't expect the computer to know what your going to do in the future. This is also why Ableton is in a conundrum of users still complaining about them not being able to figure out how to implement PDC properly in Live.

Post

bunnywrench wrote:It doesn't do PDC. And I don't recommend using latency inducing plugins in Maschine for obvious reasons. Maschine is not a DAW. Being an instrument that gets used live in a real-time environment (albeit one than can host plugins), it should not have PDC since it should be as responsive as possible.

PDC would seriously alter the live playability of Maschine. Compensating for huge latencies and a responsive live instrument don't go hand in hand. It will only serve the people who are looking for a bloated DAW instead of a mean lean live playing machine. In a real-time environment you can't expect the computer to know what your going to do in the future. This is also why Ableton is in a conundrum of users still complaining about them not being able to figure out how to implement PDC properly in Live.
"PDC can be switched on or off in any sensible host".

Why would the ability to be able to switch on or off PDC in Maschine be anything but positive?

/C
Neon City for u-he Repro - 80s pop & Synthwave soundbank
HARDWARE SAMPLER FANATIC - Akai S1100/S950/Z8 - Casio FZ20m - Emu Emax I - Ensoniq ASR10/EPS

Post

DrGonzo wrote:
bunnywrench wrote:It doesn't do PDC. And I don't recommend using latency inducing plugins in Maschine for obvious reasons. Maschine is not a DAW. Being an instrument that gets used live in a real-time environment (albeit one than can host plugins), it should not have PDC since it should be as responsive as possible.

PDC would seriously alter the live playability of Maschine. Compensating for huge latencies and a responsive live instrument don't go hand in hand. It will only serve the people who are looking for a bloated DAW instead of a mean lean live playing machine. In a real-time environment you can't expect the computer to know what your going to do in the future. This is also why Ableton is in a conundrum of users still complaining about them not being able to figure out how to implement PDC properly in Live.
"PDC can be switched on or off in any sensible host".

Why would the ability to be able to switch on or off PDC in Maschine be anything but positive?

/C

Because NI is producing a specific tool, not a one size fits all sequencer. coding PDC in an application where the sequencing is non-linear is not a trivial undertaking, it's hard, and it would take a lot of effort to produce. And in the end it doesn't fit what maschine is. Maschine is the bastard love child of an MPC and Reason 5, expecting it to be anything else misses the point completely.

Now, can you finally audition rex files in this version or not?

Post

ShawnG wrote:Now, can you finally audition rex files in this version or not?
Yes, and in project tempo.

Post

bunnywrench wrote:
ShawnG wrote:Now, can you finally audition rex files in this version or not?
Yes, and in project tempo.
sweet, thx. one of the few things I wasn't able to confirm from the press releases. a small thing, but it bugged me.

Post

So i gotta ask, what was their response and was there much interest? They've rewritten so hopefully it's laid the foundation to implement these things. :)
topaz wrote:Trust me I requested sequencing features many many times, I asked for rx2 batch import and sync in time for loops so many times on both forums and via email.

musikmachine wrote:Well y'all could get involved on the forums, at lot of this stuff is by feature request and they had OTR threads where you could ask about things you wanted. Some of Nis design decisions leave me scratching my head but they've implemented a ton of stuff that users have been asking for.

I haven't seen much around things like groove templates but round robin seems like a pretty standard thing and i wish they'd allow pad layering like Geist but i guess i'll have to use groups!

But i think most of maschine's updates have been user driven from about 1.5, the most requested stuff has been slowly added but things have been left out or changed in 2.0. I think it's a good upgrade if it's got what you want but yeah the forums are worth checking for stuff they changed in 2.0.
Latest release and Socials: https://linktr.ee/ph.i.ltr3

Post

ShawnG wrote:
bunnywrench wrote:
ShawnG wrote:Now, can you finally audition rex files in this version or not?
Yes, and in project tempo.
sweet, thx. one of the few things I wasn't able to confirm from the press releases. a small thing, but it bugged me.
Excellent, i rarely used rex loops cause of the way it loads in 1.8. :)
Latest release and Socials: https://linktr.ee/ph.i.ltr3

Post

It took me quite a while to warm up to Maschine. Bought it when it first came out, tried it for a few projects then put it back in the box until last year. Then when I started using it the right side of the display stopped working so I had to buy new hardware. No wiper or Scene follow threw me off but as the software improved and I got over the KORE debacle, Maschine grew on me. So... I took the big plunge and Maschine Studio is being delivered Monday. :hyper: :party: :clap: :harp:

Post

That's a long way around :lol:

We'll look forward to the review :ud:

Post

I think I may as well of written gfdstyug&£-
musikmachine wrote:So i gotta ask, what was their response and was there much interest? They've rewritten so hopefully it's laid the foundation to implement these things. :)
topaz wrote:Trust me I requested sequencing features many many times, I asked for rx2 batch import and sync in time for loops so many times on both forums and via email.

musikmachine wrote:Well y'all could get involved on the forums, at lot of this stuff is by feature request and they had OTR threads where you could ask about things you wanted. Some of Nis design decisions leave me scratching my head but they've implemented a ton of stuff that users have been asking for.

I haven't seen much around things like groove templates but round robin seems like a pretty standard thing and i wish they'd allow pad layering like Geist but i guess i'll have to use groups!

But i think most of maschine's updates have been user driven from about 1.5, the most requested stuff has been slowly added but things have been left out or changed in 2.0. I think it's a good upgrade if it's got what you want but yeah the forums are worth checking for stuff they changed in 2.0.

Post

topaz wrote:Seems NI have removed some features from 2.0 that would certainly mess me up, especially not exporting a single midi file ?
You can now export a MIDI file on the sound level as well as group level. So for example, if you sliced to a pad, you would still have a single MIDI file for all your slices.

You can also batch export group MIDI files into a single MIDI file.

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”