Ok, I got it fixed by installing a new JACK version (1.9.9.5) Now Ardour starts. Calf plugins load. Thank you
calf 0.0.19 is seriously out of date and error prone, do yourself a favor and grab 0.0.60 at least.
Hi, I am running 4.6.0 on Ubuntu 14.04 and I cant get it to load/see the Calf 0.0.60 plugins. When I scan in Ardour Preferences/plugins nothing happens. I’ve tried reinstalling both the Calf and Ardour, no luck.
I run an identical setup on my laptop which works perfectly. The only difference I can see is that in my not-working system many of the Calf files are in /usr/lib/x86_64-linux-gnu/lv2 whereas on my laptop they are in usr/lib/lv2.
Is that a problem ? Any help appreciated !!
Where did you get Ardour 4.6 from?
From this site - everything as instructed, donation made etc
You may need to specify the appropriate environment variable, in your case LV2_PATH IIRC and put that directory in it.
Seablade
Ardour (as built for ardour.org) looks in the following places for LV2 plugins:
~/.lv2:/usr/local/lib/lv2:/usr/local/lib64/lv2:/usr/lib/lv2:/usr/lib64/lv2
If you somehow install plugins somewhere else, then as Seablade noted, you need to set LV2_PATH in your environment before starting Ardour so that it can find them. Did you install them “by hand” on the non-working system?
Many thanks both for your speedy replies. I installed the Calf Plugins via the ubuntu Software Centre, as recommended at http://calf-studio-gear.org
Could you advise me what terminal commands to use to set the LV2_PATH to /usr/lib/x86_64-linux-gnu/lv2 ?
Thanks again
export LV2_PATH=/usr/lib/x86_64-linux-gnu/lv2:$LV2_PATH
To make it permanent add
LV2_PATH=/usr/lib/x86_64-linux-gnu/lv2:$LV2_PATH
export LV2_PATH
to .bash_profile in your home directory.
Thanks for your post, but unfortunately no joy with this command, still no plug-ins appearing if I scan in prefs.
I note that there is actually one plug-in that can be seen in Ardour on the non-working system: reasonablesynth. (No idea where it came from). On searching the file system I found this in:
/opt/Ardour-4.6.0/lib/LV2/reasonablesynth.lv2
Is this where Ardour is looking for LV2 plug-ins, and where Calf should be?
RattusB should perhaps have pointed out, since you may not have known it, that changing the path isn’t going to have any effect on a running program, nor on any shell other than the one in which you do it. Did you try launching Ardour from the console in which you typed the “export LV2_PATH=/usr/lib/x86_64-linux-gnu/lv2:$LV2_PATH”; or alternatively, did you log out of you r X session and log in again before launching if you did the edit .bashrc (preferable) approach?
Great! Worked immediately! (Obviously I should have thought of that!).
Could you clarify how to make it permanent? I don’t seem to have a file called .bash_profile?
It will be in your home directory if it exists, and if it doesn’t, just create one with your favourite text editor and put that line in it.
Thanks. I tried this and restarted, but it didn’t work. I’m new to scripting, is there other information needed in .bash_profile beyond:
LV2_PATH=/usr/lib/x86_64-linux-gnu/lv2:$LV2_PATH
export LV2_PATH
bearing in mind it’s a blank text file that I created
1 Like
Any thoughts on this anyone? Its working fine from the terminal but would be nice to make it permanent.
Did you login out and back in after creating that file? For your purposes, it is only read at login time.
Thanks Paul, yes I have logged out, several times to double check - no joy.
https://help.ubuntu.com/community/EnvironmentVariables#Persistent_environment_variables
More info than you ever wanted to know on environment variables. Not completely sure if up to date, but give it a shot, I would suggest adding the export LV2_PATH=.... line to your ~/.profile file and see if that works for you. Some graphical environments don’t always process .bash_profile as they don’t always launch a bash shell, so hopefully this will get it in your graphical environment as well. Haven’t had a need to test it, but give it a shot and see what happens.
Seablade
1 Like
Many thanks, will give it ago
Yup , I put the lines into ~/.profile and it worked at first attempt!
Think I’m sorted now, many thanks to all posters on this thread for your time and help 