I agree. FL and XT don't give a damn if the plug-in is actually compatible or not, which is why the "scan" (there is no scan, it just generates a list of names) is so fast.
That's NOT the correct way of doing things.
However, I guess it would be nice as an option for impatient people (not Rock or others with a similar problem-- 2 hours is insane and no longer a matter of patience) to have 'kamikaze' mode that will let you include any and all plug-ins.
Duplicate plug-ins can definitely be a problem, and the fact that you 'can' load them in XT doesn't mean that you're not going to crash the heck out of your program right in the middle of a song. And if you hadn't saved recently... ugh.
Greg
FR: Manual addition of new VST filters
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
-
- KVRist
- 436 posts since 13 Jul, 2004 from Bayonne, NJ
I think I'd sacrifice reliability for speed considering I rarely have a plugin that causes problems. Come to think of it, earlier versions of DR Fusion would crash T and yet it passed the scan so there's no guarantees anyway. Scanning for new plugs should hardly take any time at all if a list of known and previously scanned plugs is kept by T.
I'd like to see an option, with a disclaimer if necessary, to quick load VSTs. I'll take responsibility for the outcome just like I do with EnergyXT and FL studio. Tracktion is my favorite host but I always end up loading something else first when inspiration hits because I don't want to wait for the tedious load time.
J
I'd like to see an option, with a disclaimer if necessary, to quick load VSTs. I'll take responsibility for the outcome just like I do with EnergyXT and FL studio. Tracktion is my favorite host but I always end up loading something else first when inspiration hits because I don't want to wait for the tedious load time.
J
-
- KVRist
- 436 posts since 13 Jul, 2004 from Bayonne, NJ
Lunch Money wrote:I agree. FL and XT don't give a damn if the plug-in is actually compatible or not, which is why the "scan" (there is no scan, it just generates a list of names) is so fast.
That's NOT the correct way of doing things.
However, I guess it would be nice as an option for impatient people (not Rock or others with a similar problem-- 2 hours is insane and no longer a matter of patience) to have 'kamikaze' mode that will let you include any and all plug-ins.
Duplicate plug-ins can definitely be a problem, and the fact that you 'can' load them in XT doesn't mean that you're not going to crash the heck out of your program right in the middle of a song. And if you hadn't saved recently... ugh.
Greg
Kamikaze mode...I love it! That's what I want. I hope Mackie/Jules use that term for that feature too...I know Mackie has a sense of humor.J
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
JoMal - plug-ins can definitely still crash, so you're right that it's not a guarantee. Tracktion has no way of testing each situation that could arise with each plug-in that could cause it to crash; however, it DOES check for basic things like the plug-in ID. If even just one developer fails to register his plug-in ID in the Steinberg database, destruction, anarchy, and much wailing of women will ensue can ensue if another plug-in has the same ID.
The IDs are only 4 digits, so it's pretty tricky coming up with new ones and I think some developers are very lazy about registering them.
So, to sum up the thread so far:
- 2 hours is insane
- dodgy plug-ins or duplicates can and will screw up Tracktion's deep scan
- Kamikaze Plug-in mode would be sweet for many users
The IDs are only 4 digits, so it's pretty tricky coming up with new ones and I think some developers are very lazy about registering them.
So, to sum up the thread so far:
- 2 hours is insane
- dodgy plug-ins or duplicates can and will screw up Tracktion's deep scan
- Kamikaze Plug-in mode would be sweet for many users
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
how about an option in kamikaze mode that saves the edit every time you add a new filter
Then it would be like safe-kamikaze mode
RonC
Then it would be like safe-kamikaze mode
RonC
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
also next ver add a timer so we can report exactly how long it took to get vst's setup 
RonC
RonC
-
- KVRist
- 436 posts since 13 Jul, 2004 from Bayonne, NJ
Yes indeedLunch Money wrote: - Kamikaze Plug-in mode would be sweet for many users
J
-
- KVRist
- 436 posts since 13 Jul, 2004 from Bayonne, NJ
Where's your sense of adventure, Ron?rpc9943 wrote:how about an option in kamikaze mode that saves the edit every time you add a new filter
Then it would be like safe-kamikaze mode
RonC
J
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
-
- KVRist
- 436 posts since 13 Jul, 2004 from Bayonne, NJ
oh, them.
-
tony tony chopper tony tony chopper https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=3103
- KVRAF
- 3561 posts since 20 Jun, 2002
I agree. FL and XT don't give a damn if the plug-in is actually compatible or not, which is why the "scan" (there is no scan, it just generates a list of names) is so fast.
That's NOT the correct way of doing things.
It's the correct way of doing things in a world with so many crap plugins.
FL also features a 'kamikaze' mode, but the kamikaze mode is the one that SCANS plugins. Anyone who tests new plugins from time to time & has grown a little list just can't scan them all - they simply end up crashing. And in the best case, you wait a lot (hence this thread), closing tons of 'hello, this is my new plugin, plz give feedback' or 'you need to register' stupid dialog boxes, because the programmers made them appear when their DLL is opened.
Yes scanning plugins is the correct way of doing things, but not in this world. Ideally VST's should be registered in the registry, like DX plugins, so you wouldn't need to scan them.
-
- KVRAF
- 5851 posts since 9 Jul, 2002 from Helsinki
Just to cheer you up, Rock - "Scan for new plugs" on my DAW takes just some seconds. It's so fast I never realize that it's already over. My total plug count is around 60, most of them are effects I've never even tried
W2K, Athlon XP1700+, 1,5 Gb of PC2100 DDR, 40+80 WD Caviar disks with 8Mb buffers, so nothing esoteric, actually a rather modest machine. However I spend a good amount of time with basic maintenance - uninstall tested plugins that I didn't like, cleaning registry and defragging. I have also disabled a considerable amount of services, as it's a dedicated OS.
Maybe there should be a thread about scan issues where people would post complete machine & OS specs to track down the problem?
W2K, Athlon XP1700+, 1,5 Gb of PC2100 DDR, 40+80 WD Caviar disks with 8Mb buffers, so nothing esoteric, actually a rather modest machine. However I spend a good amount of time with basic maintenance - uninstall tested plugins that I didn't like, cleaning registry and defragging. I have also disabled a considerable amount of services, as it's a dedicated OS.
Maybe there should be a thread about scan issues where people would post complete machine & OS specs to track down the problem?
-
- KVRAF
- 8144 posts since 13 Jan, 2003 from Darkest Kent, UK
In my ignorance, can't Tracktion check the plug as it's loaded? Surely it could keep a little list of all ids used in the edit and scan that when a plugs requested?
Funnily enough I was playing with SavHost last night (just that much quicker to check new plugs with than T). I thought then whether T could ever offer a similar feature, browse for a plug with a normal file open dialogue. Would be handy when auditioning.
.g
Funnily enough I was playing with SavHost last night (just that much quicker to check new plugs with than T). I thought then whether T could ever offer a similar feature, browse for a plug with a normal file open dialogue. Would be handy when auditioning.
.g
-
- KVRian
- Topic Starter
- 1272 posts since 11 Apr, 2002 from Nashville, TN
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Sux. I like Gary's idea. You could OPT for a global scan if you're such a person, or you could have them scan on-the-fly.
TTC-- there are obvious exceptions or Rock wouldn't be having his problems, but in Tracktion, if a plug-in has problems, Tracktion WILL stop scanning it and put it on an ignore list, it won't (again, Rock has an obvious exception!) simply scan it forever, er... generally...
Rock, I feel your pain, but I still don't understand why you keep scanning all your plug-ins!! Don't you just check for new ones as you add them?
Greg
TTC-- there are obvious exceptions or Rock wouldn't be having his problems, but in Tracktion, if a plug-in has problems, Tracktion WILL stop scanning it and put it on an ignore list, it won't (again, Rock has an obvious exception!) simply scan it forever, er... generally...
Rock, I feel your pain, but I still don't understand why you keep scanning all your plug-ins!! Don't you just check for new ones as you add them?
Greg