hello
i just installed audacity v. 1.3.6 beta. installation went smoothly (as far as i can tell), audacity starts and runs smoothly, but all my previous ladspa plug-ins, which used to be sorted by number at the end of the audacity effects menu in version 1.3.5 beta are now gone.
does anyone know what the problem could be?
thanks in advance for any help.
os: ubuntu 8.0.4
1.3.6 beta install // all ladspa plug-ins gone
Forum rules
Audacity 1.3.x is now obsolete. Please use the current Audacity 2.x.x package for your distribution or compile Audacity from the source code.
Audacity 1.3.x is now obsolete. Please use the current Audacity 2.x.x package for your distribution or compile Audacity from the source code.
Re: 1.3.6 beta install // all ladspa plug-ins gone
Audacity 1.3.6 orders plug-ins in categories, I think they should still be present, but their location will have changed.
I can't give much more insight at the moment as I've only just started looking at 1.3.6 myself.
I can't give much more insight at the moment as I've only just started looking at 1.3.6 myself.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: 1.3.6 beta install // all ladspa plug-ins gone
hi
thanks for replying. the plug-ins are definitely not there--i've looked in all the categories.
i checked in ardour and all plug-ins are still there (the same ones i used to use in audacity 1.3.5 beta).
thanks for replying. the plug-ins are definitely not there--i've looked in all the categories.
i checked in ardour and all plug-ins are still there (the same ones i used to use in audacity 1.3.5 beta).
Re: 1.3.6 beta install // all ladspa plug-ins gone
hello again
ok, i've found a workaround, though i don't know if this is the "official" way of doing this.
i ended up copying the ladspa plug-ins i normally used from the /usr/lib/ladspa folder to the audacity plug-in folder. now i can use these plug-ins in audacity from the effects menu.
the thing is, with all previous audacity update installs i've never had to do this. so, maybe something went wrong with my installation that i don't know about?
can anyone shed some light on this?
thanks.
ok, i've found a workaround, though i don't know if this is the "official" way of doing this.
i ended up copying the ladspa plug-ins i normally used from the /usr/lib/ladspa folder to the audacity plug-in folder. now i can use these plug-ins in audacity from the effects menu.
the thing is, with all previous audacity update installs i've never had to do this. so, maybe something went wrong with my installation that i don't know about?
can anyone shed some light on this?
thanks.
Re: 1.3.6 beta install // all ladspa plug-ins gone
Normally all plug-ins for Audacity should be in the Audacity plug-ins folder.
The fact that it was working previously on your machine with them in a different folder is a little non-standard.
I think it makes sense that plug-ins are required to be in the Audacity plug-ins folder, since some LADSPA and Nyquist plug-ins are not designed for, and do not work with Audacity. Although this may mean some duplication of files, the plus side is that you can use plug-ins that are incompatible with Audacity in other programs, without cluttering Audacities effects list.
The fact that it was working previously on your machine with them in a different folder is a little non-standard.
I think it makes sense that plug-ins are required to be in the Audacity plug-ins folder, since some LADSPA and Nyquist plug-ins are not designed for, and do not work with Audacity. Although this may mean some duplication of files, the plus side is that you can use plug-ins that are incompatible with Audacity in other programs, without cluttering Audacities effects list.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: 1.3.6 beta install // all ladspa plug-ins gone
hi
thanks for your reply.
i agree, it does seem a bit strange that previously i had audacity accessing plug-ins not in its plug-in folder...i'm not sure what has changed, either on my end or on audacity's.
in any case, now that i've figured out, as you mentioned here, that audacity needs all plug-ins in its own folder i will follow this procedure.
makes sense...
thanks for your reply.
i agree, it does seem a bit strange that previously i had audacity accessing plug-ins not in its plug-in folder...i'm not sure what has changed, either on my end or on audacity's.
in any case, now that i've figured out, as you mentioned here, that audacity needs all plug-ins in its own folder i will follow this procedure.
makes sense...