Disclaimer
- Linux IS NOT officially supported by MuLab, so don't report issues related to Linux here. The best way to get some help is to post your issues at the https://www.winehq.org forum
- Since Linux distros differ from each other, do not take this guide as a copy and paste solution. You may need to make some adjustments to the steps presented here to fit into your Linux distro
- This guide is written using MuLab App 9.0.42 for Windows (64 bit)
- I assume a fresh install of Wine or at least a fresh Wineprefix. Anything different from this, you should know what you are doing
Before we get into the steps to get ML9 running on your Linux, we need to tweak your distro to be "professional audio friendly," which requires adjusting some Linux settings. Using https://codeberg.org/rtcqs/rtcqs is an easy way to figure out what to change. Rtcqs is a Python utility that analyzes your system and detects potential bottlenecks that may have a negative impact on system performance when working with Linux audio. This is how I go about it:
- Go to https://codeberg.org/rtcqs/rtcqs/releases
- Check the latest stable version (0.5.2 during this writting)
- Download the rtcqs_x86_64 file and give execution permission 'chmod +x rtcqs_x86_64' to it.
- Execute the script './rtcqs_x86_64'
It's time to install Wine after you've made your system "audio friendly." But which version of Wine should you install? Most of the time, the most recent version is superior. But this is where distros diverge. Some distributions will have the most recent Wine package available for you, while others will not. If your distro doesn't update Wine packages frequently, it's up to you to find and test repositories that offer more up-to-date versions of Wine.
Finally, install your Wine package or create your Wine prefix; most distributions create a default Wine 64-bit prefix.
Running MuLab 9
All of the heavy lifting has been completed. Now comes the easy part. Begin by downloading and extracting ML9. To see the magic happen, navigate to the MuLab (64 bit) folder and double-click the MuLab.exe file.
If nothing happens after the double click, see if your Wine package includes a binfmt file that allows you to run Windows programs directly, such as ./myprogram.exe, which will launch as if you had typed wine./myprogram.exe. This varies from distro to distro, so if in doubt, contact your distro's support, NOT HERE.
If everything is fine, you are now presented with the MuLab 9 User License Agreement. Agreeing on that, we reached the Audio Setup. Just change your Audio Driver Name to Pulseaudio and the rest is history
That's it, MuLab 9 is up and running on Linux. Congratulations!
Hiccups
The only issue I encountered while working with ML9 was the window losing focus on certain parts of the program. The problem has been reported in the Wine forum: https://forum.winehq.org/viewtopic.php?f=8&t=36332. The good news is that there are at least three different solutions to the problem. Let's look at them now:
- This is the simplest way for me to get around this problem. There are no special settings required. Simply create a shortcut for the problematic function. My two major stumbling blocks, for example, are the "Choose Target Module" and "Choose Midi Channel" sub-windows. That was fixed by creating two shortcuts, as shown below.
- You may be familiar with the virtual desktop if you play games with Wine. Simply run 'winecfg,' navigate to Graphics, check Emulate virtual desktop, enter the size of your desktop, Apply, and OK. When you start ML9 again, your virtual desktop will appear and you will be able to use it normally. This appears to be the most "reliable" method, and it is the one I use.
- Uncheck the box labeled "Allow the window manager to control the windows." Be aware that this workaround has some unintended consequences, such as the inability to use TAB+ALB, minimize the window, or use your desktop task manager.
Other solutions may exist, but the above should be enough. So, which one is better. The one that fits your workflow better.
FAQ
Is it stable?
Like a native version.
How about performance?
Like a native version.
Are the graphics good?
Like a native version.
How about latency? Do I need to install ASIO?
Perhaps not, but it depends on your requirements. You should be fine if your system is "professional audio friendly," as specified in the requirements above. My system, for example, only works with Pipewire. So, I've got Wine configured with PulseAudio (Wine has built-in support for PulseAudio), which is actually pipewire-pulse. In reality, Wine is using a low-latency audio driver via pipewire. I've never had a latency issue, possibly because I don't do much recording. Try out your current configuration. If it works, that's all there is to it! If that doesn't work, try installing WineASIO.
Can I use Linux VSTs?
Indeed, you can! But it's not that straightforward. Thanks to lmv for pointing out how to do that. Also Jo gave more insights here viewtopic.php?p=8462197#p8462197
How can I use Windows VSTs on Linux?
Use Wine. Since you already have your system tweaked and Wine installed, most of the plugins should function out of the box.
How to create a desktop entry to MuLab?
By default, you can not pin Windows apps on your taskbar or simply add them to your start menu. However, with a bit of code, you can fix that. Here's my mulab.desktop:
Code: Select all
[Desktop Entry]
Name=MuLab
Version=9
GenericName=Creative Music Studio
Comment=MuLab is an inspiring music studio featuring an integrated top-quality modular synth, sampler and effect engine.
Exec=wine /home/oldcastle/Applications/MuLab/MuLab.exe
Icon=/home/oldcastle/Applications/MuLab/mulab.ico
Categories=Audio;AudioVideo;Midi;Sequencer;X-Multitrack;X-Alsa;X-Jack;Qt;
Keywords=Audio;MIDI;Multitrack;Sequencer;DAW;VST;
Terminal=false
Type=Application
