I don't get how T7 scans plugins

[killmaster]

T7 hangs on SO many more plugins that any of my other DAWs. Its taking hours go through the AU and VST scanning cause it keeps hanging and I have to cancel and restart the scan. It literally is unable to scan over 100 VST plugins (and 7 or so AU plugins) which validated fine in Logic. No real issues with Presonus Studio One 3, Ableton Live 9.6 or Bitwig either.

Why would this be?

thanks for any help or information!

Greg K.

[dRowAudio]

It's probably one or two individual plugins that are hanging which is causing the whole scan to appear to take a long time. Can you see if it gets stuck on a specific plugin?

Do some of these plugins pop up windows during a scan? It's possible that the plugin is waiting for some user input. If there isn't any for a long period of time Tracktion will just kill the plugin and attempt to move on.

[killmaster]

It's probably one or two individual plugins that are hanging which is causing the whole scan to appear to take a long time. Can you see if it gets stuck on a specific plugin?

Do some of these plugins pop up windows during a scan? It's possible that the plugin is waiting for some user input. If there isn't any for a long period of time Tracktion will just kill the plugin and attempt to move on.

Its been hanging on literally hundreds for many minutes til I cancel out, then when it rescans, it seems to mark those plugins as bad and shows me this list of those plugins it couldn't scan. All plugins that work fine and validate fine with all my other DAWs. I've been working on getting at least one completely scan through of my VST directory since last night!

On a couple occasions its returned a dialog box for expired demos but that is expected.
I've never had this issue before. Even in earlier versions of Tracktion (T4 and T5).

[killmaster]

I don't know how it evaluates wether a plugin will load ok or not but it seems like it fails too easily. Maybe there's a maximum number of plugins it will allow? Cause its near the end of my VST scan, and its failing on almost every one now.

[TSC]

May have hit a collection of plugs from the same vendor that shares the same code issue - plugin code is all over the map. The initial load tests are aimed to be a balance of speed and accuracy - thoroughly testing a plugin would take a long time - however not testing enough would increase instability - and if a plugin crashes, it typically will take down the system. Even sand boxing cannot guarantee a plugin will not take down the host. It is a common misconception that because a plugin is a VST or AU, then it is standardized code - its is not

[killmaster]

May have hit a collection of plugs from the same vendor that shares the same code issue - plugin code is all over the map. The initial load tests are aimed to be a balance of speed and accuracy - thoroughly testing a plugin would take a long time - however not testing enough would increase instability - and if a plugin crashes, it typically will take down the system. Even sand boxing cannot guarantee a plugin will not take down the host. It is a common misconception that because a plugin is a VST or AU, then it is standardized code - its is not

At about 85% in my VST folder now and its literally, literally hanging on every single plugin. From NI Driver to Circle2. All other the place, not just one vendor. Something can't be right with this. Never had this issue before...

Seems to be in the "C"s now. For instance, its been hung on Glitchmachines Cataract for 15 minutes. I usually wait 15 minutes to see if it will load. These plugins I mention validate instantaneously in my other hosts.

[killmaster]

Even is hanging on BioTek demo!

[Ben di Arrows]

This is not really a solution but if you drag the dlls in from a file browser one by one you may have more success. Why this sometimes works is beyond me.

[killmaster]

This is not really a solution but if you drag the dlls in from a file browser one by one you may have more success. Why this sometimes works is beyond me.

Sorry, forgot to mention that I'm on OSX. I'm giving up on this. Basically it doesn't like nearly all of my VST. Not useable for me like this. I think it must be a bug or incompatibility with El Capitan? Maybe I have too many plugins? Who knows...

[aMUSEd]

This is not really a solution but if you drag the dlls in from a file browser one by one you may have more success. Why this sometimes works is beyond me.

Sorry, forgot to mention that I'm on OSX. I'm giving up on this. Basically it doesn't like nearly all of my VST. Not useable for me like this. I think it must be a bug or incompatibility with El Capitan? Maybe I have too many plugins? Who knows...

You can still drag in the VSTs and components you want to use. Sometimes I have the same problem with Logic's plugin scan - if I let it scan it gets choked up, but then I find if I go back into the plugin manager and scan the ones that got blacklisted one by one it scans them fine.

Actually what I have at the moment is a special folder containing symlinks to all the plugins I use in several hosts inc Tracktion, that way I can control exactly what gets scanned in and how they are organised and it scans a lot faster than the full plugin folder.

[killmaster]

This is not really a solution but if you drag the dlls in from a file browser one by one you may have more success. Why this sometimes works is beyond me.

Sorry, forgot to mention that I'm on OSX. I'm giving up on this. Basically it doesn't like nearly all of my VST. Not useable for me like this. I think it must be a bug or incompatibility with El Capitan? Maybe I have too many plugins? Who knows...

You can still drag in the VSTs and components you want to use. Sometimes I have the same problem with Logic's plugin scan - if I let it scan it gets choked up, but then I find if I go back into the plugin manager and scan the ones that got blacklisted one by one it scans them fine.

Actually what I have at the moment is a special folder containing symlinks to all the plugins I use in several hosts inc Tracktion, that way I can control exactly what gets scanned in and how they are organised and it scans a lot faster than the full plugin folder.

Ok, thanks for the tips. I will try to drag them and see. I didn't realize they would show up if it couldn't load them during the scanning test...

[TSC]

Check the bit rates too - if lots of plugins are struggling, you may be running conflicting bit rates

[killmaster]

Check the bit rates too - if lots of plugins are struggling, you may be running conflicting bit rates

hmmm. not sure what you mean. I'm having issues mainly with the initial scanning of my plugin directories. Bit rate per plugin wouldn't be an issue here would it? I'm not talking about opening edits which have plugins loaded in them...