I had a VST plugin I REALLY find useful that stopped working as of my session with Ardour today. I did not update this plugin. I did recompile Ardour a couple of times, the same way I did when this plugin was working.
This is fairly normal when using Windows VSTs on an operating system that was never intended to run them. Its quite remarkable that it works at all, ever, and is a tribute to the superb work done by the WINE devs. However it should be considered an absolute last resort, since if you change anything (anything at all e.g. sometimes even if the wind direction changes or the phase of the moon etc), it may stop working. You should certainly not rely on it for any critical work. That said, one of the most common causes of problems is a new version of WINE re-arranging the bugs a little.
I’m not sure if you’ll find an LV2 or LADSPA plugin that can do what you want (especially LADSPA since LADSPA has no GUI) but there are some excellent jack applications for all kinds of audio analysis here
I’m thinking that the jaaa - jack / alsa audio analyser might do what you need. You can patch jack applications into ardour either directly onto the master outputs or by setting up an insert point in a channel.
@audiodef - if you use a windows VST plugin on linux, you will be using WINE at some point - AFAIK there is no other way to get a binary compiled for windows to run on linux, which is essentially what you are doing when you load up a windows VST either into ardour or into an external jack based VST host.
What other plugins (made for linux) are you trying to use which don’t show up?
@audiodef: That’s very strange - I have the same version running here with both those plugins and they both show up. I think the one listed under ‘Limiter’ is an LV2 and the one listed under ‘Limiters’ is the LADSPA version which would suggest that there is something not right with LV2 support in your build (I’m getting this from looking through the .ttl files for the lv2 stuff and its late so I might have read it wrong…)
One way to tell for certain if you really have LV2 support compiled in is to run ldd on the ardour binary, so for example, if you compiled and installed ardour with a prefix /usr then you might do
at the command line, and see if the output shows a reference to libslv2 anywhere - this would indicate that you do have LV2 support in your build. If not then you don’t.
if you used the default prefix of /usr/local then you might need: