How To Use MuLab 10 With Linux

[oldcastle]

How To Use MuLab 10 With LinuxI've been running MuLab 10 on Linux for a while now with great results. Here’s a structured guide to help others do the same. The good news: each version of this guide gets shorter because things keep getting easier.

---

Quick Start (TL;DR)

1. Tune your Linux system for professional audio using rtcqs.
2. Install the latest version of Wine (prefer WineHQ packages over distro defaults).
3. Download and extract MuLab 10 (Windows 64-bit).
4. Run wine MuLab.exe from the MuLab folder.
5. In Audio Setup, select PulseAudio (PipeWire users: it works via pipewire-pulse).

That’s it — MuLab should be up and running!

---

Disclaimer

• Linux is not officially supported by MuTools (yet). Don’t report Linux-specific issues to MuTools; instead, use the WineHQ forums.
• Linux distros vary. Treat this guide as a reference, not a copy-paste script.
• Tested with: MuLab App 10.0.84 for Windows (64-bit).
• Assumes a fresh Wine install or Wineprefix. If you use custom prefixes, you should already know what you’re doing.

---

Step 1: Prepare Your System for AudioBefore running MuLab, make sure your system is optimized for low-latency audio.Using rtcqs

1. Download from rtcqs releases (latest version: 0.6.7 at the time of writing).
2. Install following the installation instructions.
3. Run the script — it reports OK (green) or WARNING (red).

Aim for as many greens as possible. Some warnings matter more than others (e.g., running a Preempt-RT kernel is more important than disabling Spectre/Meltdown mitigations). Each warning includes a link to a potential fix, but commands differ by distro — check your documentation. You only need to do this once per system.

---

Step 2: Install WineMost distros ship outdated Wine versions. The best option is to install the official WineHQ packages:

• WineHQ download page
• Always prefer stable or staging builds.

Tip: Some Windows VSTs require 32-bit libraries — make sure wine32 is installed.Once installed, create your Wine prefix (usually auto-created as 64-bit):winecfg

---

Step 3: Run MuLab 10

1. Download MuLab 10 (Windows 64-bit) from MuTools.
2. Extract the files to a folder (e.g., ~/Applications/MuLab).
3. Launch:wine MuLab.exe

If double-clicking doesn’t work, your distro may not enable binfmt integration. Just run with wine MuLab.exe manually.On first launch:

• Accept the User License Agreement.
• In Audio Setup, choose PulseAudio.

(PipeWire users: pipewire-pulse provides seamless compatibility.)

Congratulations — MuLab 10 is running on Linux!

---

Troubleshooting & HiccupsMultiple Windows Bug

• Issue: When multiple floating windows are open (e.g., plugin + color window), drag-and-drop events fail due to Wine’s handling of PeekMessage + GetMessage.
• Status: Reported at WineHQ Bug 57697.
• Workaround: Minimize unused windows before drag/drop. Fortunately, it’s not workflow-breaking.

Other Possible Issues

• Fonts not rendering → Install ttf-mscorefonts-installer (Debian/Ubuntu) or equivalent.
• Audio crackling → Lower buffer size in PipeWire or WineASIO.
• Plugins missing DLLs → Use winetricks to install required runtimes.

---

FAQ

Q: Do I need ASIO drivers?
Not always. If your system is tuned for audio, PipeWire + PulseAudio backend is usually good enough. Try it first. If you need lower latency (especially for live recording), install WineASIO.

Q: Can I run Windows VSTs?
Yes. Since you already use Wine, most Windows VSTs should work out of the box.

Q: How do I add MuLab to my desktop menu?
Create ~/.local/share/applications/mulab.desktop with the following content:

[Desktop Entry]
Name=MuLab
GenericName=Creative Music Studio
Comment=Modular DAW with synths, sampler & effects
Exec=wine /home/USERNAME/Applications/MuLab/MuLab.exe
Icon=/home/USERNAME/Applications/MuLab/mulab.ico
Categories=Audio;AudioVideo;Midi;Sequencer;
Keywords=Audio;MIDI;DAW;VST;
Terminal=false
Type=Application

Replace USERNAME with your actual user. Then refresh desktop entries:xdg-desktop-menu forceupdate

---

Advanced Tweaks (Optional)

• Pin MuLab to CPU cores using taskset for consistency.
• Keep a backup of your clean Wine prefix (tar -czf wineprefix.tar.gz ~/.wine).

---

Closing Notes

Running MuLab 10 on Linux isn’t officially supported, but with Wine it’s stable and usable. The workflow is smooth, audio latency is manageable, and most VSTs run fine. With PipeWire maturing quickly, things are only getting better.Happy music-making on Linux!

[oldcastle]

Note 1: Jo, please feel free to pin, refer, share, edit, or ignore this post.

Note 2: I'll try to keep this post updated. Tips and suggestions are welcome. But remember, ML9 IS NOT officially supported, ok?

[audiojunkie]

Very cool tutorial!! Great job!!

[MuTools]

Thanks a lot for sharing this guide, oldcastle

