Massive X - the thread

[ghettosynth]

i hang out here because, when it's not a war zone, it's like an AA meeting for music nerds and a comedy club rolled into one; what could be better?

while i wait for a real browser, midi control, fixes, tweaks, etc... i really am enjoying using MX. am glad i paid for it (using realtrance's money, of course).

It's not like he needs it anyway. What's he going to do, buy more gear to make trance? You did him a favor!

[pdxindy]

07.07.2019 - the day when hot topic about MX died [*]

It's because everyone had no choice but to uninstall it since a youtube video said so...

[pdxindy]

and another 'baiting' post. critique isn't whining, true; whining is whining.. and there's lots of that on this thread.

yeah... and most of that whining is by people upset at posts expressing some criticism of MX...

[pdxindy]

now, if you could just get all the whiners and ranters to go with you

you should leave then... you seem incapable of making a post that doesn't have overt or subtle attacks against others... which makes you one of the most negative posters in the thread.

[fisherKing]

now, if you could just get all the whiners and ranters to go with you

you should leave then... you seem incapable of making a post that doesn't have overt or subtle attacks against others... which makes you one of the most negative posters in the thread.

you need to develop a sense of humor. and there's never an excuse for whining; discussion is so much more productive.

[realtrance]

i hang out here because, when it's not a war zone, it's like an AA meeting for music nerds and a comedy club rolled into one; what could be better?

while i wait for a real browser, midi control, fixes, tweaks, etc... i really am enjoying using MX. am glad i paid for it (using realtrance's money, of course).

I was wondering where that went! I thought maybe Sadowick took it.

Oh well, the price had to be paid.

[realtrance]

Let’s all just choose to get along, it’s not that hard.

I do love the sound of MX, period, and it’s already fun to use, and obviously frustrating, too.

That’s the nice thing about software, though; it can be improved. Remember this is a 1.0 release. Much more to come.

[pdxindy]

now, if you could just get all the whiners and ranters to go with you

you should leave then... you seem incapable of making a post that doesn't have overt or subtle attacks against others... which makes you one of the most negative posters in the thread.

you need to develop a sense of humor. and there's never an excuse for whining; discussion is so much more productive.

and I'll repeat... you are incapable of making a post that isn't attacking people or telling them what to do with your oh so smug superior attitude..

[navin.neu]

Have to say, i’ve been really enjoying MX so far. Routing is fairly intuitive and i’m honestly finding it hard to make a BAD sound with. The raw wavetables on hand are all solid and the effects are great.

That being said, certain things about it do scream “this was a rushed release.” I agree with anyone who says the browser needs an overhaul and that the UI needs to be a bit more animated (little notches on the saturn rings for actual position, graphical envelopes etc.) Tbh though, i actually find the UI pretty clean and straightforward otherwise.

The thing that irks me is that NI has been rushing TONS of products out before they’re fully cooked lately. Maschine mkIII was mentioned earlier in the thread, but the Komplete Kontrol A series was also botched on release and was pretty useless to anyone not on ableton or logic. Not to mention that front panel reaktor blocks update that was somewhat of a mess since there was no good way to integrate it with user library blocks.

Anyways, heres hoping NI delivers on the promise of keeping MX updated... i’m cautiously optimistic only because i think they’ll get a lot more scrutiny with this one than they have in the past.

[glokraw]

Let’s all just choose to get along, it’s not that hard.

I do love the sound of MX, period, and it’s already fun to use, and obviously frustrating, too.

That’s the nice thing about software, though; it can be improved. Remember this is a 1.0 release. Much more to come.

Remember this is a 0.1 release. Much much much much much
much much much much more to come.

[SLiC]

Have to say, i’ve been really enjoying MX so far. Routing is fairly intuitive and i’m honestly finding it hard to make a BAD sound with. The raw wavetables on hand are all solid and the effects are great.

That being said, certain things about it do scream “this was a rushed release.” I agree with anyone who says the browser needs an overhaul and that the UI needs to be a bit more animated (little notches on the saturn rings for actual position, graphical envelopes etc.) Tbh though, i actually find the UI pretty clean and straightforward otherwise.

The thing that irks me is that NI has been rushing TONS of products out before they’re fully cooked lately. Maschine mkIII was mentioned earlier in the thread, but the Komplete Kontrol A series was also botched on release and was pretty useless to anyone not on ableton or logic. Not to mention that front panel reaktor blocks update that was somewhat of a mess since there was no good way to integrate it with user library blocks.

Anyways, heres hoping NI delivers on the promise of keeping MX updated... i’m cautiously optimistic only because i think they’ll get a lot more scrutiny with this one than they have in the past.

Yes, this is a trend and possibly linked to the amount of money pumped in to NI lately (investors looking for a return?) - who knows....but there has been a lot of it as mentioned, maybe they just took too much on. Anyway, despite the shortcomings of (in my case) both Maschine Mikro Mk 3 and Massive X I trust that NI will fix the issues eventually and work on scalable GUIs for all of their products.

Back to MX as is, I wonder if any of this new framework will find its way to.other NI instruments or FX...scalable interface, flexible modular connection...these are a good start.

I am hearing some good sportiness coming out of this thread and the one at Gearslutz, some people obviously already have a handle on this synth without a manual or visual feedback, Kudos to them, personally I need more help!

[aMUSEd]

Back to MX as is, I wonder if any of this new framework will find its way to.other NI instruments or FX...scalable interface, flexible modular connection...these are a good start.

Would not be at all surprised to see a FM-X and maybe even an Absynth X with this approach at some point. Would work great with both.

[SLiC]

Back to MX as is, I wonder if any of this new framework will find its way to.other NI instruments or FX...scalable interface, flexible modular connection...these are a good start.

Would not be at all surprised to see a FM-X and maybe even an Absynth X with this approach at some point. Would work great with both.

Yes, Absynth X came to mind for me as well and probably the legacy synth most in need of some love. I was never a Massive fan (I actually think Massive X is much more interesting) but I would be excited to see Absynth X. NI also have such a good suite of FX as singles and Guitar Rig that could be put all together as a modular style rack with MX style routing.

I notice on the NI site forums one of the dev's posted that the next 'thing' was to look at integration of KK and Maschine at core engine level. Whilst I don't know exactly what that ,means, it strikes me that they have a house style with great browser, tagger, scale set, arp etc in KK software that could just be integrated in to all products (like MX) so there is some consistency to the workflow (or host, launch all products through KK- that's almost like Kore )

[aMUSEd]

I notice on the NI site forums one of the dev's posted that the next 'thing' was to look at integration of KK and Maschine at core engine level. Whilst I don't know exactly what that ,means, it strikes me that they have a house style with great browser, tagger, scale set, arp etc in KK software that could just be integrated in to all products (like MX) so there is some consistency to the workflow (or host, launch all products through KK- that's almost like Kore )

Where? I'd like to comment on that, been saying for a long time that Maschine needs to address issues of incompatibility with KK and other NI products - in particular the lack of aftertouch support is mind-boggling considering both the keyboards and all their plugins support it (and MX makes using aftertouch so easy, although I wish it was polyphonic)

[SLiC]

I notice on the NI site forums one of the dev's posted that the next 'thing' was to look at integration of KK and Maschine at core engine level. Whilst I don't know exactly what that ,means, it strikes me that they have a house style with great browser, tagger, scale set, arp etc in KK software that could just be integrated in to all products (like MX) so there is some consistency to the workflow (or host, launch all products through KK- that's almost like Kore )

Where? I'd like to comment on that, been saying for a long time that Maschine needs to address issues of incompatibility with KK and other NI products - in particular the lack of aftertouch support is mind-boggling considering both the keyboards and all their plugins support it (and MX makes using aftertouch so easy, although I wish it was polyphonic)

https://www.native-instruments.com/foru ... ne.356733/

Maybe just wishful thinking on my part, they have released a LOT of products that are obviously not fully developed yet and don't have complete DAW, KK, MC integration (MK3, M32, A series etc) so they may just be playing catch up with development....unfortunately if they keep releasing new hardware they may never catch up; people seem incredulous that half a year after release MM MK3 doesn't even have basic DAW control.

WHAT’S NEXT?

Many of you will be wondering and asking where we head next in terms of our development. All I can say at this point, is that we will be focussing on the heart of MASCHINE and KOMPLETE KONTROL.

In our Beta environment (Centercode) we are able to share more details about our current work in progress, and plans for the next months. We are currently in the process of merging the KOMPLETE KONTROL and MASCHINE Beta environments. Once this is done, we are happy to invite you to apply to join. Keep an eye out here, you’ll be the first ones to know about this!

Best,
Kai