Linux public beta (4408)

[youki]

Starting ardour from the terminal doesn't change anything. Ok, i'll try the Ardour IRC channel, thanks for your help.

[youki]

Well, on the Ardour IRC channel i learnt that Ardour3 doesn't search for the plugin recursively in $HOME/.vst and also that it is even maybe not a default path for LinuxVST plugins.

Indeed, if i put the LinuxDSP plugin in /home/youki/.vst, Ardour3 doesn't find it EXCEPT if i start Ardour3 from a terminal. Then the plugin shows up as i added the path in the .bashrc file.

I was told also that installing Satin with ./install.sh --vstdir=$HOME/.vst/ should work. And Satin is installed directly in /home/youki/.vst without a u-he subfolder. Unfortunately it still doesn't show up in Ardour3 even if the LinuxDSP plugin does.

[abique]

Can you try with bitwig or renoise and tell me if it shows up?
What distribution are you using?

[syndicat]

Packaging won't be an easy task. There are some hardcoded relative (to user home dir) paths and requirement to be installed in a writable directory for preset management. I think it's better to leave all as is. The installation process is very easy.

...hmm,
this means the plugins are not software nor "libraries" - they are just "user data" (what is not correct). This is by principle against POSIX / SYSV filesystem quasi standards and many linux installations out there rely on. It is'nt a good idea to place binaries / "programm code" into a home directory which is loadable by a program which might i.e. have higher rights (i.e. on systems where homes has no x flag - means: the system should not allow to run code which is manipulatable by the user...).

The correct place for "plugins" (like VSTs and such stuff) would be /usr/lib or something like /usr/local/lib while i.e. user related licenses are placed somewhere under /home (i.e. "~./u-he/)

Shure, many of the commercial audio application stuff seems new to the Linux / *ix world and it's paradigms, but to get ready really linux proof there is no way around package management - beside the fact that many installations are hardly bound to package management for security and quality management (shure, this is completely new to Windosers and widely new to Mac OSers, but by fact one of the major reasons why professional linux users decide for linux - and not the fact does it "costs nothing"...).

Having program code somewhere under /home is (sorry) just ugly...


And not at last: Having demos easily installable over the software management tool of the distribution, links and product names in many (mostly highly ranked) online archives - which is a "side effect" - is a additional way for marketing.

[syndicat]

Just to explain a bit en detail:

"Libraries" (or binaries / code acting like a "library" in SYSV/POSIX semantics) - means the "plugin" builds byself has to go to:

/usr/local/lib/vst

License information has to be placed in a file or files:

-> if the license is user based - in home:

~./.u-he/ (or similiar)

-> or if it's "site wide" (means all users on that machine can use the license):

/var/lib/[u-he/] (or similiar)

While User presets are placed under home in:

~./[.u-he[/ (or similiar)

while "factory presets" come into:

/usr/share/[u-he] (or similiar)
or (more independent)
/usr/local/share/[u-he] (or similiar)

I'm not shure how far the VST SDK is able to handle relative pathes - as far as i can see from other VST compilates, it seems at least possible to work with this standard directories so far.

Under Mac OS plugins are not installed in the Users Home directory too - for (if even a bit less) good reasons.

if pathes really are a barrier for a developer, the last option is the /opt/[u-he]/[product] directory where all non user dependent details could be placed - but this is not fully standardized too.

Your "install.sh" is coded good so far and fit's the need of users not have any package in their distribution and look for a workaround - but nearly every linux user or admin would hardly prefer installation over the regarding package management of his system if there is any available.


hth a bit
cheerioh,


Niels.

[youki]

Can you try with bitwig or renoise and tell me if it shows up?
What distribution are you using?

I'm using Debian Wheezy with TangoStudio repos added.
Bitwig didn't install due to a problem of dependencies.
Renoise didn't show any LXVST.
I tried also QTractor, then the LinuxDSP plugin shows up but not Satin.

[abique]

Youki, I think that you have some dependencies issue.
You need glibc >=2.15 and gtk-3 to run the plugins.

[abique]

Syndicat, thank you for your zeal. We evaluated the idea of doing packages instead of installers in august and we chose the actual solution.
Thanks for you comprehension.

[youki]

Ok, it's what i was starting to guess. I'll have to upgrade my system in the future to use the linux version but for now i'll stick on stability and unfortunately i'll continue to use the win version with Reaper and WINE. Thanks again.

[cajmere]

Well, on the Ardour IRC channel i learnt that Ardour3 doesn't search for the plugin recursively in $HOME/.vst and also that it is even maybe not a default path for LinuxVST plugins.

Indeed, if i put the LinuxDSP plugin in /home/youki/.vst, Ardour3 doesn't find it EXCEPT if i start Ardour3 from a terminal. Then the plugin shows up as i added the path in the .bashrc file.

I was told also that installing Satin with ./install.sh --vstdir=$HOME/.vst/ should work. And Satin is installed directly in /home/youki/.vst without a u-he subfolder. Unfortunately it still doesn't show up in Ardour3 even if the LinuxDSP plugin does.

That's right. It searches not recursively. I wrote a bug report about it and putted it in the mantis bugtracker of ardour.
( http://tracker.ardour.org/view.php?id=6030)
Satin works fine in my ardour3 version, compiled from git.
Ardour 3.5.3558 (built from revision 3.5-3558-g4a17f9e)
But i had to add the plugins directories to ardour preferences(only git in git possible).

[psycha0s]

syndicat I know FHS rules and I agree with you. But I'm sure that developers have weighty reasons, why they decided not to follow FHS.

[uriukti]

In Ardour3 is a special folder for vst / usr / local / lib / lxvst. After install.sh I add one file vst to this folder manually. This file has an extension - .so After that Ardour appears plugin. Maybe it's not right, but it works.

[samplemania]

You can use the following script to batch install all of them at once:

Code: Select all

#! /bin/bash
function install_uhe()
(
  product="$1"
  rev="$2"
  cd /tmp &&
  wget http://uhedownloads.heckmannaudiogmb.netdna-cdn.com/penguin/release/$rev/$product-$rev.tar.gz -O $product-$rev.tar.gz &&
  tar xf $product-$rev.tar.gz &&
  cd $product-$rev &&
  ./install.sh --quiet &&
  cd /tmp &&
  rm -rf $product-$rev $product-$rev.tar.gz
)

for product in ACE Bazille Diva Podolski Presswerk Satin Uhbik Zebra2
do
  install_uhe $product 3193
done

I used this script (Ubuntu / Bitwig) and it seems to work - but where does it install the plugins??
I have to choose a VST path in Bitwig and don't know where to go...

[abique]

The plugins are installed in ~/.u-he
Also the VST are installed to ~/.vst/u-he

[samplemania]

The plugins are installed in ~/.u-he
Also the VST are installed to ~/.vst/u-he

Again...

Where? What is the full path?
While I installed Linux/Ubuntu several times I am not familiar with the OS folder structure as some others here.