I've included it into the M9 docs, in the FAQ section, the question about Linux:
https://www.mutools.com/info/M9/docs/mu ... swers.html

Thanks again!

[lmv]

I also use Linux and have been playing around with Mulab. My experience is a little different and it may or may not be interesting to the users and developers. I will share it anyway.

First, I am not a registered user. I want to be, but not right now. So I just have the 8.8.3 Free version and the 9.0.37 Demo version. There are interesting differences between them, but I can't be sure that everything I will describe here applies to fully registered versions of Mulab.

In 8.8.3, in Audio Setup, I can choose 'MME Audio Output' then either 'Wine Sound Mapper' or my primary sound card. I can also select the HDMI output, but I have nothing connected there so I can't really listen to it, but it seems to be accepted and play sound. Notably absent is my external USB sound card to which I connect my headphones. The primary sound card is connected to a crappy desktop loudspeaker that I use very rarely. But if I select Wine Sound Mapper and I configure JACK to play through my USB sound card, I can use the headphones.

If I choose ASIO, then my only complementary driver choice is WineASIO, and it also works perfectly. Whether it plays through the loudspeaker or headphones depends on my JACK configuration. All good.

Now, in 9.0.37, I can choose 'MME Audio Output' then either 'Wine Sound Mapper' or my primary sound card, except that the playback becomes so slow and jerky that the entire application becomes unusable. Only ASIO/WineASIO works well with 9.0.37. No big deal. I just think that something that worked so well in an older version might as well work on the new version. Why not? You can never have too many options.

I also have the problem with some widgets not working correctly, they flash for a millisecond and disappear, including the About screen. I solved that problem creating keyboard shortcuts for them. They don't flash and disappear when triggered by a key shortcut, God knows why.

"Can I use Linux VSTs?"

This is an interesting issue. In theory, yes, you can. Does Mulab want you to, though? That is quite complicated.

Note that I don't use PulseAudio. I only use JACK or ALSA. JACK runs on top of ALSA anyway. JACK is very interesting because it creates its own "plumbing." That plumbing will let you do a lot of cool stuff if applications will cooperate. Mulab does not cooperate.

Please look at this screenshot.

catia1.png

That is Catia, a JACK patchbay. It can be used to make "plumbing" connections. When I use WineASIO as the driver, all those Mulab inputs and outputs are exposed. What can I do with them? Sadly, not much and not easily.

In 8.8.3, I can click the output slot at the bottom of the MASTER rack and click 'Edit.' (That is absent from 9.0.37 so all of this only applies to 8.8.3.) From there, I can determine that MASTER send its output to out_3 and out_4. You can see that in the next screenshot. Those outputs are connected to my "Generic USB Audio Device."

catia2.png

From here, I can disconnect those and connect out_3 and out_4 to input_3 and input_4 in the "Calf Studio Gear." Calf Studio Gear is a collection of plugins, mostly effects. Then I can load some effects on it then connect output_3 and output_4 from Calf Studio Gear to my Generic USB Audio Device (i.e. my headphones) and listen to the output from Mulab altered by all those effects.

catia4.png

But can I send them back to Mulab? No, because I can't seem to find any way to use those inputs inside Mulab. I can see they are there and I can hook up audio signal to them through JACK's "plumbing," but Mulab's GUI doesn't give me any way to use those inputs. Racks have a choice of outputs (only in 8.8.3 and yet very limited) but no choice of inputs. In the screenshot above, I connected Mulab's out_1 and out_2 to my headphones, but that is just a dummy setup to illustrate a hypothetical concept. In reality, there is nothing coming out of Mulab's out_1 and out_2. MASTER was changed to use out_3 and out_4, and other racks can't use any outputs really.

Not all is lost. I still can connect Mulab to Calf and Calf to something else so I can have effects applied to Mulab's MASTER output, and record it all with something else. Note that all that plumbing setup can be saved and recalled as a preset with an application called aj-snapshot. But sadly, I can only do that to the output of MASTER. I can't change the outputs of other racks. They only accept MASTER or NONE (or other racks, but I rather fail to see how that could ever be useful).

So if I could change the output ports of other racks, then I would be able to apply effects to them individually. Even better, if I could selectively apply those inputs to racks, especially to MASTER, then I would be able to "send" each Mulab rack to a Linux effect, get the signal back and reinsert it into the project and record everything inside Mulab. That would be really cool.

What about Linux instruments? Could they be played by Mulab's MIDI composer? It's technically possible. Look at those MIDI ports exposed by ASIO. Hook up a Linux instrument to one of them, Mulab to the other and you're in business. Linux doesn't care whether it's Mulab—a Windows application—or a native sequencer issuing the notes. Linux just sees MIDI data. It will listen, it will play, and it will send audio signal back into the "plumbing." The only tiny obstacle in the way of that idea is that... Mulab does not support any of that at all. In fact, the little you can do in 8.8.3 is no longer possible in 9.0.37. 9.0.37 won't even let you change the MASTER outputs.

