maschine taking ages to load

hi there,

just loading maschine on to my macbook pro, only last night i put a new 500gb hard drive in it and upped to ram from 2gb to 4gb, for the last must be nearly an hour here its saying its scanning maschine, it shouldn't take this long, i also have maschine on my imac and it didn't take this long to load.

any idea what could be wrong here

oh and early today i loaded traktor that was like a breeze loading and everything works fine there so its nothing to do with ram

 

did you move your samples or your user library to this new drive?

 

Someone on Mac can help but you probably have Maschine scanning your entire drive for plug-ins. There are two files you need to delete that store your plug-in paths then restart. Not on Mac so I don't know the location.

 

could be one of the dll file from ur vst for example sample tank so u may need to delete and dlls of vsts that dont work with maschine

 

dll are for PCs

the op is a Mac person. on a Mac, it is VSTs and AUs.

to clarify, there might be some troublesome VST and AUs that are causing this, so you should remove all your plugins temporarily form you folders to see if this helps.

i think the problem is updating your Ram and Hardrive. did you do this after installing Maschine?

sowari

 

I think this may be the scan on whole drive issue. A single plug may stall the scan or even crash it but not do the infinite scan thing. The files that must be deleted on PC are two XML docs plugins ia32 and plugins x64. They are located where the database files are. Not sure the mac location. I would try a reinstall first to see if that will correct it. Otherwise, I have only seen that deleting those files help.

Edit: Looking through the tech support erea and the knowledge base, I see no mention of the issue of scanning whole C: drive happening on Mac so it may not apply. If none of the suggestions here work then contact support.

 

Machine is looking for samples or getting stuck on the folder with plugins, I guess. I would rename that folder , the one that holds au and vst 's , temporarily to see if machine loads up. Rename to /backup (+ original folder name )

If that solves the problem, then you should try this:
Just create a folder that has the correct folder name for the plugin folder.
And one easy way to check for a problematic plugin when you don't have too many of them, is to reintroduce them one by one in the plugin folder until your daw or machine get's stuck during loading, then you know which vst or au is the culprit.