Upcoming in Massive X 1.1

Patch notes can be found here: https://www.native-instruments.com/...l-update-status-massive-x-current-1-1.359895/

 

Nice to have a manual from which I've learned a lot. I also note a few typos. How do we report those?

 

Feel free to share them here, then I will forward them to the documentation team. Thank you!

 

I've seen a few cosmetics, nothing most people might be bothered with:

• 7.5 Sidechain modulation (p16) the diagram has labels 1 & 2 but the text talks about 5 & 6
• p59 the (1) - (4) list items are missing space after the )
• p63 the list goes (1) (4) what happened to (2) and (3)?!

Nothing too exciting. There are also many page breaks that could be changed to make the document read better. Mostly they are where a colon introduces a picture. I realise these are a nightmare to fix when the document repaginates!

I also don't think your diagrams should sit flush left (except the largest) as they look odd above lists. I would indent them to sit in line with the text after the list number.

 

Awesome, the 3 bullet points are updated and will go live next week Thank you Tony!

 

More manual errors.

• p53 low-p ass filter.
• p116, p119 several occurrences of irregardless- should be regardless(no such word as irregardless- it's regardless or irrespective).

 

Well, there is now!

 

I'm happy MassiveX is getting updated. However, there is a problem still in the program where it will not pass knob activity to the host aside from the 16 knobs across the top. It is a problem because I can only map the top 16 knobs into Kore2 while all the other controls remain invisible to Kore2.

 

Yeah considering the number of parameters there are, that one might take some time to implement properly.

 

If they could map the Envelope1 knobs and the master volume/pan knobs, that would be a helpful start to placate us until they map everything.

 

IMHO it doesn't make sense to do it in small bits.

 

Depends on how long it takes to do a tiny bit of the mapping versus all of the mapping.

 

It also depends how the product owner decides, and not random forum users

 

Haha. I like it. Don't fix that one.

It has indeed been added to various dictionaries, simply because enough people use the incorrect spelling that they now have to describe what it means when people use it. But outside of informal writing I think it should always be corrected. Looks unprofessional.

 

It's in my Oxford Dictionary for Writers and Editors, but it says to use regardless, and I consider Oxford to be the highest authority. It's such a horrible word as the prefix and the suffix cause a double negative which means that it doesn't actually make any sense in a similar irritating way that people(mostly Americans) say 'I could care less' when they mean that they don't care. I'm fine with it being used in a humorous ironic manner, just not in a technical manual.

 

Yes, but I work in another industry where I can't allow to miss targets.

Note: After my rant I have to say i'm happy with the update. Still things to adress, but the visual feedback is nice. Thanks.

 

Nice update, although it all should have been there at release! I am finding Massive X to be truly... umm.. big (well you know). But what on earth is going on with the preset browser?! Where are third party massive presets supposed to go? This needs sorting asap. Love the flat black GUI btw!

 

I could go either way on this. It'd be nice to have some parameters available at the start, but I don't think we'd be able to all agree on what's most useful, especially given you could just map those parameters to the macros in the meantime. Not to mention the hassle of the devs having to push multiple updates for one feature. Just doesn't make a lot of sense.