Main menu
You are here
Plugins not showing up and grayed out Plugins
30 April, 2014 - 15:44 — temrix
I have built Qtractor with VST support.
Now I have set the path for VST plugins to "/usr/lib/vst" and LV2 Presets Directory to "/usr/lib/lv2". It doesn't display whether the VST nor the LV2 plugins even after a restart of the program.
It does recognize my LADSPA plugins but these are all grayed out.
What can I do to make the plugins show up and add LADSPA plugins?
Forums:
re. Plugins not showing up and grayed out Plugins
you don't have to set those plugins directories explicitlly, because in fact they are already the default.
besides, the lv2 preset directory should one you have enough write privileges as a regular user (default is ~/.lv2, so you rather leave it blank)
otoh. which LADSPA plugins are yours? plugin entries are grayed when whatever their input/output ports layout can't match the track or bus where they are about to be inserted.
please provide a screenshot of the plugin selection list and the about box for some further evidence.
hth.
cheers
Aah, I haven't set the track
Aah, I haven't set the track to MIDI so they were grayed out.
Okay now I haven't set the directories and the lv2 plugins are both in "/usr/lib/lv2" and in "~/.lv2" and they still don't appear. These are the default plugins that came with the install.
What is the default VST-directory? Is it "~/.vst" or "/usr/lib/vst" or anything other?
Screenshot:
I was blocked because of reffering to an image from an image uploader. What should I do?
I guess the plugin selection screen reffered to the grayed out LADSPA plugins. If not, don't hesitate to ask me again for a screen.
Re. Plugins not showing up and grayed out Plugins
the lv2 plugins are both in "/usr/lib/lv2" and in "~/.lv2" and they still don't appear. These are the default plugins that came with the install.
they should appear as soon you select "LV2" plugin type on the plugin selection dialog; also make sure the search phrase is empty (click on the [X] on the left).
also, from a command line console terminal, enter `
lv2ls` and see if anything gets actually listed.as last resort, try to rebuild the whole thing now with debug print outs (
./configure --enable-debug) and watch for standard output console printouts (better run in from a console terminal for that matter).hth.
cheers
I've entered lv2ls in the
I've entered lv2ls in the terminal and nothing comes.
Hmm when configuring it prints out:
OSC service support (liblo) . . . . . . . . . . .: no (I'm aware of that as I don't need it yet)
but maybe it it this:
Non Session Management (NSM) support . . . . . . .: no
X11 Unique/Single instance . . . . . . . . . . . .: no
VeSTige header support . . . . . . . . . . . . . .: no
Let me know when that is not the problem meanwhile I build it again with debug options.
re. I've entered lv2ls in the terminal
I've entered lv2ls in the terminal and nothing comes.
if lv2ls can't find any plugins then you haven't any installed perhaps. or at least not under the regular default search path (which should be something like "
~/.lv2:/usr/local/lib/lv2:/usr/lib/lv2" ...)and what about when you run a debug enabled build, what is spitted out when you try to list lv2 plugins from the selection dialog? (nb. output appears in stdout, on terminal console).
seeya
I was missing the "lv2ls"
I was missing the "lv2ls"-library. When I now enter it still nothing comes. (But at least no message I should install it :P) I have copied the lv2's to all three paths.
Sorry, where is qtractor installed? I can't find it under /opt and other places. I want to remove it so I can run the debug build.
re. where is qtractor installed?
you can run the debug build right after the `
make` step as `src/qtractor`, no need to `make install`.hth.
cheers
Hmm, there appears no
Hmm, there appears no terminal on shutdown. What do I have to do to make a debug build? I have only typed in "./configure --enable-debug" and then "make".
re. no terminal on shutdown
can you more specific what doesn't appear in your case?
if your checking out from svn trunk the steps the build and run are:
then you can run it immediately with
if instead you're makeing it from a release or snapshot tarball then you can skip the first step above.
hth.
cheers
Okay now I know what you
Okay now I know what you mean.
Here is the output:
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "" under id 3
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "" under id 4
qtractorPluginPath[0x7fff97ac04b0]::open() paths="/home/temrix/.lv2:/usr/local/lib64/lv2:/usr/lib64/lv2:/usr/local/lib/lv2:/usr/lib/lv2" typeHint=4
qtractorLv2PluginType::lv2_open()
qtractorMainForm::updateSessionPre()
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
qtractorMainForm::updateSessionPost()
qtractorMainForm::viewRefresh()
qtractorMidiControl::sendAllControllers(0)
qtractorMainForm::trackAdd()
qtractorPluginPath[0x993a20]::open() paths="/home/temrix/.lv2:/usr/local/lib64/lv2:/usr/lib64/lv2:/usr/local/lib/lv2:/usr/lib/lv2" typeHint=4
qtractorPluginPath[0x993a20]::open() paths="/home/temrix/.vst:/usr/local/lib64/vst:/usr/lib64/vst:/usr/local/lib/vst:/usr/lib/vst" typeHint=3
qtractorPluginPath[0x993a20]::open() paths="/home/temrix/.lv2:/usr/local/lib64/lv2:/usr/lib64/lv2:/usr/local/lib/lv2:/usr/lib/lv2" typeHint=4
qtractorLv2PluginType::lv2_close()
"Datei oder Verzeichnis nicht gefunden" means "File or folder not found"
re. from the above debugging printout
from the above debugging printout output, one can see that the actual search paths for plugins are
/home/temrix/.lv2:/usr/local/lib64/lv2:/usr/lib64/lv2:/usr/local/lib/lv2:/usr/lib/lv2"VST path="
/home/temrix/.vst:/usr/local/lib64/vst:/usr/lib64/vst:/usr/local/lib/vst:/usr/lib/vst"but none is being found anywhere there as each plugin filepath (.so) would be then listed thereafter.
search your filesystem on each of the above directories; i suspect that either the /lib or /lib64 might be duplicated and source for confusion if one is a symlink to the other; otherwise something is wrong with either your plugins installation or your distro filesystems layout and i kind of running out of options... :(
cheers
Finally I got it. The plugins
Finally I got it. The plugins must not be in sub-folders.
Thanks for your time!
Now that I have installed
Now that I have installed WhySynth it finds it but I installed dssi-vst too and it doesn't. However the file in /usr/lib/dssi/dssi-vst.so does exist.
EDIT: It finds it when I click on 'Any'.
re. installed dssi-vst too and it doesn't
dssi-vst is a VST plugin bridge or proxy or whatever it's better called--its purpose is not to show up as a plugin by itself but to present windows VSTs as plain DSSI plugins
nb. the search/scan path for locating those windows netive plugins (.dll) is given by the VST_PATH environment variable. iow. it is NOT tweakable on qtractor options whatsoever.
cheers
Audacity plugins
Audacity sucks now. LADSPA plugins DO NOT show up in Windows 10. Nobody seems to care. Nobody is trying to fix it.
Add new comment