does anyone know how i can bypass the vst scan on maschine mk3 startup? it's starting to take a lengthy while waiting for it to scan all plugins
Press the Esc key.
I tried doing this and it doesn't work
You should not.
Once it is done correctly, Maschine will open in few seconds. Until you change something (add new plugin etc. etc.). Then it will re-scan again but much faster.
If not done, it will re-scan again and again, every time you open the app.
If not done, un-scanned plugins will not appear in your instrument/effects list.
No matter how many times you wait for the scan to complete, every single time you open the Maschine software it scans again. It may be quicker, but it still happens.
Therefore, once you've done the initial scan, the only way to get past the scan next time is to hit Esc. (which does work).
Over the years there have been many posts from users complaining about the startup scan, so it definitely is an issue - which NI supposedly improved recently with "four times faster" parallel scanning.
People have questioned why Maschine behaves this way when other VST hosting software does not.
With 400 plugins (more or less) on my PC:
My Maschine opens in 4-5 seconds,
Ableton opens in 7,
Cubase opens in 11-12 seconds
(all above values are not standard, they can be faster or slower each time, depending on the case, but those, are the most often results)
So, i can not really understand why people complaining… Unless, if this is not a standard issue for everyone (for me, it is definitely not). But in this case, their delay should be causing by their systems, not by Maschine itself. If it was a bug it would be much-much more common among users.
For me:
Ableton Live 12 Suite = 19 seconds
Maschine 3 = 47 seconds
@legacy420 Is it still happening, and is it happening every time you launch the program? Then it might be wise to get in touch with support here: https://bit.ly/NI_Support_All maybe we can figure out what causes these issues.
Lately this is happening also to me. Wait in the order of 5 to 10 min (Maschine gets even stuck during startup, with the “The program is not responding. Do you want to close it or wait for a response?” message). If I tell it to wait for a response and I’m very patient, after 5 or more minutes it finally opens.
The “Esc” workaround works only if I perform it immediately when (and IF) I see the first plugins being scanned. Once the program is stuck, it only shows the “not responding” message.
I’m trying to narrow down the causes of this. If I discover something, I will post it here
@legacy420 @LostInFoundation One thing to check is the Maschine log file.
I can pass it on to our QA & devs. This might give indication on what's causing this.
Thank you @Jeremy_NI
Here is my Maschine 3.log
I wanted to also add the Maschine 2.log since the issue is happening even there, but i can't find it in the Temp folder. Does it have a different more obscure name or is it in a different location?
I'm hoping this helps but may not apply to PC guys. Although I use Mac OS, I started having the long load problem when I reinstalled Kontakt Player7 to work around the hang that occurs when using any Hypha preset directly from the Maschine browser.
Reinstalling Kontakt player 7 fixes the Hypha hang, so there's that. However, the next session (a day later) when I tried to start Maschine it took minutes rather than the ususal approx 5 secs to start.
That's a bigger deal than having to access Hypha presets from the within the actual instrument, so I uninstalled Kontakt Player 7, and then reset the whole Maschine database. Lo and behold, start times back to normal.
Curious, and being an obvious glutton for punishment (married, so…) I reinstalled Kontakt player 7, played for a bit and quit. Rebooted. Tried to boot Maschine, start time was dismal. This time I only uninstalled Kontakt 7 per the NI instructions but did not reset the whole Maschine database. Load times were again back to normal.
If you can use your rig without Kontakt Player 7, give it a shot and let us know if it helps. Cheers, Yall.
Sorry for not getting back earlier. I've forwarded the file to the Maschine team, hopefully they can get some useful info from this.
Maschine 2 is a different beast on that regard, it's noot the same scanning system so no log file. Since it's also happening in Maschne 2, did you add some plug-ins recently or did you do any software update?
The only thing I remember I added is Maschine 3 itself.
And… things are starting to behave even worst: since the installation of Maschine 3, I started to have some issues in Maschine 3 also with plugins that were previously installed (and that I use daily), like this message about damaged samples file in Alicia’s Keys
(translation of the message: “Maschine 3.exe - File damaged. The file or the directory \Documents\Alicias Keys\Samples\Alicias Keys_005.nkx is damaged and not readable. Execute the Chkdsk utility”)
A couple of notes:
Let’s see if the team can discover something