Slow VST Scan - Jamstix or StompBud owners please help me!

[Integratron]

pough,

you have tried this with your a/v services stopped, right?

I'm not sure what you mean by a/v services stopped?

I mean kill your antivirus program. Don't just stop the executable, if it runs as one or more services, disable those services and try the plugin scan without them running.

oh right, anti-virus - no a/v and really no probs with scans - I thought you meant audio/video

[chico.co.uk]

TEST #4
No Jamstix, so StompBud and NO VIRUS SCANNER
Total Time: 00:02:58
Average: 00:00:01

133 - first half
Total Time: 00:01:06
Average: 00:00:00

133 - second half
Total Time: 00:01:52
Average: 00:00:01

chico, you're the man!

And even after putting Jamstix back in, the difference in time is negligible. Holy shit. There goes days of research...

ooops, sorry mate.

But seriously, that's still a really good catch on your part. It makes sense that if the T scan loads a large soundset into memory when it loads a dll to check it, then the realtime scanner in your a/v will check the sampleset out for malware. So maybe there's still scope for an option to "quick scan" plugs that doesn't involve actually loading the dll (if that's technically possible ...)

[pough]

So maybe there's still scope for an option to "quick scan" plugs that doesn't involve actually loading the dll (if that's technically possible ...)

I should think so; it's what some of the other hosts do. Maybe they'll add it just to avoid having more people like me whine about it without realizing that it's the virus scanner to blame!

[koolkeys]

Well, part of it is Tracktion's fault, if it does indeed load each .dll to test it. If it didn't test it, it wouldn't scan it, right?

My only wonder is why it takes SO LONG for you to scan with those plugs, even with the virus scan on. It really shouldn't take that much time. Could it really be due to the scanner scanning each file that's being loaded?

By the way, I have to admit that in my years with Tracktion, I haven't seen confirmation that Tracktion actually LOADS each plug during the scan. Not saying it doesn't, but has that been confirmed? If so, then this all makes sense.

Brent

[chico.co.uk]

I think the counter argument has always been that if the plug is dodgy that should show up during the scan, and be marked as not a valid VST, rather than risking crashing T when it's first loaded in a real project. So it's a double edged sword, you could speed up plugin scans at the cost of having what would look like an apparently less stable Tracktion.

Although it would be the plug that wasn't stable, all the end user would see would be Tracktion crashing, and they inevitably blame the host app ...

[koolkeys]

Which is why I don't mind the scan this way. I think it should be the way it is by default, with a warning next to the option to turn it off explaining what could happen.

Brent

[rockstar_not]

pough,

Have you shut off your virus-scanning software before you do the plugin scan?

Please try this - it changed the world for me with Tracktion.

-Scott

[Zauni]

Glad to hear disabling the A/V scan fixed the problem.

We do have one report of crashes of Jamstix in T2 (from Integratron who we supplied with a special demo beta DLL). If any other of you experience crashes of T2 with Jamstix, please let us know via the Rayzoon support forum or e-mail so we can research this.

[koolkeys]

Thanks Zauni! And it's good to hear(from your forums) that JS2 will not load the samples except when loading a song.

Brent

[pough]

Have you shut off your virus-scanning software before you do the plugin scan?

One page ago.

Yes, children, the moral of the story is: antivirus programs gummy up the plugin scan something fierce. Compare these two times:

01:01:23 vs 00:02:58

What a difference!

[rockstar_not]

Have you shut off your virus-scanning software before you do the plugin scan?

One page ago.

Yes, children, the moral of the story is: antivirus programs gummy up the plugin scan something fierce. Compare these two times:

01:01:23 vs 00:02:58

What a difference!

Great - you'll see I suggested this on page #1 of the thread.

-Scott

[DarkStar]

Curious . . .
What Antivirus software is it that causes problems during scanning?

[Lunch Money]

I keep my AVG enabled and haven't had any problems, so I'm guessing not that one.

[pough]

I keep my AVG enabled and haven't had any problems, so I'm guessing not that one.

Good guess, but incorrect. I'm using AVG.

[pough]

Great - you'll see I suggested this on page #1 of the thread.

Yup, but it didn't seem to match my scenario (you said your scan was shorter than 5 minutes and mine was almost two hours) so I continued to test on what seemed to be giving me information that made sense to me. I did the AV test after I was satisfied that there really is something goofy about certain plugins that affect the loading of all the plugins afterwards. I still think there are issues that could be addressed, but 3 minutes is far less worrisome than two hours.