osxmidi/linvst-x

Linux Windows Vst Wrapper

linvst-x's Issues

Error when trying to load Altiverb 7

Please, make me know if I can provide you more information.

This is the output of lin-vst-server-x.exe.so

Loading  /home/devnix/.wine/drive_c/Program Files/Steinberg/VSTPlugins/Audio Ease/Altiverb 7.dll
0009:fixme:ver:GetCurrentPackageId (0x228910 (nil)): stub
0009:fixme:heap:RtlSetHeapInformation 0x10000 0 0x229740 4 stub
0043:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
MplugInstanceErr
Load Error
0009:fixme:win:RegisterTouchWindow (0xc0072 00000002): stub
0009:fixme:win:RegisterTouchWindow (0xd0070 00000002): stub

In general, it feels way more performant than LinVst, and it doesn't have some keyboard/mouse glitches that I suffered with LinVst (for example, clicking or dragging with the Ctrl key)

Wine-staging 6.4 and stack overflows

Hi there!
I'm not sure if it's the same issue as #3, but here we go:

Tested with:

• manjaro
• reaper 6.25 (linux 64-bit)
• LinVst: 3.15
• LinVst-X: 4.0 (but same issue with 3.2 it seems)
• wine: see below

With wine-staging 6.2:

• Fresh boot
• If I load a pretty big project (~80 instances of FabFilter stuff loaded in LinVst-X; and lots of LinVst stuff as well), all loads fine and for lin-vst-server-x.exe the taskmanager shows me RSS: 1.2GB and CPU: 5%
• If I then close reaper, for lin-vst-server-x.exe the taskmanager shows me RSS: ~600MB and CPU: 0%
• If I repeat loading that project and closing Reaper again, it keeps working. Only thing that seems strange though is that the taskmanager RSS value keeps rising for both "cases" (i.e. Reaper running, Reaper closed) by about 100MB per iteration of this procedure
• but lin-vst-server-x.exe keeps running throughout and will always come back down to CPU: 0% in taskmanager

With wine-staging 6.4:

• Fresh boot
• If I load the same pretty big project (80 instances of FabFilter stuff load in LinVst-X; and lots of LinVst stuff as well), all loads fine and for lin-vst-server-x.exe the taskmanager shows me RSS: 1.2GB and CPU: 5%
• But if I then close reaper, for lin-vst-server-x.exe the taskmanager shows me RSS: 0MB and CPU: 20%.
• Furthermore the terminal output I started Reaper in shows a stack overflow:
  jack: deactivated client jack: close client dssi-vst-server[1]: exiting 012c:err:virtual:virtual_setup_exception stack overflow 1872 bytes in thread 012c addr 0x7bc266cc stack 0x1308b0 (0x130000-0x131000-0x230000) 012c:fixme:vcruntime:__telemetry_main_return_trigger (0000000180000000) dssi-vst-server[1]: exiting dssi-vst-server[1]: exiting dssi-vst-server[1]: exiting
• htop, while it's output truly doesn't look helpful for wine (as you mentioned before) shows the Z status; according to ps man page Z defunct ("zombie") process, terminated but not reaped by its parent
• If I try starting Reaper again at this point with the same project (or any other project using LinVst-X), it just hangs and won't load. Probably because of that rogue lin-vst-server-x.exe process.
• If I then SIGKILL the server, then wine will soon afterwards terminate as well
• If I now try to start Reaper, it still hangs, because lin-vst-server-x.exe is neither running, nor being auto-started.
  • Question: I assume this is by design? At least to me it seems that once the server has been killed manually once, it won't auto-start anymore
