mod-ams.lv2 - duplicate plugin uris

[mxmilkiib]

Using the change_uri branch;

lilv_world_add_plugin(): warning: Duplicate plugin <http://github.com/blablack/ams-lv2/lfo2_freq>
lilv_world_add_plugin(): warning: ... found in file:///usr/lib/lv2/ams.lv2/
lilv_world_add_plugin(): warning: ... and      file:///usr/lib/lv2/mod-ams.lv2/ (ignored)
lilv_world_add_plugin(): warning: Duplicate plugin <http://github.com/blablack/ams-lv2/vcaexp>
lilv_world_add_plugin(): warning: ... found in file:///usr/lib/lv2/ams.lv2/
lilv_world_add_plugin(): warning: ... and      file:///usr/lib/lv2/mod-ams.lv2/ (ignored)
lilv_world_add_plugin(): warning: Duplicate plugin <http://github.com/blablack/ams-lv2/vcalin>
lilv_world_add_plugin(): warning: ... found in file:///usr/lib/lv2/ams.lv2/
lilv_world_add_plugin(): warning: ... and      file:///usr/lib/lv2/mod-ams.lv2/ (ignored)
lilv_world_add_plugin(): warning: Duplicate plugin <http://github.com/blablack/ams-lv2/vcf>
lilv_world_add_plugin(): warning: ... found in file:///usr/lib/lv2/ams.lv2/
lilv_world_add_plugin(): warning: ... and      file:///usr/lib/lv2/mod-ams.lv2/ (ignored)
lilv_world_add_plugin(): warning: Duplicate plugin <http://github.com/blablack/ams-lv2/vco3>
lilv_world_add_plugin(): warning: ... found in file:///usr/lib/lv2/ams.lv2/
lilv_world_add_plugin(): warning: ... and      file:///usr/lib/lv2/mod-ams.lv2/ (ignored)
ALL OK!

[falkTX]

You reported this in the wrong place :)

[mxmilkiib]

There's no issue queue for that project! :)

[BramGiesen]

@mxmilkiib, I've enabled the issues section on the mod-ams repo. Regarding this issue, there are indeed some issues with duplicate URI's between the mod-ams and regular ams package. On our system the regular ams package is patched so it doesn't contain the plugins that are also present in the mod-ams package. I checked changing the URI's for the mod-ams package, but this will cause issues with backwards compatibility within our device.

[falkTX]

Note that there is some conversation surrounding how to deal with LV2 plugins that need to change URIs.
When a solution is officially picked in LV2, we will go for it, but until then we have to live with this.