when i install new plugings often they automatically appear in the "Files to ignore when searching" field of the settings>plugins page (and are not available in my edits of course).
Does anyone know why a plug gets automatically placed here, and if there's anything i can do to prevent it? (i have tried manually deleteing their names from the list, but they reappear there again as soon as i rescan my directories)
any ideas? thanks
Vsts: "Files to ignore when searching"
-
- KVRist
- 453 posts since 10 Jul, 2003 from Rotterdam
-
- KVRist
- Topic Starter
- 453 posts since 10 Jul, 2003 from Rotterdam
It seems to affect certain dll files..
I notice that the free smex plugin: KTAudioHealer.dll seems to regularly cause problems for me. When i scan, sometimes it shows up in the ignored list.. sometimes not (and then it's available in my edits ).
I notice that the free smex plugin: KTAudioHealer.dll seems to regularly cause problems for me. When i scan, sometimes it shows up in the ignored list.. sometimes not (and then it's available in my edits ).
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
try temporarily removing ALL your other plugs (eg: rename your "plugins" folder "_plugins") and re-scan with only the problem dll present.
If it works now, it probably means you had an id conflict with another plug.. you just need to find which one, and decide if the new plug is worth getting rid it.
If it works now, it probably means you had an id conflict with another plug.. you just need to find which one, and decide if the new plug is worth getting rid it.
-
- KVRist
- Topic Starter
- 453 posts since 10 Jul, 2003 from Rotterdam
thankyou, i'll try that (some feedback from tracktion that an id conflict was causing the 'ignoring' would be helpful).
-
- KVRist
- 317 posts since 13 Oct, 2001 from Mars
Dunno who started saying ID conflict is an issue in T. AFAIK, you can have several copies of the same dll and have them all running at the same time - as long as each one is named distinctively.cbit wrote:thankyou, i'll try that (some feedback from tracktion that an id conflict was causing the 'ignoring' would be helpful).
Only some hosts scan for ID conflict, and T most likely isn't one of them.
-
- KVRist
- Topic Starter
- 453 posts since 10 Jul, 2003 from Rotterdam
I've looked through a bunch of similar posts querying why this ignore list thing happens.. but didn't find any definitive answers.
TheWall: if its not an ID issue, and no plugins share the same .dll filename, do you know why this might be happening? (this still seems like the most likely explanation to me).
TheWall: if its not an ID issue, and no plugins share the same .dll filename, do you know why this might be happening? (this still seems like the most likely explanation to me).
-
- KVRist
- 317 posts since 13 Oct, 2001 from Mars
Hi cibit,cbit wrote: TheWall: if its not an ID issue, and no plugins share the same .dll filename, do you know why this might be happening? (this still seems like the most likely explanation to me).
Honestly, I don't know.
I understand it's frustrating. But the only thing we users can do to ease the situation is probably by urging the plugin dev to contact Jules for more info. Just remember, not all plugin devs(some commercial devs included) are interested in solving issues with a non-big3 host...
-
- KVRist
- Topic Starter
- 453 posts since 10 Jul, 2003 from Rotterdam
thanks TheWall, your answer was confirmed by niall from ndc plugs too.. he also says tracktion doesn't scan for plug ids.
one of his plugs is affected in this way on my system.. hopefully we can figure out what's going on.
one of his plugs is affected in this way on my system.. hopefully we can figure out what's going on.
-
- KVRist
- 300 posts since 11 Feb, 2003
My guess is that plugins get into the ignored list when:
- The DLL fails to load or not a VST plugin like MSCRT.DLL, etc.
- Maybe when it causes an exception and Tracktion catches it and put it in the list (which is similar to the above)
A plugin that fails to load might have a success next time you try so thats why clearing the list might help to allow Tracktion to try and load them again
Plugin IDs are related to preset files and other plugin stored data but not to loading plugins
- The DLL fails to load or not a VST plugin like MSCRT.DLL, etc.
- Maybe when it causes an exception and Tracktion catches it and put it in the list (which is similar to the above)
A plugin that fails to load might have a success next time you try so thats why clearing the list might help to allow Tracktion to try and load them again
Plugin IDs are related to preset files and other plugin stored data but not to loading plugins