Melda on Linux - Community reports

[Frankie.T]

Maybe a day we will hopefully get a linux version of Melda plugins (please ), in the mean time i think may be useful to share some infos about our running setup to help other people, and to have a kind of status on what is working and what's not.

Ofc the conversation is open because certain things can get trivial to get working and helping each other is always a plus.

I start with my current setup.

Distro: Nobara (based on Fedora)

Compatibility Layer: Soda 9 through Bottles, so i don't have to downgrade my system wine because of the yabridge/wine issue, but i can use a script that use that wineprefix to load my daw/yabridge/win plugins with my linux native daw (reaper)

Melda version: 16.04 i know it's older but it works and i don't need the new manager

Difficulties/issues: The main issue to make it work was the yabridge/wine issue, i'm not an expert linux user, so it took me a while to get it working, and i have to say that chatgpt helped me.
Plugin wise, i still didn't made any intense workload, but everything seems working, unfortunately cpu usage is way higher than windows, that's the only downside i've noticed so far.

[audiojunkie]

Maybe a day we will hopefully get a linux version of Melda plugins (please ), in the mean time i think may be useful to share some infos about our running setup to help other people, and to have a kind of status on what is working and what's not.

Ofc the conversation is open because certain things can get trivial to get working and helping each other is always a plus.

I start with my current setup.

Distro: Nobara (based on Fedora)

Compatibility Layer: Soda 9 through Bottles, so i don't have to downgrade my system wine because of the yabridge/wine issue, but i can use a script that use that wineprefix to load my daw/yabridge/win plugins with my linux native daw (reaper)

Melda version: 16.04 i know it's older but it works and i don't need the new manager

Difficulties/issues: The main issue to make it work was the yabridge/wine issue, i'm not an expert linux user, so it took me a while to get it working, and i have to say that chatgpt helped me.
Plugin wise, i still didn't made any intense workload, but everything seems working, unfortunately cpu usage is way higher than windows, that's the only downside i've noticed so far.

We are all still waiting for the WINE side of things to get the patches integrated for NTSync. NTSync is already in the kernel and ready to go, so when WINE finally gets it, it should help to greatly reduce your CPU usage for audio. (FYI, it was designed for games, but audio benefits from it too).

[Frankie.T]

Maybe a day we will hopefully get a linux version of Melda plugins (please ), in the mean time i think may be useful to share some infos about our running setup to help other people, and to have a kind of status on what is working and what's not.

Ofc the conversation is open because certain things can get trivial to get working and helping each other is always a plus.

I start with my current setup.

Distro: Nobara (based on Fedora)

Compatibility Layer: Soda 9 through Bottles, so i don't have to downgrade my system wine because of the yabridge/wine issue, but i can use a script that use that wineprefix to load my daw/yabridge/win plugins with my linux native daw (reaper)

Melda version: 16.04 i know it's older but it works and i don't need the new manager

Difficulties/issues: The main issue to make it work was the yabridge/wine issue, i'm not an expert linux user, so it took me a while to get it working, and i have to say that chatgpt helped me.
Plugin wise, i still didn't made any intense workload, but everything seems working, unfortunately cpu usage is way higher than windows, that's the only downside i've noticed so far.

We are all still waiting for the WINE side of things to get the patches integrated for NTSync. NTSync is already in the kernel and ready to go, so when WINE finally gets it, it should help to greatly reduce your CPU usage for audio. (FYI, it was designed for games, but audio benefits from it too).

I'm curious to check what will happens when wine will get those things. I just tried the latest (buggy) version, wine 10.13 staging, and cpu consumption is even higher than soda 9, so apart from the gui bug, that newer version (i know is a kind of beta, so not stable) perform even worse.

I see on the heroic game launcher, NTSync to be enabled for game, so are you sure isn't still there?

[audiojunkie]

There were a couple ntsync variations that existed and required a special compiled version of wine, but the one I am referring to is the official version that is now in the kernel, and will soon be in wine.

[mabian]

I'm using a Bottle configured with Wine 10, but I'm overriding wine 10 with wine 9 stable (tkg), and Melda plugins 17.05 work pretty well in REAPER Native Linux and Yabridge 5.1.1. It's like Black Magic, but it works.

To override the Bottle Wine, I add in the .profile file the path to a folder that contains Wine 9. So, whenever Wine cmd is invoked with my user, version 9 is called.