Since this is all about Linux and Mulab is a Windows application and we Linux users know what that means (Windows developers typically don't like to help Linux), the chances are extremely slim. But it's worth a chat. We were so close...

[pljones]

A project-level "Audio In" in MuLab is a module. You can configure it to accept the hardware ins of your choice.

[oldcastle]

Since this is all about Linux and Mulab is a Windows application and we Linux users know what that means (Windows developers typically don't like to help Linux), the chances are extremely slim. But it's worth a chat. We were so close...

Thank you for contributing and sharing your experience. I believe that the more we share, the more we can learn and assist those who want to venture into Linux territory.

I'm a wannabe bedroom producer, so my use of ML is quite simple. Because ML on Linux is not officially supported, we make do with what we have. However, I am pleased with ML 9, since right now it covers all my needs. Sure, other people's needs are probably different from mine, so Linux may not be the solution for them.

I understand that the guide could go into greater depth on a variety of topics, but that was not my intention. My intention was to get ML up and running so that we could have some fun.

[lmv]

A project-level "Audio In" in MuLab is a module. You can configure it to accept the hardware ins of your choice.

This is amazing! At first, I had no idea what you were talking about. But I investigated and yes, modules are the answer. Modules let you add/configure inputs and outputs and send out MIDI, so everything I speculated above is 100% possible and ready to go. I just tested effects, instruments, everything. The integration with Linux is complete.

So let's set this record straight:

"Can I use Linux VSTs?"

Yes! You can use Linux VSTs, LV2, LADSPA or whatever Linux has to offer. If Linux can do it, it can be used as an extension of Mulab.

Thank you for the valuable information.

[humanboeing]

I'm happy you resolved the issue
I too am looking into alternative OSes, mainly linux and bsd given the privacy issues and pushy methods of microsoft, hopefully more devs add linux support in the future.

[oldcastle]

So let's set this record straight:

"Can I use Linux VSTs?"

Yes! You can use Linux VSTs, LV2, LADSPA or whatever Linux has to offer. If Linux can do it, it can be used as an extension of Mulab.

Thank you for the valuable information.

Hey! Would you like to elaborate on this in a short how-to so that I can include it in the guide?

[lmv]

Hey! Would you like to elaborate on this in a short how-to so that I can include it in the guide?

Writing would be hard because I found Mulab's way of handling this very confusing. I achieved it, but I'm not sure how. I can't write about something I don't understand. So I made a video doing it. The video is a little confusing too, you can see I am fumbling in the dark and probably did things that were not even necessary, but it should be a starting point. You can view/stream it or download it here: https://gofile.io/d/NfrLcQ

That site deletes files after some time, so I recommend downloading it. If you have accounts somewhere where you can share the video, please do. If it says download is not available, that's temporary, just try again later.

Note: that is Mulab 9.0.37 Demo. I couldn't make MIDI work on 8.8.3 Free version, just external effects. I couldn't find a way to make a MIDI out port.

[lmv]

I'm happy you resolved the issue
I too am looking into alternative OSes, mainly linux and bsd given the privacy issues and pushy methods of microsoft, hopefully more devs add linux support in the future.

I find Mulab not just very Linux/Wine-friendly, I really like its approach to most things and the workflow in general. It's the only DAW I really like to use. I don't like this whole "modules" concept, I think it's quite confusing, but it still is the best DAW I've seen so far.

[humanboeing]

It's the only DAW I really like to use.

Same here.

I don't like this whole "modules" concept, I think it's quite confusing, but it still is the best DAW I've seen so far.

This is one of my favourite aspects of MuLab, but I can see some people may not like it because it can get quite nerdy. Good thing is most of the time you don't need to venture into modular area and stay in the front panel/composer view and still be able to compose music just fine.

[oldcastle]

Hey! Would you like to elaborate on this in a short how-to so that I can include it in the guide?

Writing would be hard because I found Mulab's way of handling this very confusing. I achieved it, but I'm not sure how. I can't write about something I don't understand. So I made a video doing it. The video is a little confusing too, you can see I am fumbling in the dark and probably did things that were not even necessary, but it should be a starting point. You can view/stream it or download it here: https://gofile.io/d/NfrLcQ

That site deletes files after some time, so I recommend downloading it. If you have accounts somewhere where you can share the video, please do. If it says download is not available, that's temporary, just try again later.

Note: that is Mulab 9.0.37 Demo. I couldn't make MIDI work on 8.8.3 Free version, just external effects. I couldn't find a way to make a MIDI out port.

I updated the guide! Thanks, lmv for the insights. Yes, I'm still confused, but I'm glad that it works.

[MuTools]

Hey i did not watch the full video but let me quickly tell that if you want to send events from within the composer to a MIDI output then send the events to a composer event output and then in the Project Modular Area connect that composer event output to the MIDI output module (= the Project Event Output module that is set to the MIDI output). This is assumed that the composer is inside the Project Modular Area. If the composer would be in a deeper modular level, then make sure to repeat the routings to upward modular levels until the composer events arrive in the Project Modular Area, then connect it to the MIDI output module.