Calf Plugin Suite 0.90.7 on Debian 12 64bit

[Piergi]

Code: Select all

sudo cp -rf whateverplugin.lv2 /usr/lib/lv2

Been doing so for years now without an issue. I fact I did that laste withe a few plugins from linuxdaw.org NO ISSUES at all..

the lv2 folder was there but when I opened it it was the content of what's in any lv2 plugin. In other words no other plugin was there except a plug-in called lv2 which I thought it was the directory.

From your description, it looks like the original directory /usr/lib/lv2 got overwritten with the new one. Since in your command there was no trailing slash in the destination, and you used "force" (-f), could it be that "/usr/lib/lv2" was originally a symlink, and got overwritten (just a wild guess)?
Maybe the other times you tabbed it and bash-completion put the slash at the end? I don't know.

(Relevant info also here: https://stackoverflow.com/questions/181 ... py-folders)

[Axel-Erfurt]

A simple test. As you can see, nothing has been deleted.

Code: Select all

axel@chieftech:/tmp$ mkdir lv2
axel@chieftech:/tmp$ mkdir /tmp/lv2/test.lv2
axel@chieftech:/tmp$ cp -rf lv2-gtk-ui-bridge.lv2 /tmp/lv2
axel@chieftech:/tmp$ ls /tmp/lv2
lv2-gtk-ui-bridge.lv2  test.lv2

[Piergi]

A simple test. As you can see, nothing has been deleted.

I mentioned the possibility that the original directory was a symlink.
Also mentioned that it was a "wild guess".

The description that funkmuscle posted (also quoted in my post above) makes me think that the original directory was (somehow) overwritten by the cp -rf command (with the force option preventing a warning).

EDIT:
I tried it now with a symlink (in a Mac, not sure if there are differences) and the symlink is indeed not overwritten. Thus, I just don't know what happened.

[rncbc]

Another variation: Couldn't someone ask chatGPT (for instance) to assist in rewriting the code to use QT6?

Same problem. There will be QT7 some time.

The best solution is probably a statically linked toolkit that's contained in the source tree. The Ardour project does it this way but has unfortunately made the mistake that their toolkit (modified gtk2) is one of those who don't coexist with other versions of their own.

Qt can be statically linked alright, something that to my knowledge no gtk version can (ever) probably do, unless a boat load of work and bloat goes perfectly aligned (glib, gtk, gdk, pango, etc.)--might be mistaken ofc. im no gtk fan here, ok?

meanwhile enjoy yours truly Vee-One-Suite which are 99.9% self-contained, Qt6-statically linked LV2 plugins made to work on officially supported ardour.org binaries from the cradle

if you wish, you may take them right from horse's mouth: just look into the repos

cheers

nb. once statically linked you won't have to deal with toolkit or framework version (in)compatibilities whatsoever.

[k410]

Another variation: Couldn't someone ask chatGPT (for instance) to assist in rewriting the code to use QT6?

Same problem. There will be QT7 some time.

The best solution is probably a statically linked toolkit that's contained in the source tree. The Ardour project does it this way but has unfortunately made the mistake that their toolkit (modified gtk2) is one of those who don't coexist with other versions of their own.

Qt can be statically linked alright, something that to my knowledge no gtk version can (ever) probably do, unless a boat load of work and bloat goes perfectly aligned (glib, gtk, gdk, pango, etc.)--might be mistaken ofc. im no gtk fan here, ok?

meanwhile enjoy yours truly Vee-One-Suite which are 99.9% self-contained, Qt6-statically linked LV2 plugins made to work on _officially supported_ ardour.org binaries from the cradle

if you wish, you may take them right from horse's mouth: just look into the repos

cheers

nb. once statically linked you won't have to deal with toolkit or framework version (in)compatibilities whatsoever.

"Today you are even more handsome!" (a compliment I learned from the live-action version of The King's Avatar)

Of course when I asked about redoing the Calf plugin suite with QT I had in mind the story about the origins of LXQT, and thought it would be an easy thing to do (for someone who knew what they were doing).