Ignored VST plugin which is newer than cache (FIXED)

Installation & Configuration Linux
#1

My Ardour log (Ardour 6.0.0, AVLinux 2020.5.10) shows many messages like this:

2020-06-15T22:17:18 [INFO]: Re-Scan Plugins (Preferences > Plugins) to update the cache, also make sure your system-time is set correctly.
2020-06-15T22:17:18 [WARNING]: Ignored VST plugin which is newer than cache: ‘/usr/lib/vst/AF210.so’ (cache: ‘/home/diehl/.cache/ardour6/vst/8964b0bbfb57af4e9809985322bbc60ea0ca4e31.fsi64’)

I rescanned the plugins but still get this error. Checking the files mentioned in the complaint I don’t see a problem:

$ dir /usr/lib/vst/AF210.so
-rw-r–r-- 1 root root 1332592 May 28 12:56 /usr/lib/vst/AF210.so
$ dir /home/diehl/.cache/ardour6/vst/8964b0bbfb57af4e9809985322bbc60ea0ca4e31.fsi64
-rw-r–r-- 1 diehl diehl 1143 Jun 15 22:17 /home/diehl/.cache/ardour6/vst/8964b0bbfb57af4e9809985322bbc60ea0ca4e31.fsi64

Plugin appears to be older than cache.

Also, I am able to use the AF210 plugin normally, so it does not seem that the VST is actually ignored.

Are these messages some kind of bug or is there a configuration problem?

#2

After restarting Ardour, these messages have gone away. So I guess the re-scan actually did fix the problem, but only after a restart of Ardour.

#3

I guess it’s too late now.

stat ~/.cache/ardour6/vst/8964b0bbfb57af4e9809985322bbc60ea0ca4e31.fsi64
stat /usr/lib/vst/AF210.so

Ardour compares at “Modify” timestamp (mtime).

#4

i have this error can u help me

2020-06-15T23:17:07 [WARNING]: LADSPA: module “/usr/lib/ladspa/ambisonic2.so” has no descriptor function.
2020-06-15T23:17:07 [WARNING]: ‘ladspa_descriptor’: /usr/lib/ladspa/ambisonic2.so: undefined symbol: ladspa_descriptor
2020-06-15T23:17:08 [WARNING]: LADSPA: module “/usr/lib/ladspa/ambisonic1.so” has no descriptor function.
2020-06-15T23:17:08 [WARNING]: ‘ladspa_descriptor’: /usr/lib/ladspa/ambisonic1.so: undefined symbol: ladspa_descriptor
2020-06-15T23:17:08 [WARNING]: LADSPA: module “/usr/lib/ladspa/ambisonic3.so” has no descriptor function.
2020-06-15T23:17:08 [WARNING]: ‘ladspa_descriptor’: /usr/lib/ladspa/ambisonic3.so: undefined symbol: ladspa_descriptor
2020-06-15T23:17:08 [WARNING]: LADSPA: module “/usr/lib/ladspa/ambisonic0.so” has no descriptor function.
2020-06-15T23:17:08 [WARNING]: ‘ladspa_descriptor’: /usr/lib/ladspa/ambisonic0.so: undefined symbol: ladspa_descriptor
2020-06-15T23:17:27 [WARNING]: Unsupported required LV2 feature: ‘http://lv2plug.in/ns/ext/buf-size#fixedBlockLength’ in ‘KlangFalter’.
2020-06-15T23:17:27 [WARNING]: Unsupported required LV2 feature: ‘http://lv2plug.in/ns/ext/buf-size#fixedBlockLength’ in ‘Vex’.
2020-06-15T23:17:28 [WARNING]: Ignoring duplicate Linux VST plugin Shiroverb
Cannot get VST information for ‘/usr/lib/vst/b_reverb.lv2.so’: failed to load cache file.

#5
  1. the LADSPA errors: these plugins were compiled incorrectly.
  2. the LV2 errors: as it says, the plugins use an LV2 extension not supported by Ardour
  3. the Linux VST duplicate error: self-explanatory
  4. Final error: unknown
#6

A LV2 plugin in a VST folder – and not even /usr/bin/lxvst for Linux VSTs. How did that end up there? Which GNU/Linux distribution are you using?

Also if this is b_reverb.lv2 from setBfree, the author (me) highly recommends to not package it (compilation is even disabled by default).

#7

AVlinux 64 bit and i compile ardour from source

#8

Unless you’re using Ambisonics, uninstall the amb-plugin package (that’ll get rid of the LADSPA warnings), but it might be worth filing a bug report about that issue.

#9

i uninstall amb-plugins & setbfree but again have below error

2020-06-16T06:40:43 [WARNING]: Unsupported required LV2 feature: ‘http://lv2plug.in/ns/ext/buf-size#fixedBlockLength’ in ‘KlangFalter’.
2020-06-16T06:40:43 [WARNING]: Unsupported required LV2 feature: ‘http://lv2plug.in/ns/ext/buf-size#fixedBlockLength’ in ‘Vex’.

#10

As Paul said in his reply above

GMaq, who creates the AVLinux disto, usually hangs around here but since it’s an issue with his plugin packaging and/or your own Ardour compillation you should post the question on his forum
http://bandshed.net/forum_archive/bandshed.net/forum/index.php.html

Edit : I can’t even get my KlangFalter or Vex plugins, from the most recent git, to show up in my self-compiled Ardour 6.0.15; not even if I do a rescan.
My A6 apparently ignores them since they’re not supported, so it’s unclear why you get the errors.

#11

solved by uninstall distrho-plugin-ports-lv2 & klangfalter-lv2

#12

It’s just a Warning (not an error). Those LV2 plugins can work in other hosts just fine.

The tech details:

required LV2 feature: ‘fixedBlockLength’ means that the plugin can only be used if the block-size is constant. In Ardour this is not the case. e.g. when looping or using automation, Ardour can use smaller process-blocks.

e.g play N samples, loop, continue and play (block-size - N) samples.

Some other simple LV2 hosts do not have this constraint and hence can satisfy the plugin’s requirement.

This is usually trade-off. Requiring a fixed block size allows a developer to optimize the math and also shorten development time.

#13

@x42 @peder @killum

To clarify other than a single package containing small collection of plugin binaries that are not packaged in Ubuntu, Debian or KXStudio repositories the majority of AV Linux plugins originate from the KXStudio repositories. I have checked my ‘avlinux-plugins-extra’ package and there are no LV2 plugins in the systemwide /usr/lib/vst VST folder. This problem was probably from a KXStudio updated package I would guess. Are there not versions of SetBFree that use VST wrappers and components of SetBFree that end up in the users VST folder?

As far as the ambisonics plugins error messages that is an upstream packaging problem that has been around for a long time, it’s an annoying error but completely harmless to run Ardour with…

#14

PS. keep in mind that those are just warnings. Perhaps we should downgrade the severity to info.

It is not unusual that some plugins cannot be used equally in all hosts.

#15

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.