• Anyway, if I then manually start the server, I can start Reaper with that big project just fine again. But closing Reaper will once again end up with that stack overflow and that rogue, high CPU usage server lurking around
• but here's the interesting part:
  • doing all this with a manually started server and loading a minimal project with just one VST loaded (I used this: https://www.voxengo.com/product/msed/ ) with LinVst-X does not produce a stack overflow
  • but even just loading up 10 instances of that VST in the same single track and then closing Reaper will cause a stack overflow (for me at least)
  • I also tested this on my laptop: same setup re versions and same behaviour

So would be interesting if you can reproduce this minimal example.

Just want to say WOW.

I used Carla and its VST bridge with a windows x64 vst and got severe xruns at 64 samples, better but still unusable at 128 samples. With the precompiled (buster) linvst I can use the same vst at 64 samples without any xruns. Amazing!

LinVst-X with wine-6.3 (Staging)

Hello,
I'm trying LinVst-X on Ubuntu 20.04.2 LTS but it doesn't work. Plugin scan in Reaper stoped on "VST Plugin is not responding". Probably it is problem with wine 6.3 (Staging). Downgrade is little bit tricky on ubuntu...

confusing build instructions

Hi, I-m having trouble with the install instructions. in the README you say.

LinVst-X binaries are at https://github.com/osxmidi/LinVst-X/releases

The usual X11 and Wine dev packages and multilib are needed (details are in the LinVst Make Guide https://github.com/osxmidi/LinVst/tree/master/Make-Guide) then

make

sudo make install

First, why do I need to use make, etc if I downloaded binaries? Maybe you need to distinguish this in the README file.
Then you continue with:

See the convert folder Notes on how to make the linvstx.so renaming conversion utilities.

I can't find those notes and i don't know if I do want to make the "linvstx.so renaming conversion utilities". What's that?

Finally, I tried to build the LinVST-X deb-package but I don't understand if I do need both sources since the guide mentions
folder "64bits-32bits" which is not present in the "X" version?

I think you should clear this up in the docs. Maybe adding a straightforward step list for each target, for the both versions.

I could help with the docs, maybe. Just need the answers.

Ways and solutions to run old dxshelled dx plugins

Linvst is better than yabridge. It consumes 3x less cpu power! Beware! I have wrapped to dlls old dx plugs like timeworks millenium pack, dx reverb, hyperprism, etc using xlutop dxshell utility. Dxshell-wrapped plugs load and work fine via wine in vst plugin analyzer or art console but some of them, namely millenium pack from 1998 and anwida dx reverb do not work in a daw loaded as .so linvst wrapped plugs and no matter which wine prefix i use from win95 to win7. When testing via testvst32.exe.so reverb.dll i get segmentation fault error, when via testvst32.exe it says Libraryloaderror. How can i fix it? By the way hyperprism dx pack from 1997 runs fine under dxshell->linvst. Which libs do i need to install and how to give support to those failing plugins?

Crashes when closing a DAW

Hello,

I have been using LinVst-X a lot recently with some orchestral sample libraries, but have been running into the following issue...

OS: Ubuntu 20.04
DAW: Ardour 6, Reaper
Plugins: Spitfire BBCSO Discover, Native Instruments Kontakt

1. Create a project in the DAW, and load plugins via LinVst-X. Save the project.
2. Try to close the DAW. After a few moments it crashes and displays the 'Not responding... Force Quit/Wait' window. Choose the 'Force Quit' option.
3. The LinVst-X server is still running and visible in System Monitor (as expected). However if you try to launch the DAW again it simply crashes and will not open.
4. If you kill the LinVst-X process, this doesn't solve the problem - the DAW still won't relaunch. Also, if you try to restart LinVst-X by killing the process and then typing '/usr/bin/lin-vst-server-x.exe.so' in a terminal, it just says 'Segmentation fault'.
5. It seems the only way to get the DAW and LinVst-X running again is to reboot the computer.

I hope that's all clear - let me know if you need anything else!

LinVst and LinVst-X not working at all.

Hi, I reinstalled my OS and after that bitwig 3.3 doesn't recognize my converted VST. Native VST works well.
Wine version: 6.3
OS: Manjaro gnome edition

Need help asap if it's possible (gotta finish one project)
Thanks

-DNOFOCUS compile flag no longer has original effect

Hi osxmide, similar topic as for osxmidi/LinVst#222

I tried applying the -DNOFOCUS compile flag here as well, using Makefile-64bitonly.

In this case the build worked fine and I was able to bridge plugins (e.g. FabFilter stuff).

But the issue is that the focusing behavior is not what it used to be. The plugin window still grabs the focus and only clicking outside of plugin window will give focus back to reaper.

What I had used before:

• linvst-x: git c5d7b6c (one commit before 4.1 tag (for whatever reason))

What I tried here:

• linvst-x: 4.78 (specifically git fa0308e)

Again, maybe you can have a look when time permits!

Can LinVst-X coexist with LinVst?

I've been able to load a lot of plugins with LinVst but now I need to use Virtual Sound Stage 2, which communicates between instances and doesn't seem to work with LinVst.

I've deleted all my generated .so files with the LinVst-X tool, but it seems like now Reaper doesn't add as scanned any of these plugins. This would start working again if I generate the .so files for standard LinVst.

Is there something I am missing? Can LinVst.X coexist with LinVst on the same machine or I do have to uninstall it?

Thank you so much!

LinVst-X Server not closing on DAW close and using high CPU vs LinVST

This applies only to LinVST-X not LinVST. I have only tested the VST2X version not VST3X.

On First load of a LinVST-X wrapped plugin, LinVST Server takes 10% of my CPU. A LinVST wrapped plugin only uses about 1% of my CPU on first load. Subsequent loads of LinVST-X plugins do not use much more CPU, but the CPU usage compared to loading even the same plugin wrapped as LinVST instead of LinVST-X uses 10 times the CPU which seems pretty odd.

Also, when closing the DAW (Reaper 6.05), LinVST Server-X does not close and continues to use 10 percent of the CPU. When using the regular LinVST Server, it closes as expected and does not continue to take up CPU.

This is on Manjaro Linux with 5.5.8 Kernel and Wine Staging 5.3.1