search

robbert-vdh / yabridge

A modern and transparent way to use Windows VST2, VST3 and CLAP plugins on Linux
GNU General Public License v3.0
2.25k stars 56 forks source link

(Bug?) Sonarworks reference 4 plugin not discovered in Reaper #162

Closed score100 closed 2 years ago

score100 commented 2 years ago

Thanks for giving yabridge a shot!

Problem description

Background: Sonarworks used to develop their vst plugin also for linux for a while, but that is unfortunately no longer the case. Therefore I've tried to see if I can get their windows vst-version working.

I can put the .dll plugin into my VST2 directory. Yabridge-sync finds it and does and creates a .so. But unlike other plugins in the folder Reaper just will not find it. Can not see why, even after re-scanning and re-launching the app several times.

Any help on this? I'm still new to this fabulous program but so far setting up vst's had been a breeze.

What did you expect to happen?

That Reaper would discover the plugin

What actually happened?

It's untraceable

Operating system

Lubuntu 20.04

How did you install yabridge?

From the release page

yabridge version

3.7.0

yabridgectl version

3.7.0

Wine version

wine-7.1 (Staging)

Plugin

Sonarworks Reference audio

Plugin type

VST2

Plugin architecture

64-bit

Host

Reaper

Desktop environment or WM

No response

GPU model

No response

GPU drivers and kernel

No response

Debug log

No log shows up in /tmp/ :(

Anything else?

It looks to me like it had actually recognized previously that there is indeed a plugin. But it doesn't show up in the list of plugins.

robbert-vdh commented 2 years ago

Can you show me a screenshot of the directory containing the VST2 plugin's .dll file and the .so file created by yabridgectl in a file manager/from ls -Al, a screenshot of the plugin locations dropdown in REAPER, and the plugin blacklist dropdown in REAPER?

robbert-vdh commented 2 years ago

Oh and Sonarworks Reference 4 does still have a Linux version, I think it's just hidden somewhere deep on a support page now. Or you may need to use the wayback machine to find it if they've taken down that page in the meantime.

score100 commented 2 years ago

Thanks for the swift reply!

Can you show me a screenshot of the directory containing the VST2 plugin's .dll file and the .so file created by yabridgectl in a file manager/from ls -Al, a screenshot of the plugin locations dropdown in REAPER, and the plugin blacklist dropdown in REAPER? screen3 screen2 screen

Here you go. Apparently it just fails to load it. When clicking on plugins that failed scanning it tries to load it for some seconds, then nothing happens. And it still isn't in the list after.

Oh and Sonarworks Reference 4 does still have a Linux version, I think it's just hidden somewhere deep on a support page now. Or you may need to use the wayback machine to find it if they've taken down that page in the meantime.

All I found so far where dead links. Might be able to retrieve it by contacting Sonarworks. Anywhow, they already said they've abandoned it and not getting any futures updates feels like a drawback when it comes to investing in a license.

robbert-vdh commented 2 years ago

(Sorry I was away for a day!)

Likely the plugin relies on some library that's either not present or disabled in your Wine prefix. Since the plugin is blacklisted, REAPER won't try scanning it again. So you'll need to:

  1. Close REAPER if you already have it running, then reopen it with rm -f /tmp/yabridge.log; env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=1+editor reaper. Make sure you don't load a project or anything else.
  2. Go to that 'Plugins that failed to scan' dialog again, and click on Sonarworks Reference plugin at the bottom of that list.
  3. You'll now have a log file at /tmp/yabridge.log. Reading through that you can probably already figure out what the problem is, but you can also attach it here. If for whatever reason that file does not get created, check REAPER's output in your terminal from the moment you tried to rescan the plugin.
score100 commented 2 years ago

Now worries about being away, you already deserve credit enough for all of this :) Here is the log https://pastebin.com/Stv6f34V

Did not found any clear instructions online how to deal with this.

robbert-vdh commented 2 years ago

Did you launch REAPER with the command I told you to use and did you copy this from /tmp/yabridge.log? There's a lot of information missing from the output you posted.

score100 commented 2 years ago

Hi I did, but realized I might have closed one window to early. Here is one again https://pastebin.com/SH10hC9X

robbert-vdh commented 2 years ago

So the plugin returned a null pointer while initializing. That's at least not a Wine bug or anything, but the plugin intentionally doing that. Now why it might do that, I have no idea. The common reason for that would be DRM. Did you activate Sonarworks under Wine yet?

score100 commented 2 years ago

No it isn't activated yet. But normally you shouldn't have a problem with that. From trying it on windows I know you will be able to load it just fine as a plugin and then are able to select a trial.

score100 commented 2 years ago

Also a thing to mention: as the sonarworks installer won't work on linux I just copied the .dll file from my windows vst folder to my linux wine -vst folder. Could it be that the .dll of a vst depends on other files set in the installation?

robbert-vdh commented 2 years ago

Yeah that's definitely the problem. Software that doesn't come in a .zip archive is almost never portable like that.

davidhaley commented 2 years ago

FYI, there is a .SO (linux-compatible) version of Sonarworks Reference 4; however, as you have already pointed out, it's technically no longer maintained.

I saw a post here mentioning to email them and request it: https://support.sonarworks.com/hc/en-us/articles/360013444319-Reference-3-4-software-releases-component-matrix-and-support-status-

I emailed them and received this file: https://support.sonarworks.com/attachments/token/ruZKv1I1wY6RSXCiU7ECOvnlQ/?name=Sonarworks+Reference+4+VST+Plugin+4.4.9.9+%281%29.tar.gz

I consider this a temporary solution though since it's no longer maintained. Using the windows VST inside yabridge would be the best solution.

It would probably be good to email them as well, so they know that the linux plugin is in demand - perhaps they will choose to maintain it again.

Hope that it helps in the meantime.

robbert-vdh commented 2 years ago

Closing this since this is a configuration issue and there has not been a response in a while.