Description of problem: When installing plugins in Fedora, they go to /usr/lib64/vst and /usr/lib64/vst3 ... (same for other formats) But by default Ardour is not configured to look into these directories. User might think that the plugins does not work, until he/she manually add the directories to Ardour configuration. How reproducible: Always Actual results: Plugins are not available by default, requiring explicit configuration change Expected results: Plugins should be available without requiring manual configuration. Ardour hardcoded it here https://github.com/Ardour/ardour/blob/fad71ce748fd244611ffad397fd0c51ecbe72334/libs/ardour/plugin_manager.cc#L2055 RPM Spec could include a path to add /usr/lib64/vst3 to the hardcoded list. Or the RPM Spec could set the VST3_PATH environment variable https://github.com/Ardour/ardour/blob/fad71ce748fd244611ffad397fd0c51ecbe72334/libs/ardour/plugin_manager.cc#L318 It could be done globally by adding a file to /etc/profile.d or patching the script https://github.com/Ardour/ardour/blob/master/gtk2_ardour/ardour.sh.in A similar issue has been fixed in Carla https://bugzilla.redhat.com/show_bug.cgi?id=1971859
Ardour rationale is to comply with VST3 specification: https://developer.steinberg.help/display/VST/Plug-in+Locations/ They expect plugins to be in /usr/lib/vst3/. Maybe the package could create a link from /usr/lib/vst3/ to /usr/lib64/vst3 to solve this issue?
I cannot delete or even edit my own comments??
Note that I have been able to rebuild the RPM with 6.9.0, I could propose a patch and test, but I would appreciate a direction: - Patch the hardcoded list https://github.com/Ardour/ardour/blob/fad71ce748fd244611ffad397fd0c51ecbe72334/libs/ardour/plugin_manager.cc#L2055 - Create a symbolic link from /usr/lib/vst3 to /usr/lib64/vst3 (IF /usr/lib/vst3 does not already exist of course) - Add a file to /etc/profile.d to set VST3_PATH=/usr/lib64/vst3 environment variable? - Patch the script to set VST3_PATH=VST3_PATH:/usr/lib64/vst3 https://github.com/Ardour/ardour/blob/master/gtk2_ardour/ardour.sh.in ? Which way should I go to make Ardour work out-of-the-box without bothering users?
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
FEDORA-2022-f1f05aa2ae has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f1f05aa2ae
FEDORA-2022-65135db61b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-65135db61b
FEDORA-2022-02dc9982b5 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-02dc9982b5
FEDORA-2022-f1f05aa2ae has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-f1f05aa2ae` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f1f05aa2ae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-65135db61b has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-65135db61b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-65135db61b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-02dc9982b5 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-02dc9982b5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-02dc9982b5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-02dc9982b5 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-f1f05aa2ae has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-65135db61b has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
@brunovern.a Do you have any vst3 packages that install in /usr/lib64/vst3 ? I don't, but https://steinbergmedia.github.io/vst3_dev_portal/pages/Technical+Documentation/Locations+Format/Plugin+Format.html defines the vst3 format as bundles (directories) that (can) contain multiple architectures, for example both MyPlugin.vst3/Contents/i386-linux/ and MyPlugin.vst3/Contents/x86_64-linux/ . There is thus no good FHS / packaging compliant place for such files. But https://steinbergmedia.github.io/vst3_dev_portal/pages/Technical+Documentation/Locations+Format/Plugin+Locations.html says /usr/lib/vst3/ , and I think the Fedora package should follow upstream and support that without adding to the proliferation of non-standard plugin locations.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days