Thanks Chris. I think you are right. Audacity seems to be looking in the wrong place for the ladspa plugin. A Debian bug reporter has found that it is looking in /usr/lib/x86_64-linux-gnu/ladspa instead of /usr/lib/ladspa. Regards, Ross
** Bug watch added: Debian Bug tracker #724836 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724836 ** Also affects: audacity via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724836 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Studio, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1261654 Title: missing LADSPA support Status in Audacity: Unknown Status in “audacity” package in Ubuntu: Confirmed Bug description: The version of audacity in trusty seems to be missing LADSPA support: under Effects, I see only 29 plugins listed. Downgrading to version 2.0.3-1 (from raring/saucy), I see the expected list of 277 plugins. Comparing the configure for raring/saucy and trusty the only difference I can see is the following, but raring/saucy: --with-ffmpeg=system trusty: --without-ffmpeg I'd be surprised if that is relevant and added to which, the build log shows that ladspa is enabled (?!?) To manage notifications about this bug go to: https://bugs.launchpad.net/audacity/+bug/1261654/+subscriptions -- Mailing list: https://launchpad.net/~linux-traipu Post to : [email protected] Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
