Maschine mk2 working within the Maschine 3.x(with limitations)

6xes

People are likely unaware that you can run Maschine 2.x within the 3.x version…

what does this mean in practical terms??

hard to say… as i have not fully experimented with it

but if you are interested in experimenting with the Maschine mk2 controller… look for the Kushview elements VST

Find more posts tagged with

Comments

6xes

okay after a little bit of experimentation, it would seem that you can control midi elements of Maschine 3.x within the Maschine 2.x stand alone environment with the Mk2 controller

the limitation is you can only control the "8" Auto midi assignments that are in the "Host" config whilst in the Maschine3.VST3 (also the group needs to be selected)

D-One

Maschine inside Maschine sounds like a worst routing nightmare than routing Maschine-Plug on a DAW tho, i wouldn't trust such a setup long-term neither.

donnerhans

The hardware machine MK2 does not work with the new software machine 3. The drivers for it are missing. Hello NI, will the drivers for MK2 be delivered later or can all MK2 owners throw their wonderful device in the garbage can? 😫
Surely it can't be that difficult to generate a mapping from MK2 to MK2. I would be very pleased if this were to be delivered later.

6xes

https://community.native-instruments.com/discussion/comment/190488#Comment_190488

edit: dont knock it until you've tried it

theres not much in the way of routing….

the Audio signal shares the same output… but again the limitation so far is only 8 "auto" assignments can be made from what i can see of the free version of Kushview's Elements VST

(from a MK2 controller perspective)

D-One

https://community.native-instruments.com/discussion/comment/190491#Comment_190491

He is talking about loading Maschine 2 plugin inside Maschine 3. It's not a driver problem, the driver still exists, support was removed from V3 inside the application itself.

https://community.native-instruments.com/discussion/comment/190492#Comment_190492

Not knocking it, I don't have an Mk2 to even have a reason to attempt… I advise against it because we aren't supposed to be able to load V2 inside V3, so if it's blocked eventually then you wont be able to open those projects. So, would not advise the general public to go there, unless you're willing to take risks.

6xes

https://community.native-instruments.com/discussion/comment/190501#Comment_190501

just to clarify things concerning the maschine Mk2 controller

i was using the maschine3.vst within Maschine 2.x standalone… which is why the Host x8 "auto" assignments work with the Maschine mk2 with the maschine3.vst

im sure there are more benefits to using the maschine within maschine scenario, just as an example, you can run the VST and have a separate BPM's running in unison and independantly… which cannot be done with any other host except through Elements or by manner of the BPM per scene in maschine3.0

ozon

https://community.native-instruments.com/discussion/comment/190491#Comment_190491

Garbage is the official destination for the Mk2:

https://community.native-instruments.com/discussion/37381/ending-software-support-for-some-earlier-generations-of-maschine

PK The DJ

"Garbage is the official destination for the Mk2"

No, because if you have a MK2 then it will continue to work with version 2.X of the software.

ozon

https://community.native-instruments.com/discussion/comment/190518#Comment_190518

Until the next OS upgrade.

D-One

Wanna know whats interesting? All the lua script code that relates to the Mk1 and Mk2 are still there in Maschine 3 afaik, not only that but the main script that loads them is also sort of intact (names are M1 and M2)… It has additions but nothing actually removed. If i had an Mk1/Mk2 I would give a go a trying to find where it's disabled.

PK The DJ

"Until the next OS upgrade"

Newsflash - you don't HAVE to upgrade your OS. If you have a working system, and upgrading would potentially break something, then don't upgrade.

This is more of a "problem" on MacOS anyway. Apple have a history of breaking support for things with their OS upgrades - and Mac users tend to then blame the vendor of whatever isn't working, rather than Apple.

ozon

https://community.native-instruments.com/discussion/comment/190522#Comment_190522

Security risk.

D-One

You also might have to in order to use something else, works both ways.

Simple solution for NI then, don't make products for MacOS if you dont plan on supporting it, how about that? If one decides to make products for a platform then you gotta accept how that platform works IMO.

But I bet they don't want to loose those $ from MacOS users…

PK The DJ

How long do you want to do this? LOL 😂

Newsflash - you don't HAVE to be permanently connected to the internet. There are also plenty of third party security programs that you could use if your OS is not being updated. You could also secure your system via suitable hardware, even the router you already have.

D-One

How came you have some sort of absolute certainty that people you dont even know "dont have" to do this or that? How you know he doesn't work remote or something that would require constant web access?

OS Security issues cant be fixed with simply stuff, apple doesn't even divulge vulnerabilities or exploits for obvious reasons for any 3rd party to even attempt to fix them.

Quick links

Unanswered questions