My Solution for Windows Apps with Linux

[Audiojunkie]

I got tired of the back and forth with WINE for plugins (I use it for other tools, just not plugins). I want to tell you what I did. It's so simple and obvious, people will think it is cheating. As you know, there are a limited number of solutions for running Windows plugins with Linux:

• yabridge & WINE
• LinVST3 & WINE
• WINEASIO & WINE with a vst host (such as Blue Cat Audio's Patchwork) through pipewire or with Connector
• Using a Windows machine & a Linux machine with Audiogridder through a network
• Using a Windows machine and a Linux machine, and 2 audio interfaces connected together
• Possibly a Win VM with a low latency solution to Linux Pipewire

I decided to treat a tiny NUC-sized windows 11 computer with an interface as a hardware synth. I have Blue Cat Audio's Patchwork application set to run upon startup. I have the power off button configured to shut down the computer with two quick button presses. The Windows computer is headless, unless I need to troubleshoot something in the startup. I run the computer without a monitor (just like a piece of hardware). I use the RDP protocol (with audio set to not transfer), and I can access the box from my Linux machine if needed. Otherwise, I can run everything else through MIDI. A small NUC-like headless device, along with an audio interface, and it essentially IS a hardware synth. It's so simple, and avoids any problems with yabridge, LinVST, WINE, WINEASIO, etc., etc., and as an added bonus, it off loads CPU and RAM usage.

[tavasti]

I have been considering it, but this far haven't done. Main reason for not going for it is money: I would need to get one bigger audio interface, because my current interface has all inputs occupied. And to make that windows really usable, able to run more than one plugin at the time, I would need to get really bigger interface, more than 10 inputs. Meaning at least 350€ money spent on that. Will see if there will be the day I think that investment is worth it

[Audiojunkie]

Money is my biggest problem as well. And I have some hardware synths I’d like to use too, and I don’t have enough input channels on my audio interface. But I found a way to do it much cheaper. I wanted a multichannel audio card as well, but ended up not being able to afford it. Here’s the trick: use a line mixer to sub-mix your synths, using something like one of the following:

• Samson SM10 Rackmount Line Mixer $280
• ART MX822 Stereo Rackmount Mixer $230
• Behringer RX1602 V2 Rackmount Line Mixer $140
• Moukey Audio Mixer, DC 5V, 8 Stereo Ultra, Low Noise 8 Channel Line Mixer $42

Think of it as a studio expander.

I’m currently using a 2in 2out Arturia Minifuse 2 for my Linux system, as well as one for my Win11 machine.

I’m also using my pedalboard as a super powered studio effects unit, including:

• HX Stomp
• Boss MS-3
• Boss VF-1
• ElectroHarmonix B9
• DigiTech Mosaic

In addition, I’m using two:

• Cubilux 5-Way Quarter Inch Signal Splitters $22 each—one for each output. This allows me the ability to run anything I want through my outboard effects, and also feed anything to the Win11 device for any Windows 11 effects.

While I do have to record each track alone (instead of recording directly into its own channel like one would with an audio interface with more channels), until I am ready for that, I can run everything into a single stereo output. It’s not that much different from using an audio interface with more inputs.

My original plan called for a Focusrite Scarlett gen4 18i20 and a Behringer AD8200—and with cables and other things that I planned on getting, it was going to cost well over $1000. I couldn’t afford it. However, using this alternative method, I’ve found that I can accomplish nearly the same for around $200.

[Linuxmusician01]

[...]windows 11 computer with an interface as a hardware synth. [...]

Maybe a stupid question but can you operate it via Midi in your Linux DAW? Or can you only record live playing?

[Audiojunkie]

[...]windows 11 computer with an interface as a hardware synth. [...]

Maybe a stupid question but can you operate it via Midi in your Linux DAW? Or can you only record live playing?

I’m using two Arturia Minifuse 2 interfaces. They both have midi ports. I treat this headless Win11 like a hardware synth—with midi.

[Linuxmusician01]

[...]windows 11 computer with an interface as a hardware synth. [...]

Maybe a stupid question but can you operate it via Midi in your Linux DAW? Or can you only record live playing?

I’m using two Arturia Minifuse 2 interfaces. They both have midi ports. I treat this headless Win11 like a hardware synth—with midi.

Thanks. It's an alternative if software bridging won't work. Mini-PC's are affordable these days and if they're headless it's not that much of extra stuff in one's house.

[miuzik]

If you don't have a screen in you Windows PC, How do you edit vst parameters? Sorry if I lost something

[Audiojunkie]

If you don't have a screen in you Windows PC, How do you edit vst parameters? Sorry if I lost something

You don't need a second screen to control the parameters. Use your MIDI controller to control the parameters. Log into the Windows PC headless with an RDP client to further view and configure your Windows plugin. Don't forward the audio through RDP, because it will be really delayed. Connecting to the Windows machine directly with MIDI and Audio should work just fine.

Here are several RDP clients available for Linux that facilitate remote desktop connections:

• Remmina: A high-performance remote desktop client that supports multiple protocols, including RDP, VNC, SSH, and more
• TigerVNC: A robust VNC client that also supports RDP connections
• AnyDesk: A fast and lightweight remote desktop application that supports multiple platforms
• VNC Connect: A remote access software that provides high-speed streaming and customizable remote access
• Vinagre: A simple remote desktop client designed for the GNOME desktop

These clients offer various features and security options to ensure seamless and secure remote desktop access.

[sophia2005]

You don't need a second screen to control the parameters. Use your MIDI controller to control the parameters. Log into the Windows PC headless with an RDP client to further view and configure your Windows plugin. Don't forward the audio through RDP, because it will be really delayed. Connecting to the Windows machine directly with MIDI and Audio should work just fine.

Here are several RDP clients available for Linux that facilitate remote desktop connections:

• Remmina: A high-performance remote desktop client that supports multiple protocols, including RDP, VNC, SSH, and more
• TigerVNC: A robust VNC client that also supports RDP connections
• AnyDesk: A fast and lightweight remote desktop application that supports multiple platforms
• VNC Connect: A remote access software that provides high-speed streaming and customizable remote access
• Vinagre: A simple remote desktop client designed for the GNOME desktop

These clients offer various features and security options to ensure seamless and secure remote desktop access.

Among the Linux RDP clients like Remmina, TigerVNC or AnyDesk, which one do you find to be the most stable in controlling the Windows plugin remotely while maintaining low performance and latency?

[Audiojunkie]

You don't need a second screen to control the parameters. Use your MIDI controller to control the parameters. Log into the Windows PC headless with an RDP client to further view and configure your Windows plugin. Don't forward the audio through RDP, because it will be really delayed. Connecting to the Windows machine directly with MIDI and Audio should work just fine.

Here are several RDP clients available for Linux that facilitate remote desktop connections:

• Remmina: A high-performance remote desktop client that supports multiple protocols, including RDP, VNC, SSH, and more
• TigerVNC: A robust VNC client that also supports RDP connections
• AnyDesk: A fast and lightweight remote desktop application that supports multiple platforms
• VNC Connect: A remote access software that provides high-speed streaming and customizable remote access
• Vinagre: A simple remote desktop client designed for the GNOME desktop

These clients offer various features and security options to ensure seamless and secure remote desktop access.

Among the Linux RDP clients like Remmina, TigerVNC or AnyDesk, which one do you find to be the most stable in controlling the Windows plugin remotely while maintaining low performance and latency?

As long as you have two normal machines, capable of normally low latencies, there shouldn't be much affect from RDP at all, other than the use of CPU cycles for processing. RDP is a Windows protocol for transferring screen viewing and control from one computer to another through a network--a remote viewer/controller, if you will. The speed of your network will have more affect than anything else with RDP. You do not want to try transferring audio through it though--that would be too slow. The idea is to simply use RDP to see and control the things that you can't directly control through MIDI cc, such as assigning the midi, initial plugin setup, etc. Remember, you will be connecting your Linux machine's audio interface and midi to the headless Windows machine's audio and midi interface--just like you would with a hardware synth or sampler. Think of the RDP control as a replacement for the front interface built onto a hardware synth. The audio is going to come from the Windows machine's audio interface, and go directly into your Linux machine's audio interface. The midi keyboard and knob control is going to come from your midi controller, into your DAW, and out to the Windows software. For a simple example, if you have your Linux audio interface running at 2.5ms latency, and your Windows audio interface also running at 2.5ms latency, then you'll need to add up the total round trip latency--approximately 10ms +/- what the interfaces themselves add. Depending upon how sensitive to latency you are, and how low you are able to get your audio latency, the total latency should be fairly close to hardware synth latency too. Add in Direct Monitoring, and it should be very usable--regardless of the RDP client you use--and this is only while trying to record live. Playback won't be a problem at all.

In short, I would try each client, and use the one that has the best support and response for the distro you are using. I hope this helps!