Plugins not loading after Exporting file and moving all plugins to a new folder
-
- KVRer
- 15 posts since 1 Dec, 2017
I have noticed that if the plugins are moved to a new folder, the plugins do not get re-associated with the tracks even after executing a full re-scan of all plugins. I have tried exporting the project file as an archive, but the problem remains. In such a situation, there surely must be a way whereby one is not required to re-assign all the earlier plugins to individual tracks. The question is, how does one share a Project file that has many plugins? Will the other person also have to set up a plugins folder in some specific way? Ideally, an archived file should have all associated files, plugins, etc embedded in a manner that will allow a collaborator to use the file straightaway without having to bother about how a plugins folder have to be set up.
-
- Beware the Quoth
- 35506 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
If you're genuinely suggesting that plugins be embedded in the project (rather than data about which plugins were used) then be aware that this(*) would make it illegal to give a project to anyone else, as you'd be infringing the copyright of the plugin developer.Pertinax wrote: Ideally, an archived file should have all associated files, plugins, etc embedded in a manner that will allow a collaborator to use the file straightaway without having to bother about how a plugins folder have to be set up.
(And it wouldnt necessarily work; very many plugins rely on data elsewhere on your system.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
-
- KVRAF
- 1790 posts since 30 Dec, 2012
It sounds like something else is going on here. There's a fairly exhaustive search we do when trying to load plugins that checks things like name, manufacturer etc. We even try and load 32-bit versions if there was "64-bit" in the original name.
Are you sure that the plugins have been scanned and new instances load correctly?
Are you sure that the plugins have been scanned and new instances load correctly?
-
- KVRer
- Topic Starter
- 15 posts since 1 Dec, 2017
whyterabbyt: I just felt that all plugins should remain associated with the respective tracks even if the plugins folder is relocated. I thought that embedding all components might offer a solution, but as you say there may be other legal and technical complications.
dRowAudio: I had re-scanned all plugins in the new location and they are all getting displayed in the plugins window of the "Settings" tab. So, in effect, they are all available for use. The problem is that the plugins on tracks are all getting displayed with a big red X mark. I am able to add plugins individually, and the tracks play perfectly, but you can imagine how laborious this task is going to be when there are many plugins and many tracks - let alone the trouble of re-creating individual plugin presets all over again.
dRowAudio: I had re-scanned all plugins in the new location and they are all getting displayed in the plugins window of the "Settings" tab. So, in effect, they are all available for use. The problem is that the plugins on tracks are all getting displayed with a big red X mark. I am able to add plugins individually, and the tracks play perfectly, but you can imagine how laborious this task is going to be when there are many plugins and many tracks - let alone the trouble of re-creating individual plugin presets all over again.
Last edited by Pertinax on Fri Dec 01, 2017 2:57 pm, edited 1 time in total.
-
- KVRAF
- 1790 posts since 30 Dec, 2012
A big red X means the plugin is disabled (i.e. bypassed).
If a plugin fails to load because it can't be found it will have a warning icon on it:
If a plugin fails to load because it can't be found it will have a warning icon on it:
You do not have the required permissions to view the files attached to this post.
-
- KVRer
- Topic Starter
- 15 posts since 1 Dec, 2017
Thanks so much. I stand corrected. I get your point about the red X that refers to a bypassed plugin, which I would have disabled earlier. You are also right about the warning icon. They are in fact appearing on all plugins, signifying that they are not getting loaded. But how is this possible when all the plugins are being displayed as a list in the plugins window of the "Settings" tab, and I am able to pull in individual plugins on tracks and then they seem to be working fine?
-
- KVRist
- 320 posts since 9 Sep, 2017
I don't have this type of problem in T6.
But one caveat, I do have to use the function to delete all plugins from the manager list, that can't be found any more.
You might have run into a problem of plugins listed twice, the old path and the new path.
But one caveat, I do have to use the function to delete all plugins from the manager list, that can't be found any more.
You might have run into a problem of plugins listed twice, the old path and the new path.
-
- KVRer
- Topic Starter
- 15 posts since 1 Dec, 2017
HansP and Others: Thanks for all your inputs. I have gone through the process in detail and have been able to reproduce the plugins related problem in T6. The steps are outlined below:
- Drag and drop a plugin (say PianoX) next to a midi track.
- Save and exit Tracktion
- Move PianoX.dll to a new location outside the parent VST plugins folder.
- Open Tracktion
- PianoX appears as a blank plugin (without a name or a warning sign) next to the midi track.
When I click on the plugin, no error message (such as: "ERROR! - This plugin couldn't be loaded!) is displayed in the Properties Section.
- Go to Settings -> Plugins
The plugin PianoX is still displayed in the Plugins List along with all other plugins
- Click on "Scanning and Sorting..." button
- Click on "Scan for new or updated VST plug-ins
- Add the new path for PianoX in the "Select Folders to scan ..." window
- Click on "Scan"
- Go to Track window
PianoX again appears as a blank plugin (without a name or a warning sign) next to the midi track.
- Save and Close Tracktion
- Open Tracktion.
PianoX appears with its name (but with a warning sign) next to the midi track.
The error message "ERROR! - This plugin couldn't be loaded!" is displayed in the Properties Section.
The object of this exercise is to prove that if for any reason a plugin is moved out of its original parent VST plugins folder, the plugin will have to be re-assigned (dragged and dropped) to a track for it to work. If this is the case, then how does one collaborate/share edits with others? Ideally, once a new path is set, and the plugins are re-scanned, the relocated plugin should re-attach to the designated track without one having to manually drag/drop the specific plugin all over again. Imagine a scenario where one has to do this for all plugins if they are moved out to a different folder!
Am I missing something very basic?
- Drag and drop a plugin (say PianoX) next to a midi track.
- Save and exit Tracktion
- Move PianoX.dll to a new location outside the parent VST plugins folder.
- Open Tracktion
- PianoX appears as a blank plugin (without a name or a warning sign) next to the midi track.
When I click on the plugin, no error message (such as: "ERROR! - This plugin couldn't be loaded!) is displayed in the Properties Section.
- Go to Settings -> Plugins
The plugin PianoX is still displayed in the Plugins List along with all other plugins
- Click on "Scanning and Sorting..." button
- Click on "Scan for new or updated VST plug-ins
- Add the new path for PianoX in the "Select Folders to scan ..." window
- Click on "Scan"
- Go to Track window
PianoX again appears as a blank plugin (without a name or a warning sign) next to the midi track.
- Save and Close Tracktion
- Open Tracktion.
PianoX appears with its name (but with a warning sign) next to the midi track.
The error message "ERROR! - This plugin couldn't be loaded!" is displayed in the Properties Section.
The object of this exercise is to prove that if for any reason a plugin is moved out of its original parent VST plugins folder, the plugin will have to be re-assigned (dragged and dropped) to a track for it to work. If this is the case, then how does one collaborate/share edits with others? Ideally, once a new path is set, and the plugins are re-scanned, the relocated plugin should re-attach to the designated track without one having to manually drag/drop the specific plugin all over again. Imagine a scenario where one has to do this for all plugins if they are moved out to a different folder!
Am I missing something very basic?