Remember the problem where Max was chewing for ages without using any cpu while scanning the vst folder ? I fixed it on my box by removing a folder full of .pat files (patterns for the Audio Realism drum machine). But it seems another problem occur now with the 5.0.6 update. I can use the vst~ object anymore again...

vst-scanning-problem-back-again-in-5-0-6-win-xp

May i suggest Max not to scan vst folders anymore, to get rid of this persistent problem ? Vst~ will crash when it will loading specific troublesome plugins, but will let us work with the other ones.

This is all related to database harvesting and adding files to the search path. There was some work done to remedy it in 5.06 but we realise that we're not there yet. We're working hard on a solution for this right now.

Thanks for the note about difficulties with non-Max .pat files. We'll check it out.

One thing you might try to get vst~ working is add your vst folder to Max 5's file paths explicitly. You will get an extra bit of waiting when you first restart while your VST folders are scanned, but hopefully the vst~ object will load quickly.

If the problem is caused by a vstplugins folder that has a *lot* of files (i.e. closer to 1000 than 100) then this will be fixed in 5.0.7 -- it clearly is not fixed in 5.0.6. The interval between the release of 5.0.6 and 5.0.7 will probably be much shorter than the interval between 5.0.5 and 5.0.6. I don't think you'll have to wait that long.

Basically, there was a windows-version specific issue that would cause max to slow down exponentially as the number of files in a folder grew. So, 5.0.7 on windows should work much better with folders that have large numbers of files.

Now, if the problem is due to max getting confused by .pat files then that might be something else, but we'd have to investigate that further.

Finally, if there are problems due to certain vst plugs crashing then please email support at cycling with the specific plugs and we can see what we can do.

If the problem is caused by a vstplugins folder that has a *lot* of files (i.e. closer to 1000 than 100) then this will be fixed in 5.0.7 -- it clearly is not fixed in 5.0.6.  The interval between the release of 5.0.6 and 5.0.7 will probably be much shorter than the interval between 5.0.5 and 5.0.6.  I don't think you'll have to wait that long.  

Basically, there was a windows-version specific issue that would cause max to slow down exponentially as the number of files in a folder grew.  So, 5.0.7 on windows should work much better with folders that have large numbers of files.  

Now, if the problem is due to max getting confused by .pat files then that might be something else, but we'd have to investigate that further.  

Finally, if there are problems due to certain vst plugs crashing then please email support at cycling with the specific plugs and we can see what we can do.  

vst~ scanning problem back again in 5.0.6 (win XP)