-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ladspa plugin path will not accept 2 paths #1170
Comments
In May we added As far as the -Tres |
Thanks for the reply Tres. I feel a bit stupid now, I changed it to just ~/.ladspa and it does seem to be picking up the other folder as well automatically. Neither comma or colon seem to work if I do manually include both folders though. Colon just results in the /usr/lib64/ladspa folder being shown and comma isn't remembered after restarting, it changes to "/usr/local/bin/../lib//ladspa/" for some reason. It was the wiki that I was referring to - http://lmms.sourceforge.net/wiki/index.php/1.0:LMMS_Settings#Paths. Anyway, thanks for the help and the clarification, there does seem to be something odd with this but it is working for me now. |
@Sti2nd, can you fix the documentation?
Error in documentation:
I tested this for I'm marking this as invalid but please don't "feel stupid" as the interface offers no hints as to this functionality and our documentation is wrong, so it is very good you brought this to our attention, thank you! -Tres |
I'm not @Sti2nd, but I fixed the typo 😉 |
Thanks! 👻 |
I am unable to use the two ladspa paths I have on my system. If I set it to either one then I can use the plugins from that folder but if I put both folders it only sees one particular folder.
The manual states:
"If you have multiple locations, separate them with colons in the standard UNIX path manner."
This is what I have in the ladspa plugin path option: /home/alex/.ladspa:/usr/lib64/ladspa (this is also the output of echoing ladspa path).
However, only the plugins from /usr/lib64/ladspa will show up with this setting. I hope I am just doing something wrong or missing something here.
I am using the 1.0.93rc.
The text was updated successfully, but these errors were encountered: