Debugging plugins

[osxmidi]

Debugging plugins

[osxmidi]

There are various ways to try to work out what dll's might be needed to be overridden or added or disabled.

There is the wine debugger report when it crashes that lists the dll's that were loaded.

Also, using a hex editor on the vst binary and text searching for dll is another method.

I could not initially get the new Line 6 Helix to run, but I picked up that the msvcr120.dll and gdiplus.dll (and especially the gdiplus.dll) were probably causing problems from scanning the vst Helix binary with a hex editor to see what dll's it might have been using.

The dll's that cause a fair amount of trouble are, d2d1.dll (it's only partially implemented in Wine), gdiplus.dll, wininet.dll (net connection) and maybe some others.

[osxmidi]

I downloaded Sampletank 2.5.5.b and eventually got it to run ok with Linux Reaper on Debian 9 with Wine Staging 2.18.

The install is not smooth and I had a few Wine crashes during it, and one initial crash in Reaper where it seems to want some path set to it's wine default install path, so even though it crashed, the path dialog box was still up and so I just hit ok.

It seems ok after all of that.

[osxmidi]

I just reread your post.

I think the problems are due to you using wine-rt 2.0.1.

wine-rt can have problems and usually wine-staging is recommended instead.

wine-staging can have priorities set, so it can replace wine-rt and it's priorities.

[lgarrido]

OK, so a possible line of tracking problematic DLLs could be just scanning which of them are used and trying to override them one by one in winecfg.

$ strings .wine32/drive_c/Program\ Files/VstPlugIns/SampleTank2.x.dll | grep -i dll
kernel32.dll
mscoree.dll
user32.dll
KERNEL32.dll
USER32.dll
ADVAPI32.dll
VST.dll

I will look into wine-staging, thanks! wine-rt 2.0.1 is what KXStudio provides, to date.