Package Details: calf-ladspa 0.90.1.0-1

Git Clone URL: https://aur.archlinux.org/calf-ladspa.git (read-only, click to copy)
Package Base: calf-ladspa
Description: JACK audio plug-ins for musicians (LADSPA version)
Upstream URL: https://github.com/LMMS/veal
Licenses: LGPL2.1
Groups: ladspa-plugins, pro-audio
Conflicts: lmms
Submitter: Teteros
Maintainer: Teteros
Last Packager: Teteros
Votes: 1
Popularity: 0.000013
First Submitted: 2017-04-03 07:56
Last Updated: 2020-04-21 23:55

Latest Comments

Teteros commented on 2020-04-21 22:18

@Carotino You're correct, except I believe it's the other way around. The legacy non-veal Calf LADSPA chorus plugin is MultiChorus without spaces while the updated veal fork (at least the one from master branch this PKGBUILD is building from) is with.

It's strange you needed to do this as I was sure I patched .rad files bundled with radium to fix this for you https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=radium#n71

What might be happening is that the specific version of calf-ladspa bundled in LMMS doesn't use spaces while this calf-ladspa package does?

You could comment out the sed line in the radium PKGBUILD or manually edit the new song template in /opt to fix it. (or just load your own template project somewhere instead of creating a new song, which has the fixed plugin name)

The issue upstream with more details is here https://github.com/kmatheussen/radium/issues/1158#issuecomment-433523503

I'll double check this in the radium PKGBUILD for you whenever the next radium release (6.0? 5.10? 5.9.100?) comes out :)

Carotino commented on 2020-04-20 13:59

Hi. In my case I'm trying to allow Radium to find the calf plugins. I tried both what you suggested but it complains the same, even if I can add it manually later. It looks to me that Radium is looking for Multi Chorus while the plugin adverts itself as MultiChorus (without spaces) - but I may be wrong. In the end it works, so I'd tell you can leave it like it is now.

Thanks

Teteros commented on 2020-04-19 01:01

@Carotino Good question, yes it is. I have this package conflict with LMMS simply because LMMS already has calf-ladspa bundled in, meaning if you install this with LMMS package installed, you will have a duplicate entry for each calf plugin in LMMS.

If you want to use calf-ladspa with other plugin hosts alongside LMMS (like carla), you can add path /usr/lib/lmms/ladspa in the host or as environment variable export LADSPA_PATH=/usr/lib/lmms/ladspa:$LADSPA_PATH to get them.

Alternatively you can symlink calf.so somewhere in your LADSPA search path like the home: ln -s /usr/lib/lmms/ladspa/calf.so $HOME/.ladspa

Seeing how LMMS doesn't crash or have any other adverse effects other than the duplicate calf plugins, I could remove the conflicts() if you'd like?

Though IMO with above options it's not really needed.

Carotino commented on 2020-04-17 20:42

Hi. This package conflicts with LMMS: is it intended? Can it be avoided? Thanks

Teteros commented on 2019-02-06 17:01

Sorry for updating this so late.

I've turned off integrity checks since this is pulling the CMakeLists from LMMS master and veal LADSPA version seems pinned to 'ladspa' branch for a while now.

I wouldn't expect any packaging changes.

johan_schuijt commented on 2019-01-26 20:25

I was not able to build the package, seems they've changed the CMakeLists.txt file a month ago.

==> Validating source files with sha256sums... ladspa.zip ... Passed CMakeLists.txt ... FAILED config.h.in ... Passed ==> ERROR: One or more files did not pass the validity check!

Teteros commented on 2018-10-06 18:01

EDIT: I've switched to LMMS project's fork of calf which has bugfixes and no longer conflicts with calf from community.

NOTE: This will likely break projects depending on LADSPA calf.so

prior to 0.90 version of this package as it has been renamed to veal.so