Just Back from NAMM and more Tracktion info for you.

[valley]

On the other hand the fastest and most stable plugin scan I know of overall is in Audiomulch - I just don't know how the dev managed it, it's quite astounding, even the initial scan is only a few seconds and after that startup is almost instant and I've never known it to crash while scanning. Maybe you should commission the dev to work with you.

in other words its scan is basically

dir /%vstplugins%/*.dll

I imagine the Tracktion devs could get that working quite well by themselves.

[fandango]

1. No change.
2. No change. The line tool still depends on snap level for controllers.
Ben

That's a shame. Thanks for the reply though.

[Mr. Tingle]

On the other hand the fastest and most stable plugin scan I know of overall is in Audiomulch - I just don't know how the dev managed it, it's quite astounding, even the initial scan is only a few seconds and after that startup is almost instant and I've never known it to crash while scanning. Maybe you should commission the dev to work with you.

in other words its scan is basically

dir /%vstplugins%/*.dll

I imagine the Tracktion devs could get that working quite well by themselves.

If it works so well though, why not use it?

[koolkeys]

They don't use it because they choose a more stable scan, and one that will automatically flag bad plugs so they don't stop the scan the next time.

Maybe just an option as to what kind of scan to do would be nice. That way, it will make both sides of this happy.

But with a basic scan, there DOES come the possibility that you have more troubles with bad plugs.

Brent

[valley]

in other words its scan is basically

dir /%vstplugins%/*.dll

I imagine the Tracktion devs could get that working quite well by themselves.

If it works so well though, why not use it?

It doesn't. Anything that is a dll will get hoovered up, which includes stuff that isn't a plugin, which your host will find out the hard way when you try to open it.

[Mr. Tingle]

They don't use it because they choose a more stable scan

On the other hand the fastest and most stable plugin scan I know of overall is in Audiomulch

So, is it more stable or not, who is right?

[Mr. Tingle]

I think the only thing that really needs to be done is have a little box that pops up when you do a scan and shows the plugin being scanned, next to this would be a 'skip' button that could be pressed if tracktion seemed to get stuck. problem solved.

[Warmonger]

They don't use it because they choose a more stable scan

On the other hand the fastest and most stable plugin scan I know of overall is in Audiomulch

So, is it more stable or not, who is right?

Audiomulch is more stable at scan time. Since it's not loading the DLLs, there's no reason for the scan itself to be unstable. Tracktion's approach is more stable once the app is launched, since incompatible plugins have less chance of being loaded.

When would you rather have your DAW crash, at load time or in the middle of a session?

That said, I'd love to have the option of a super-quick plugin scan that works that way.

[semiquaver]

Ts scan is about 10 times faster than DP's on Mac. And I would rather have T crash during scan than while working! that said if there is a way for a scan to fail w/out crashing T that would be great. I should note that all 3 hosts I use regularly (T, DP, Live) will crash occasionally during a scan.

[pough]

Regarding plug-in scan. There are definitely ways to improve it and there are some great ideas in this thread.

Appreciated.

[Integratron]

I run hundreds of plugs and T has never hung or crashed - do you know specifically, what plugs are doing this?

[pough]

I've spent the evening running some tests. A scan is currently running and it will probably take quite some time. I'm looking at the log file while it's going. At the start, plugins get scanned at a rate of one per two seconds. It's slowed down to one per 30 seconds right now and I'm not staying awake to see how it all turns out. I'm not sure if it's one or two plugins in particular or if it's just a cumulative effect. I'll plot a graph or something.

[\m/]

* is glad not to use a lot of plugins.. yet *

As no answer forthcoming to same question about T3... to folks who got the T2 physical version :

Did it come with printed documentation?

[jplanet]

I run hundreds of plugs and T has never hung or crashed - do you know specifically, what plugs are doing this?

Vaz always crashes T2 for me.
BFD-all and groups used to, now it's ok.
Occasionally the Steinberg Grand will cause a crash.

[valley]

* is glad not to use a lot of plugins.. yet *

As no answer forthcoming to same question about T3... to folks who got the T2 physical version :

Did it come with printed documentation?

Not full printed documentation. There was a printed user guide, and a larger PDF reference manual.

Probably T3 will follow a similar path. The printed documentation may even be smaller given that there seems to be a video included.