Need to go back to 2.15.2
toneyrome Member Posts: 17 Helper
If you're on a Mac you can just open Maschine using Rosetta until you get things sorted.0
Ah yes of course! Done that now... So please remind me, that means Maschine is not running natively on Silicon right - there's some kind of layer of code translating it or something? And now I can see all the VST3s are showing up as 'wrapped' - would someone mind briefly summarising the effect of all this?
Damn! I was excited to make use of native M1 support. But dozens of my plugins (all Arturia, for example) don't automatically load with their VST3 counterpart. So none of my sessions are compatible. Is this how it's going to be moving forward?! Is there no way for the plugins to load as VST with all settings loaded properly?
The message I get when opening all previous sessions is:
"Project Plug-ins not migrated" "Please be aware that VST2 is not supported on native apple silicon, except when run in Rosetta 2 mode. We encountered an error auto-migrating the VST2 plug-ins to a compatible VST3. Please contact the plugin manufacturer for more information."0
It's the typical NI shenanigans:
You can use Maschine Natively now but tons of NI products aren't native yet (not to mention from 3rd party), so... you pick between Rosetta 2 where all your stuff should work fine, or pick Native silicon to get more performance but have half your stuff not working. 😐 Rosseta slows things a bit but it's pretty darn efficient, shouldn't be an issue unless your projects are all hitting the CPU to its limit.
Regardless both modes support VST3 now.
Using Rosett 2 mode?
Nothing changes compared to the previous version, it already had to run in Rosseta 2.1
Thanks D-One. Good to know that I'm not forced to choose between VST3 or an older version of Maschine. That said, I actually am running into CPU issues and would love to have M1 support (I have the M1 Max Macbook and STILL having CPU issues). Worth noting that all of my critical plugins already have Apple silicon support. The issue is that my VSTs and VST2s are not auto-migrating to VST3s. Are we expecting manufacturers (especially big ones like Arturia) to fix that compatibility issue?0
The issue is that my VSTs and VST2s are not auto-migrating to VST3s. Are we expecting manufacturers (especially big ones like Arturia) to fix that compatibility issue?
As understand it Maschine uses the official VST3 migration method but not all other 3rd party devs use it, something to do with parameter ID's... So I think yes, if its broken then the other manufacturer has to enable the migration support.0
- 12.4K All Categories
- 21 Welcome
- 563 Hangout
- 68 NI News
- 273 Tech Talks
- 1.3K Native Access
- 5.8K Komplete
- 762 Komplete General
- 1.3K Komplete Kontrol
- 2.1K Kontakt
- 568 Reaktor
- 186 Battery 4
- 315 Guitar Rig & FX
- 222 Massive X & Synths
- 278 Other Software & Hardware
- 2.6K Maschine
- 24 Sampling Room
- 3.1K Traktor
- 2.9K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators