View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007700 | ardour | bugs | public | 2018-12-05 09:31 | 2018-12-06 08:58 |
| Reporter | hcw70 | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | Ubuntu | OS Version | 18.04 |
| Product Version | 5.12 | ||||
| Summary | 0007700: LV2 Plugin Studiolink does not work | ||||
| Description | When using the Studiolink LV2 plugin from https://github.com/Studio-Link/app/releases/tag/v17.03.1-beta in Ardour as a plugin i dont get a connection to any of the test accounts (i.e. "freakshow1@studio-link.de") if using from within ardour. If using Studiolink-standalone it works (via pulseaudio). It also works when using via "jalv http://studio-link.de/plugins/lv2/studio-link " which is a LV2 standalone host. | ||||
| Tags | No tags attached. | ||||
|
|
A quick look at https://github.com/Studio-Link/overlay-lv2/blob/master/build.sh It seems the plugin dynamically links against openSSL. Does it also and rely on system-wide certs? |
|
|
PS. A quick-look at the binary confirms this. The plugin pollutes the global namespace with its own TLS and undefined X509: `nm -g ~/studio-link.lv2/studio-link.so` It likely fails in Ardour because Ardour itself uses curl with openSSL and comes first (while jalv doesn't). In short, please link your plugin statically. Plugins should be self-contained and not expose any symbols that may conflict or interfere with other plugins or the host. Many other plugins also use openSSL internally for license checks so this is crucial. Check with `nm -g studio-link.so` and `objdump -T studio-link.so` try CFLAGS="-fvisibility=hidden -fdata-sections -ffunction-sections" LDFLAGS="-fvisibility=hidden -fdata-sections -ffunction-sections -Wl,--gc-sections -Wl,-O1 -Wl,--as-needed -Wl,--strip-all" for the plugin and all dependencies |
|
|
Thanks for you quick analysis!!! I will forward this to the studio-link developers! |
|
|
(Re)Opened a ticket at https://gitlab.com/studio.link/app/issues/8 . Lets see if that outcome solves the issue. |
