Jump to content

NI Updates: Massive X and Komplete Kontrol


Magic Russ

Recommended Posts

Mostly Apple stuff, but for Massive X allowing user preset tags to be edited has been long in coming.

1.4.3 - 2023-03-23

MASSIVE X is available as AAX, AU, VST and VST3 Plug-ins in this version.

MASSIVE X requires an Intel processor with AVX or an Apple Silicon processor.

The MASSIVE X Factory Library is a separate installation, be sure to install via NATIVE ACCESS.

ADDED AAX Apple Silicon support

IMPROVED Various browser fixes and enhancements. User preset tags can now be edited

FIXED Massive is now macOS Ventura compatible

KNOWN ISSUE VST3 crashes in Reaper on macOS during scan (but still passes validation)

KNOWN ISSUE Host automation parameter names are fixed to "Macro" in Logic and GarageBand on Apple Silicon computers

KNOWN ISSUE Intermittent crashes when used with Mainstage

KNOWN ISSUE VST3 Macro parameters are overwritten by the DAW when recalling projects with Digital Performer. Please use AU or VST2 instead

 

2.9.0 2023-03-22 

ADDED AAX plug-in running natively on Apple Silicon 

FIXED Crash in Logic Pro when closing plug-in UI with speech engine enabled 

FIXED Handling of MIDI program change messages with VST3 plug-ins 

FIXED AAS plug-ins UI are blank after reopening UI in Live FIXED ScanApp crashes

  • Like 2
  • Thanks 3
Link to comment
Share on other sites

Just tried to update MASSIVE X and got a trojan alert from Windows Defender:

2015673850_NITrojan.png.a8b413d9d4a275b6d0ca5f5633bab716.png

 

So went looking via google and got this very recent post at NI Forums:

https://community.native-instruments.com/discussion/11586/microsoft-defender-detects-trojan-script-on-update-file-of-massive-x

Seems other "legit" applications are suffering from same issue when updated etc

 

 

  • Like 1
Link to comment
Share on other sites

I'm holding off until this is fixed but FWIW it's 99.9999999% that it's a false positive

It's being triggered by the  Windows Defender realtime protection, which is basically a Machine Learning model - that's what the !ml stands for on the end of the warning.  It's taking a look at the file and thinking that it reminds it of that particular virus.

Either way, unless you absolutely MUST have those fixes I'd advise anyone to wait - why risk it ? 

 

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...