Looking forward to seeing a new stable asset with Wine, Yabridge, and Wayland, that makes them work out of the box.
So far I'm getting away with this workaround, and it seems pretty solid.

Hope it helps,
Mario

[mevla]

Do I get it that the new installation scheme for Melda plugins works well under Linux ? The version of Melda plugins I'm using is the one just before there was the installation method change. I will update though, as well as getting a new computer, in the next 3-4 months or so (no rush). I'm looking at running off SSD drives only (4 TB), with 32 GB of RAM for the new computer (complete plan/wish list in the Bitwig forum). I'm currently using Xubuntu and Bitwig Linux, with yabridge and wine, never had any OS problems with Melda plugins. I could continue with Xubuntu or, I could use an headless basic Debian install to which I'll manually add X.org and XFCE (like I do on Rapsberry Pi 5 anc Compute Module 5).

[mabian]

Melda Plugin Manager - and plugins - work fine here on Debian 12,13, and Ubuntu Studio with Wine 9.x + Yabridge 5.1.1 + Native Linux REAPER 7.4x.

I'm on Melda Plugin Manager 2.13 and plugins 17.05.

- Mario

[mevla]

Melda Plugin Manager - and plugins - work fine here on Debian 12,13, and Ubuntu Studio with Wine 9.x + Yabridge 5.1.1 + Native Linux REAPER 7.4x.
I'm on Melda Plugin Manager 2.13 and plugins 17.05.

Thanks !

[Hexspa]

Kazrog now supports Linux.

https://kazrog-knowledge-base.groovehq. ... word=linux

Hopefully this is a good place to mention it.

[mabian]

Update:

Now on plugins 17.06, Wine 9.0 + Bottles 52 + Yabridge 5.1.1 + Native Linux REAPER 7.5x + Linux Mint 22.

Have to set Melda plugins to run as "Separated Process" to prevent conflicts and possible hang on right-click menus.

Still working fine, even though they eat a lot of CPU, at least twice what they take on Windows.

- Mario

[rtoip]

delete

[audiojunkie]

Update:

Now on plugins 17.06, Wine 9.0 + Bottles 52 + Yabridge 5.1.1 + Native Linux REAPER 7.5x + Linux Mint 22.

Have to set Melda plugins to run as "Separated Process" to prevent conflicts and possible hang on right-click menus.

Still working fine, even though they eat a lot of CPU, at least twice what they take on Windows.

- Mario

Well, then I have some really good news for you. When Linux Mint finally gets upgraded to kernel 6.14, and you get upgraded to WINE 10.16, you will find that ntsync has been integrated in both the kernel and in WINE. This should give you a very nice upgrade in performance.

In case you haven't heard about it, here is an article showing initial performance numbers:

https://www.phoronix.com/news/Windows-NT-Sync-RFC-Linux

[mabian]

It would be really great news if Wine 10.16 would play well with Yabridge, and I don't think it does. I'd like so much to be proved wrong
In the meantime, I discovered that setting the REAPER "buffering CPU num" setting to 4 instead of "Automatic" gives an incredible burst in CPU stability ... maybe it leaves some CPUs free for system stuff I don't know... I managed to get down to 32 samples buffer (not perfect but pretty much stable). Before that I barely could go below 128. Now 64 seems stable, 128 rock solid, 32 not for the faint at heart

[audiojunkie]

It would be really great news if Wine 10.16 would play well with Yabridge, and I don't think it does. I'd like so much to be proved wrong
In the meantime, I discovered that setting the REAPER "buffering CPU num" setting to 4 instead of "Automatic" gives an incredible burst in CPU stability ... maybe it leaves some CPUs free for system stuff I don't know... I managed to get down to 32 samples buffer (not perfect but pretty much stable). Before that I barely could go below 128. Now 64 seems stable, 128 rock solid, 32 not for the faint at heart

At the rate yabridge is going (meaning really slow at getting fixed), relying on it might be a while. Consider using WineASIO, RaySession, and Reaper (windows version) to connect to your Reaper Linux version. Of course, you won't have to worry about that until Linux Mint gets the updated kernel. Maybe by then yabridge will be fixed. (...here's to hoping! )

[NWSM]

Kazrog now supports Linux.

https://kazrog-knowledge-base.groovehq. ... word=linux

Hopefully this is a good place to mention it.

And they have free Clipper =)
(sorry 4 offtopic)