There HAS to be a way to STOP Maschine from scanning EVERY plugin on start up

Joseph CR Vourteque · 2022-02-10T14:46:37+00:00

There was an error rendering this rich post.

Guys, I am at my wits end.

I love Maschine but I loaded it literally 8 minutes ago and it's STILL scanning every plugin on my machine. It does this every time (this time is particularly slow) and I really need it to stop.

I have unclicked EVERYTHING I can think of to stop this madness. I run a Windows machine and do not care if this isn't an issue on Macs, because I'm not going to stop using Windows. So can someone PLEASE get me a work around?

At the very least - NI - can you fix this? this is ridiculous. Since I started writing it is STILL scanning every damn thing.

Thanks all

-Joe

Find more posts tagged with

Maschine 2 SW

Comments

ozon

@Don1990 wrote:

Been waiting on simple and BASIC solutions since 2009, […] Thankfully I'm still able to make use of my return policy with a local music shop.

That must be the most generous return policy of all time in the whole universe!

Jiglo

Buy a M+ and live the dream 🤙

Scanning done in less than a minute and i'm making music shortly after switching on, even it it's scanning a bit longer in the background the 280gb (ish) worth of content. It's what dreams are made of! 😎

Don1990

https://community.native-instruments.com/discussion/comment/129661#Comment_129661

lol, of course I sold my 2009 mk1 later down the line. Got the MK2, sold it. MK3 sold it, now I gave the MK3 another chance, but returning it.

https://community.native-instruments.com/discussion/comment/129669#Comment_129669

That's like saying: I am having car problems with my Honda. "Well, buy a Mercedes then and live the dream" and the Mercedes has the same issues just "less". lol. No device/DAW should unsolicitedly scan for POTENTIALLY new plugins. We know damn well when we install new plugins, just give us the option to scan whenever we feel like it not every time on startup (like any other device/DAW does).

Jiglo

Yeah sorry man, but you have a computer science degree and have been told you can press esc to save the scanning. I just found it slightly amusing and it's perhaps a bit more like saying you a mechanic and have a problem with your Honda????

Anyway, i'm unaware of such a scanning issue as I haven't personally experienced it, so i'm sorry for not being more sympathetic.

Don1990

No worries on the sympathy part, I appreciate it though. Not asking for sympathy, I am asking for a SIMPLE not even technical solution. I am glad you are living the dream with your M+ 😬

And yes, I am willing do fix 1 or 2 things (it's not just the scanning issue) on my Honda but if I have to fix the whole engine? Nah thanks. I'd rather purchase a car that runs 'normal' instead of a car that works 'half normal' with a zillion workarounds. You can enjoy your hooptie.

"and have been told you can press esc to save the scanning"

You are proving my whole point lol, did you read my post about usability? How is doing extra steps benefiting usability? One of the MOST important things when it comes to companies that hire technicians/computer scientists. Usability is usually the FIRST thing in the process of inventing/releasing a concept of a product.

DeepThumb

I stop scanning by pressing the ESC button, if I want that. No problem at all for me.

D-One

I had this problem a few times and the solution was always the same, either deactivate or remove a specific plugin... You just have to look at the loading screen and see in what plug name the app stalls in.

https://community.native-instruments.com/discussion/comment/38892#Comment_38892

This is the solution 90% of the time, if people bother to pinpoint which plugin causes the issue.

Vocalpoint

https://community.native-instruments.com/discussion/comment/129936#Comment_129936

This works fine - but the real issue here remains the same.

I fully support scanning - when needed - like I have actually added something new to the plugin pile - what goads me is the "scan no matter what" assumption.

There is literally no reason whatsoever to ever scan anything when nothing has changed. This behavior is best demonstrated when dragging KK into a new song in Studio One over here - drag, drop and ready -in about 1 ms.

Don1990

https://community.native-instruments.com/discussion/comment/129951#Comment_129951

Thank you, all the needed to be said! 🙌

PK The DJ

As has been said (repeatedly) there is a way to stop the scanning. Press escape.

It's incredible what people find to complain about. 🤣

Bear in mind what would happen if NI removed the scan at startup. No doubt the forum would be full of people saying they just installed a bunch of plugins but they're not showing up.

Someone will say all they have to do is go to this location and press that button - but oh no, that's too much trouble. "I have to press a button? Why can't it be done automatically?" and around we go again.

😁

Vocalpoint

@PK The DJ

"Bear in mind what would happen if NI removed the scan at startup. No doubt the forum would be full of people saying they just installed a bunch of plugins but they're not showing up."

No one is saying "remove" the scan. What should be considered is exactly like Presonus does this.

In the early going - Studio One treats me like a child that has no idea what is going on (when I first install the program) and subjects me to a plugin scan EVERYTIME I start the program.

Soon I become familiar with the environment (and the pain that this scan imparts) so Studio One then treats me like an adult by offering me a toggle to turn this ****** off.

Once that has occurred - it is on me - now and forever - to manage my scan priorities.

Not a big ask. If a typical user cannot "manage" their own plugins (and scans) in KK - there is something wrong here.

Don1990

https://community.native-instruments.com/discussion/comment/130439#Comment_130439

You didn't even read the rest of the convo, you just talk to talk. Read the whole topic again. Everyone and their mother knows the ESC key stops it, but that's one of MANY workarounds NI implemented. If that would be the only thing, nobody would have ever complained. A WORKAROUND, is NOT a fix...damn how can people not comprehend that. Read:

"And yes, I am willing do fix 1 or 2 things (it's not just the scanning issue) on my Honda but if I have to fix the whole engine? Nah thanks. I'd rather purchase a car that runs 'normal' instead of a car that works 'half normal' with a zillion workarounds. You can enjoy your hooptie."

https://community.native-instruments.com/discussion/comment/130448#Comment_130448

Amen! 🙌

PK The DJ

@Don1990

Everyone and their mother knows

Seems like it's you that needs to "read the whole topic again". Clearly OP did not know about pressing the escape key - hence the thread title and the first post asking for a workaround.

Don1990

@PK The DJ

You're talking about "it's not a big issue to press the ESC key". No ******...that's pretty much what I am saying in all of my previous posts. I know the OP asked for a workaround, I am just stating that there is a simple FIX instead of WORKAROUND.

Do you prefer a electric start on a dirtbike or a kick-start? No, it not a big issue to start it with a kick-start. But everyone and their mother prefer powering on the dirtbike with electric start.

PK The DJ

@Don1990 Earlier you said "How is doing extra steps benefiting usability?"

Well there's either going to be an "extra step" pressing esc at the start.......or, if the startup scan is not taking place, an "extra step" when you DO need to scan.

It doesn't need a FIX because nothing is BROKEN.

[edit] I just noticed, in your first post of this thread, you said that you're out and you're not coming back.

Why are you still here? 🤣

Quick links

Unanswered questions