OMG - More VST loading problems

[Scoops]

Man....
I cant believe it. I added 9 new VST's to my startup search path and it increased the time it took to open T by 3 whole seconds.

I find this totally unaccepatble, so to rid myself of this problem, I'll be going back to my tape deck.
Like all I have to do there is turn it on.

Have a nice day
Scoops

[djsubject]

Man....
I cant believe it. I added 9 new VST's to my startup search path and it increased the time it took to open T by 3 whole seconds.

I find this totally unaccepatble, so to rid myself of this problem, I'll be going back to my tape deck.
Like all I have to do there is turn it on.

Have a nice day
Scoops

3 hole seconds??!! bin tracktion!!!

Thats what ron would do


sorry i thought it was funny

[Lunch Money]

I would also bin Tracktion if I were you.

Either that, or disable start-up scanning. <grin>

(ie. I knew you were joking, but I also wasn't sure if you knew about that)

Greg

[Scoops]

Hey Lunch

Yeah I was jus joking, and yes I was aware of the disable feature, but......just out of curiosity, how many plugins does it take to cause an opening time in excess of say 20 second? I have about 75 in my current search path and it still only takes less than 10 seconds.

Scoops

[Lunch Money]

No idea. I think I only have about 40 installed right now. I did have about 200 at some point in time and I could easily imagine it having taken 20 seconds though I don't remember the actual time offhand.

Greg

[IIRs]

It takes me about 6 secs to launch T with scan off.

Scanning for new plugs just took about 75 secs.

A full re-scan was getting on for 3 minutes.

Maybe I need to streamline a bit..

[Lunch Money]

I just did a re-scan and I don't even have that many plug-ins (relatively), and I clocked in at 25 seconds, by which I mean that it took longer than I expected.

Even if I re-scan the entire directory once a week, that's only 25 seconds.

Greg

[IIRs]

Its when I repeatedly open up a home-made SE plug in Tracktion only to discover a small niggly mistake that will take 10 seconds to correct in SE, that I start to resent scanning times of a minute or more..

I never said it was a big deal though, just that I would personally use an option to scan just one specific directory quite regularly, if it was there.

[JoMal]

hmmmm. Can someone explain this to me?

When I first load Tracktion after a fresh boot, a full scan takes 2 minutes and a "new plugin" scan takes about 1:40 minute. I have a ton of plugs so that's probably why but here is the strange thing:
If I shut down Tracktion then open it again (not rebooting computer) it only takes about 15-20 seconds for a "new plugin" scan. It's like Tracktion is storing the results of it's previous scan somewhere but those results are lost if the computer is re-booted and Tracktion loaded from scratch. Hope this makes sense.

J

[chico.co.uk]

Do you reboot, and start Tracktion immediately? In other words, has you machine actually finished booting yet? Even on a fast machine on xp, if you have a few apps set on startup, it takes a couple of minutes for it to properly settle down and load them all into memory, page them out etc.

In other words, if you reboot, f**k off downstairs and make a coffee, and watch the simpsons for fifteen minutes, then come back up and start up Tracktion, does it still lag? If not, it's your startup routine you want to look at, not Tracktion.

Also, try turning off any real-time A/V scanners you have running while starting Tracktion.

[JoMal]

Do you reboot, and start Tracktion immediately? In other words, has you machine actually finished booting yet? Even on a fast machine on xp, if you have a few apps set on startup, it takes a couple of minutes for it to properly settle down and load them all into memory, page them out etc.

In other words, if you reboot, f**k off downstairs and make a coffee, and watch the simpsons for fifteen minutes, then come back up and start up Tracktion, does it still lag? If not, it's your startup routine you want to look at, not Tracktion.

Also, try turning off any real-time A/V scanners you have running while starting Tracktion.

No, I usually don't start Tracktion right away - so the computer has plenty of time to settle down. This load time is not really a big deal to me but I was curious as to why, after shutting down Tracktion and then reloading it again, the start up time was noticeably faster the second time. I will try without the virus scanner running and see what happens....I need to get into the habit of turning that off while recording anyway.
Thanks

J

[SaviorNeeded]

My impression is: any program loads faster the second time if you start it up just after shutting it down. Tracktion does this, Word, Coreldraw...I think Windows tries to keep things in memory just for this purpose. When you move on to something else, then the load time goes back to normal.

BTW, in all the discussions about Tracktion's load and rescan times (in this and other threads) I've never seen anyone mention CPU speed and memory. My slower machine (1.6 gig, 512 meg) takes longer than most of the times mentioned by others. In other words, it's not just number of VSTs, I'd guess.

Tom

[androidlove]

platinumears wrote:
"Its when I repeatedly open up a home-made SE plug in Tracktion only to discover a small niggly mistake that will take 10 seconds to correct in SE, that I start to resent scanning times of a minute or more..

I never said it was a big deal though, just that I would personally use an option to scan just one specific directory quite regularly, if it was there"

Before putting VST's into my Tracktion VST folders, I test them in CMuzys because it imports 1 plug at a time.

[rpc9943]

hey why cant we get a "import single dll"

RonC

[JoMal]

My impression is: any program loads faster the second time if you start it up just after shutting it down. Tracktion does this, Word, Coreldraw...I think Windows tries to keep things in memory just for this purpose. When you move on to something else, then the load time goes back to normal.

BTW, in all the discussions about Tracktion's load and rescan times (in this and other threads) I've never seen anyone mention CPU speed and memory. My slower machine (1.6 gig, 512 meg) takes longer than most of the times mentioned by others. In other words, it's not just number of VSTs, I'd guess.

Tom

I've noticed that too now that I think of it (programs loading faster the 2nd time). I have an old machine - 1.4 gHz and 512M ram - so......I'm sure that plays into it. The wait for the VST scan is tolerable though, I was just curious.

J