Plugin scanning is just so tedious

[aMUSEd]

Strange. In my system it just takes 3 minutes and I have much plugins.
Running Tracktion on vist.

It's OK for VST, the problem is with AU and no other host I know restarts the scan from 0 every time. They just scan what is new.

[aMUSEd]

Reading the original post, I wonder if you're even using the same program as me??

The latest version now rescans my entire plugin folder in a few seconds, by checking multiple plugins in parallel. I'm at a loss to know what could be slowing your machine down - even if you have hundreds of plugins, it should only take a minute at worst case.

But making the scan run from 0 whenever I run it just to add a new plugin or two is crazy

That would be crazy, but that's not what it does. It has always ignored VST plugins that it has already seen. For AUs, it does need to rescan them all because there's no way to know whether their properties have changed (it can't look at the date of the file like it can for VST), but IIRC you're a Windows user (?)

Sorry then it should scan at startup like logic does, or at least have the option, just for AU's.. why not? that way at startup it looks for new AU's in the folder.

that's the issue, Au's, and i think the OP meant the same as he's on mac also now.

Yes I'm on Mac now. The slowness is one problem but it also completely hogs the cpu. This on an i7 Mac.

[chico.co.uk]

If it's not possibel to read the AU dates, I wonder, then, how DSP Quattro and Digital Performer manage to only look for newly added AU:s when scanning?

They probably just ignore any IDs they've seen before. We could choose to do that too, but it means that if a new version of a plugin comes out which has a different name/description/number of inputs/outputs, etc, then it won't realise that those things have changed.

If every host that used Au's had to rescan them from scratch every time one plugin was changed, everyone would literally be bald. Come on.

It might be an idea to re read that exchange, because you don't seem to have understood what was explained

In fact, speaking generally, when you're telling a developer how to code their app, and they explain how it currently works, it's a good idea to try to understand the response before arguing about it. In my experience.

Ok you are a fanboy and I have been noticing all you posts diminishing people's issues with t4

< sigh >

You need to work on your reading and comprehension if that's what you're taking away from this

[Winstontaneous]

No plugin scanning issues on a Mac with Mountain Lion 10.8.4.
Installed a bunch of plugs this week, Tracktion v. 4.3.2 scanned VSTs in less than a minute, AUs in about a minute.
No different from Reaper, AudioMulch, ReNoise, Audition, or Live.

Only weirdness was that 4 or 5 Tracktion logos spawned on the Dock and whirled around while scanning, as mentioned by audientronic above.

For people with super-long scan times is it possible that there's some plugin requiring a response, like an expired demo version? I've had dialogue boxes from various Plogue and FXpansion plugins stall scanning on both Windows and Mac (in other hosts) until I clicked on them. Just a thought.