View previous topic :: View next topic |
Author |
Message |
gkmac Guru
Joined: 19 Jan 2003 Posts: 336 Location: West Sussex, UK
|
Posted: Tue Oct 22, 2024 8:29 pm Post subject: kdenlive: cannot use ladspa plugin |
|
|
In kdenlive it's apparently possible to use LADSPA plugins but I cannot get them working at all, specificly the "noise-suppression-for-voice" plugin.
There are guides for getting it working on other distros such as this one which mention compiling it from source and copying librnnoise_ladspa.so into /usr/lib/ladspa; that's precisely what the Gentoo ebuild does (in Gentoo's case it goes into /usr/lib64/ladspa). The guides simply say "restart kdenlive afterwards and you'll find it by searching in the Effects list" but it never appears for me.
The effect is visible in Audacity so the plugin is definitely there, but starting kdenlive from the command line reveals a few lines of plugin not available: "ladspa"
I've tried re-emerging kdenlive and I've even tried installing ladspa-sdk then re-emerging kdenlive afterwards, but it still persists with those plugin not available: "ladspa" warnings and searching for "noise" in the effects list still shows no sign of "Noise Suppressor for Voice".
Any ideas? _________________ If ~amd64 ebuilds are cutting edge, then git-9999 ebuilds are chainsaws.
"Not everyone can ride a unicycle, does that mean we should put another wheel on it?" - Lokheed |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3477
|
Posted: Tue Oct 22, 2024 8:53 pm Post subject: |
|
|
This looks like the same problem I had with easyeffects. And this is how I solved it:
Code: | lrwxrwxrwx 1 root root 17 2024-03-28 /usr/lib/ladspa -> /usr/lib64/ladspa
lrwxrwxrwx 1 root root 15 2024-03-28 /usr/lib/lv2 -> /usr/lib64/lv2 |
I consider it a workaround rather than a proper solution, but it works, so whatever _________________ Make Computing Fun Again |
|
Back to top |
|
|
gkmac Guru
Joined: 19 Jan 2003 Posts: 336 Location: West Sussex, UK
|
Posted: Tue Oct 22, 2024 9:03 pm Post subject: |
|
|
Good thinking about those symlinks. Unfortunately it doesn't work, still getting plugin not available: "ladspa" and still no sign of the plugin appearing in kdenlive. _________________ If ~amd64 ebuilds are cutting edge, then git-9999 ebuilds are chainsaws.
"Not everyone can ride a unicycle, does that mean we should put another wheel on it?" - Lokheed |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3477
|
Posted: Tue Oct 22, 2024 9:39 pm Post subject: |
|
|
Well, if it's not the location, then maybe some dependency needs an interface?
Have you enabled ladspa USE flag? Kdenlive doesn't like my configuration, so I can't just --pretend install it do see the all dependencies, but I remember it being opt-in for my toys. Same thing applies to lv2. _________________ Make Computing Fun Again |
|
Back to top |
|
|
gkmac Guru
Joined: 19 Jan 2003 Posts: 336 Location: West Sussex, UK
|
Posted: Tue Oct 22, 2024 9:56 pm Post subject: |
|
|
szatox wrote: | Have you enabled ladspa USE flag? ... Same thing applies to lv2. | The kdenlive ebuild itself does not have either of those USE flags.
I've enabled both those USE flags, re-emerged everything that used those USE flags and re-emerged kdenlive yet again afterwards. Still no change. _________________ If ~amd64 ebuilds are cutting edge, then git-9999 ebuilds are chainsaws.
"Not everyone can ride a unicycle, does that mean we should put another wheel on it?" - Lokheed |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3477
|
Posted: Tue Oct 22, 2024 11:48 pm Post subject: |
|
|
Damn, that's not good. I'm outside of familiar territory now and it's pretty hard to come up with new ideas without having the problem right in front of me.
Quote: | starting kdenlive from the command line reveals a few lines of plugin not available: "ladspa" |
Kinda grasping at straws here, but a bunch of things depend on media-libs/ladspa-sdk. Could it be a missing dependency?
Does kdenlive have a verbose or debug switch enabling more detailed messages?
In the end, there's always the option of running kdenlive under strace. It does print e.g. calls to open a file, which may tell you what exactly it can't find, as well as a bunch of other things we wouldn't guess to ask about, but might still recognize as a problem when we see it. _________________ Make Computing Fun Again |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22876
|
Posted: Tue Oct 22, 2024 11:52 pm Post subject: |
|
|
If you go the strace route, I suggest starting with strace --decode-fds -e trace=file -f -tt -o /tmp/kdenlive.strace kdenlive --arg1 --arg2. By restricting it to file related operations, we can cut down on noise, and hopefully not cut out the critical piece. You could omit -e trace=file to get a much more verbose trace. |
|
Back to top |
|
|
pingtoo Veteran
Joined: 10 Sep 2021 Posts: 1341 Location: Richmond Hill, Canada
|
Posted: Wed Oct 23, 2024 12:22 am Post subject: |
|
|
gkmac.
I did a quick search in KDE/kdenlive source code for word "ladspa".
Does Code: | ladspa_declipper.xml
ladspa_equalizer.xml
ladspa_equalizer_15.xml
ladspa_librnnoise.xml
ladspa_limiter.xml
ladspa_phaser.xml
ladspa_pitch.xml
ladspa_pitch_scale.xml
ladspa_rate_scale.xml
ladspa_reverb.xml
ladspa_room_reverb.xml
ladspa_vinyl.xml | Ring any bell?
Do you know where is ${KDE_INSTALL_DATADIR}${DATA_INSTALL_PREFIX}/effects)?
Can you find for example am_pitchshift_1433.so on your file system?
I can dig deeper but just want to understand current state on your setting for now. Will try tomorrow. |
|
Back to top |
|
|
|