Maschine 3.0 General Discussion

@Matthew_NI said "we, as a MIDI controller, typically have access to"

Shouldn't that say "typically do not have access to"?

Hi Mark, i find it difficult to expect companies to deliver services, if there is no clause about support duration in the contract. just from the standpoint of sanity, it would kill me to have expectations and high hopes for something others are doing. the moment i pay for my product for a one time fee. the deal is closed. thanks to the internet, it is possible to patch everything during years, that gives a distorted perception on the product itself. before you had to deliver at launch, if it failed, that was it. Today everything is on it's own strange timeline, assume it is is just common practice, as for costumer care and self preservation, more than a legal obligation. i find it very annoying to be on an alert for new stuff all the time, i give me one month a year(surprise, surprise, cyber weeks), to check out gear, than i close the lit from the constant noise from the net for the rest of the year, silence is one the most precious resources in our world, especially for people that work in very loud environments. of course i will never miss a launch of my favorite apps that i love to pay full prize every time, even if they do not deliver the most, i am willing to invest in them (not ni for me btw). it's my opinion and way to handle things, happy if you disagree. just what will i do when ni goes out of business tomorrow? i am responsible for my system, from the get go. i have to make an informed decision, every step of the way. from hardware to software,from compatibility to maintaining , it's up to me to make it work. when the day comes to stay in a system that works for now, or to upgrade to something that could break my production, and i choose to upgrade, i have to fix it, except i can hire a engineer. being in charge of technical stuff takes a lot air from being creative and productive. i feel your pain man. but PCs are general purpose devices, not specialized audio production tools. every thing can break at any time, it is not the most stable environment. so if you can dedicate one pc solely to making music/ audio production with apps installed on the main drive. make regularly images (.iso) from it and you should be future prove, and even if a controller break, check out your local instrument dealers, they mostly know somebody that fixes gear. and with llms, who know, in some years we are able to write custom driver as non engineers. somebody already startet one.

All the best to you,
cheers,
fabio

I just checked - stem separation is definitely mentioned and pictured. It's in the PDF version too.

@ozon (sorry editing the comment, does not allow taging members apparently) i tried to connect the mk3 to the ipad. the issue (one of many ?) is maybe that the mk3 can not be started in MIDI-Mode, or at least i was not able to do so. I used a powersupply to power maschine and connected it via din to a midi interface that was connected to an ipad.

i am speculating, that the implementation of the midi protocol is wrapped in its own "utility" layer and as such not exposed directly to the ui and midi port. also when starting up mk3 in MIDI-Mode under windows, my custom templates are loaded automatically, what could indicate that the controller editor is a dependency, if the templates are not stored on the hw unit itself.

Maybe an implementation of a "MIDI-Mode template utility" directly to the maschine application , and than a port to other OS would be a solution? in case of mobile devices, i find it more intriguing to utilize the touch screen itself, and as such save other resources. Sure the play style has to adapt, i do not mind. question now that imaschine is history, is a maschine 3.+ port for iOS even a thing?

for me, really the maschine application is just a companion software to the controller, and as such not the focal point.

everything that can not be handled from the hardware unit itself is a "flaw" in it's design.

I personally do not mind, managing settings and naming pattern/scenes on the computer is ok. but other than that, the gui plays no role when i perform with the mk3, and all features that are not available via the controller dismissed.

So maschine 3.0 as a standalone app and the vst gui to me is irrelevant. without the controller or a daw and a price tag of 99$, who is is this for? i can't even map parameters to an external midi controller… or can i ?😅 and as a music production app, you can start with the same price tag on a beginner tier on any major daw plattform and upgrade in time and need.. hack get reaper license for 60 bucks and take all the free goodies from every developer you like. you have in minutes a great tool set for itb and computer based audio production in general, you can start out without to worry about licensing issues. and as soon you start to earn bit money, switch to a commercial license for 230$ (still a great price).

but getting back to the maschine 3.0 software itself, i think the "About your ideas for maschine 3" is a much more productive discussion. but i will not spam that discussion. in my opinion, it is up to native instruments to hire great minds to push this product and if you are interested to be a part of the development, join the beta program https://native-instruments.centercode.com/key/maschine-software-only

At this point, i do not find that native instruments has introduced something really interesting to be worth of discussing, just solid new features on a absolute fantastic instrument and fixing the gui would be much appreciated😊