I don't know what Jo has planned. I personally enjoy MuLab over WINE, more than I am likely to enjoy a native "Linux" MuLab. But that is partially because I still use MuLab 32bit (most win->lin ports end up only being 64bit [but 32bit will eventually disappear anyway]).I'm sure Jo will surprise us with a Linux version in the not-so-distant future!
There are a lot of issues with Linux. But I am a Linux, less corporate code contributed, minded user. I prefer Xorg (not Wayland), Jack (not Pipewire), light Window Managers (not Desktop Environments), muslC (not glibc), and OpenRC (not systemD). And, I still use some 32bit systems.
It isn't very likely that any commercial Linux DAW will be built over muslC. And, like with Reaper, MuLab would need to follow major Desktop Environment window managing standards. In Reaper (with no GTK/QT based Desktop Environment) I have to completely maximize a settings window, if I want the mouse to accurately connect with it (not so over Wine). Consequently, I haven't used Reaper since the early 7 releases.
The nice thing about MuLab, as a native Linux application, is that it would be one of the better Linux DAW options. It already has tons of functionality (for some maybe complete), without needing to worry about plugin compatibility. But, if you needed a Windows plugin, it might be better just allowing MuLab to be the plugin host as a Wine application, rather than bridging plugins over Wine to a native Linux MuLab.
I've had success building the VST bridge from "Carla [Kxstudio]" and using it without Carla, to host MuLab VST. This give me a nearer MuLab -> Jack connection. For example, the Composer transport obeys Jack's transport control. This isn't possible with WineAsio. Also, MIDI connections are over Jack, instead of over WineAlsaMidi. I also seem to get less Jack Xruns and error messages (i can achieve a little lower Jack latency). But, it isn't substantially better than WineAsio, unless you want that Transport control.
I'd rather have a MuLab, with built in Jack Audio support. And then a Wine utility (like WineAsio) to bridge Windows/Wine Jack Audio, to native Linux Jack Audio. But, I don't know how the Licensing works. The MuLab Jack Audio might need to be an external dll and opensource. And, I've never used Jack Audio on native Windows. It might suck, and not be worth Jo's time.
Nothing I've said here is groundbreaking. I'm just adding to the conversation.
Statistics: Posted by 4u610h346 — Sat Jan 11, 2025 10:49 pm