Plugin scanning
- KVRAF
- Topic Starter
- 4892 posts since 3 Jan, 2003 from Vancouver
I guess it's worth trying, but to be honest Tracktion has been miserable at scanning plugins for longer than I've had an antivirus program installed. It's always made me wonder what the hell it's doing to take so long. I swear it gets stoned and is distracted by its hand for half an hour...
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
So *that's* why my music always sounds like unfocussed noodling - it's cos my sequencer is stoned. I'd always figured it was cos I have no talent. 
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
As a quick test, what happens if you have that as your only installed plugin when doing a scan? (I.E put that plug in a folder by itself and have Tracktion look for plugins only in that folder)
If it still freezes, then most likely Tracktion doesn't like that plug. If it doesn't, it suggests that somehow some plugins are interfering with each other during scanning (which would explain why some people have problems and others don't).
If it still freezes, then most likely Tracktion doesn't like that plug. If it doesn't, it suggests that somehow some plugins are interfering with each other during scanning (which would explain why some people have problems and others don't).
Someone shot the food. Remember: don't shoot food!
-
- KVRian
- 1112 posts since 17 Jul, 2003 from Kauai, HI
Pough! (Just to get your mind off your troubles, may I suggest you post some spring photos in OT?)
Tom
Tom
-
- KVRAF
- 1884 posts since 9 Feb, 2004 from Rochester, MN
The demo works fine here. I have automatic plugin scanning disabled, but when checking for new plugs, it takes about 30 seconds total.
I've always thought that scanning could be faster, but in this case, there must be a software conflict involved. I can't imagine a simple plugin scan taking even 10 minutes, let alone half an hour or the better part of a day.
I've always thought that scanning could be faster, but in this case, there must be a software conflict involved. I can't imagine a simple plugin scan taking even 10 minutes, let alone half an hour or the better part of a day.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
It's the plug-ins. Unfortunately, Tracktion should have some sort of way of deciding, "Nah, this plug-in doesn't want to cooperate" and simply put it to the refused list instead of trying for that long.
When a plug-in is sometimes on the 'rejected' list and sometimes not, I wonder what's causing that.
When a plug-in is sometimes on the 'rejected' list and sometimes not, I wonder what's causing that.
-
- KVRAF
- 1527 posts since 3 Apr, 2002 from desolation row
Pough, I have Morphing Delay 2.1 and do not have any problems whatsoever, either with T1 or T2. Also, now I am running T2, I have turned of the scan for new plug-ins at every startup, and just do the quick scan if I install a new one. I feel that Tracktion starts reasonably quick. BTW, I only have 50-60 plu-ings in my folders. Also, although probably not related, all my plug-ins are in Tracktion/plugins, not Tracktion2/pluginspough wrote:Yeah, but half an hour was conservative. It ran all day, just looking at the one plugin: Morphing Delay. Does anyone else have that plugin?
...
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
-
- KVRAF
- 3745 posts since 29 Sep, 2002 from Killafornia
I'm late to the party but damn thats funnypough wrote:What exactly is Tracktion doing during a plugin scan? Taking each pluging out for tea and strumpets and having a nice chat?
Tracktion starts up MUCH faster for me the second time. So if I open it, close it (wait for process to die), then open it again, its about 10 times faster on start up. Maybe tracktion isnt saving the last scan information or something.



