if you change the name a parent folder vst; or the main route
example: GVST to GVST-plugins;
/user/lib/vst to /home/user(name)/plugins/vst
It affects all projects. GVST-plugin not recognized.
and asks me to ignore or save again
that's correct; original paths to plugin excutables must not change over the time (LADSPA, DSSI and VST); note that plugins executable absolute file paths are saved/stored onto the session file (.qtr).
only LV2 plugins won't suffer from this restriction as they are uniquely identified by URI (and not an canonical file-system path);
if you do move or rename files around your file-system, any files that are still possibly referenced in a .qtr session for instance, and especially plugin executable paths (LADSPA, DSSI or VST), then you shall edit and update by hand all the absolute path and file-names that have been moved or renamed around.
as you may already know this strict plugin path restriction, that again only applies to LADSPA, DSSI and VST plugins, prevails even though a session is saved in archive/zip format (one single file bundle with .qtz suffix).
re Vst new route: not detected
may you rephrase your question?
i guess you're not a master in english, nor am i, so please, can you breath calmly and take it easier for both of us? :)
cheers
re Vst new route: not detected
if you change the name a parent folder vst; or the main route
example: GVST to GVST-plugins;
/user/lib/vst to /home/user(name)/plugins/vst
It affects all projects. GVST-plugin not recognized.
and asks me to ignore or save again
re Vst new route: not detected
that's correct; original paths to plugin excutables must not change over the time (LADSPA, DSSI and VST); note that plugins executable absolute file paths are saved/stored onto the session file (.qtr).
only LV2 plugins won't suffer from this restriction as they are uniquely identified by URI (and not an canonical file-system path);
if you do move or rename files around your file-system, any files that are still possibly referenced in a .qtr session for instance, and especially plugin executable paths (LADSPA, DSSI or VST), then you shall edit and update by hand all the absolute path and file-names that have been moved or renamed around.
as you may already know this strict plugin path restriction, that again only applies to LADSPA, DSSI and VST plugins, prevails even though a session is saved in archive/zip format (one single file bundle with .qtz suffix).
cheers
re Vst new route: not detected
with commercial plugins also happen?
overtonedsp, DiscoDSP, loomer, u-he ...
re Vst new route: not detected
with commercial plugins also happen?
with ANY plugin type but LV2.
cheers
Add new comment