Looking for testers for my DAW: OMNI! (Windows / Linux) 🎧🚀

[id3at]

Hi everyone!
My proprietary DAW – OMNI – is fast approaching the beta phase. Before that happens, though, I need to thoroughly test the alpha version under battle conditions. And that's where I need your help!
I'm looking for enthusiasts and producers who would like to drop OMNI into their daily workflow, test the application on their own hardware, and report all encountered bugs, crashes, or feedback directly to me.
What you should know:

Systems: I'm looking for people working on both Windows and Linux.
Form: Complete volunteering – we're doing this out of passion!
How it works: Each tester will get access to a dedicated folder where I will be uploading the latest builds on an ongoing basis.
What do I offer in return?
In addition to my immense gratitude and a real impact on the program's development – when the application enters the beta phase, I will create a special thank-you tab on the website. If you wish, your name (or nickname) will appear there with an official note on how you helped build OMNI.
How to apply?
Write to me here in a private message or directly through the website: omnidaw.com
Huge thanks in advance for any support. Let's create something cool together!

[Stephan326]

I am willing to test

[id3at]

Awesome! Thanks for reaching out and willing to help.
​Please head over to omnidaw.com and drop me a message through the website to get things started. Also, let me know which operating system (Windows or Linux) you'll be testing OMNI on so I can get the right build ready for you.
​Looking forward to working together!

[id3at]

I invite everyone interested to test the new Iris synthesizer, a combined MIDI FX panel, FX modulation and device, in one chain.
https://omnidaw.com/news/iris-ai-create ... ipiec-2026
OMNi - Let's get ready FOR the beats!

[audiojunkie]

This looks very interesting!!!! How do you plan to monetize it?

[audiojunkie]

What copy protection will it use?

[id3at]

Thanks! It's a completely free project with absolutely no copy protection. I don't plan to force any monetization—I'll just rely on voluntary 'pay-what-you-want' donations if a community ever forms. Please note it's provided 'as is' without warranty.

[audiojunkie]

Thanks! It's a completely free project with absolutely no copy protection. I don't plan to force any monetization—I'll just rely on voluntary 'pay-what-you-want' donations if a community ever forms. Please note it's provided 'as is' without warranty.

I love that! I would advise that you add a minimum to the 'pay-what-you-want' donations. PWYW has a history of not doing too well with monetization.

[keys_au1]

Genuine question: What can it offer over Reaper on Linux? If this is substantial then I'd be happy to try it out, but I'd only be using it on Linux. I am not dual-booting at all. In fact using zero windows software is the goal.

[audiojunkie]

Genuine question: What can it offer over Reaper on Linux? If this is substantial then I'd be happy to try it out, but I'd only be using it on Linux. I am not dual-booting at all. In fact using zero windows software is the goal.

Well.... Reaper now supports containers, but they only support serial or parallel connections. They don't have the ability to branch like Element can. This could be really important and useful if you are doing a setup like I suggested above, where you can load one setup instance while using the other instance. I'm not sure about Carla--it may be able to do that too, but I don't know. I would suggest downloading the newest free binary version available, and see what it does for you. If you like it, you can pay for the newest version. That way, you don't lose any money while you are testing things to see if they will do what you need.

[keys_au1]

Genuine question: What can it offer over Reaper on Linux? If this is substantial then I'd be happy to try it out, but I'd only be using it on Linux. I am not dual-booting at all. In fact using zero windows software is the goal.

Well.... Reaper now supports containers, but they only support serial or parallel connections. They don't have the ability to branch like Element can. This could be really important and useful if you are doing a setup like I suggested above, where you can load one setup instance while using the other instance. I'm not sure about Carla--it may be able to do that too, but I don't know. I would suggest downloading the newest free binary version available, and see what it does for you. If you like it, you can pay for the newest version. That way, you don't lose any money while you are testing things to see if they will do what you need.

Sorry that post was re the Omni DAW in the post above...I should have made that comment in my post.

[id3at]

Your approach: "using zero windows software is the goal" is exactly our philosophy when creating Omni. Linux isn't a "second-class" system to us where we just compile the code—Linux is our primary development system where we work and test Omni every day.

Everything under Omni's hood is optimized for the Linux audio ecosystem:

Native PipeWire and JACK integration: Omni registers directly as a client in the system graph, creating its own audio and MIDI ports (out_L/R, in_L/R, midi_in/out) and supporting transport synchronization (JACK Transport) without any bridges. It also features an automatic fallback to ALSA.

Low-level RT optimizations at the Linux kernel level: During audio thread initialization, our Rust engine executes native system calls:

libc::pthread_setschedparam – assigns the thread the highest real-time priority (SCHED_FIFO with a priority of 70).

libc::mlockall(MCL_CURRENT | MCL_FUTURE) – locks the entire DAW memory in RAM, preventing page faults, which is a crucial condition on Linux for avoiding audio dropouts (xruns).

Modern GUI for Wayland / Tiling WMs: The interface (egui) is hardware-accelerated and supports so-called egui viewports. This allows "detaching" panels (mixer, Piano Roll, arranger) into separate native system windows, which works brilliantly on Linux tiling environments (i3, Sway, Hyprland) and pure Wayland.

Native distribution format: Omni's primary output format on Linux is an AppImage, allowing you to run it on any distribution without fighting dependencies.

Since you use REAPER exclusively on Linux, I'd love to ask about your experiences with it. In Omni, we set out to solve a few problems right at the architectural level. How do these issues look from your perspective in REAPER?

How do sandboxed plugin windows behave? Does running a plugin in a separate/dedicated process on Linux integrate stably with the DAW, or do the windows "float" over the interface and, for example, lose focus in tiling window managers? (In Omni, isolated CLAP/VST3 plugins integrate seamlessly inside a single interface thanks to our custom IPC).

What happens when a plugin crashes during scanning? Can it freeze REAPER's entire startup process, forcing you to kill it in the terminal? (In Omni, the plugin scanner runs in a dedicated sandbox—if a plugin crashes, the scanner process dies, the plugin is blacklisted, and the DAW continues to boot up).

Does PipeWire integration work "out of the box"? Does REAPER automatically adjust to the system server's sample rate, or does it require launching through wrappers like pw-jack?

How do you handle a clip and sequencer-style workflow? For Live Looping or an advanced step sequencer (e.g., with note randomness and probability), do you have to install JSFX/ReaPack scripts, and how does that cooperate with the Undo/Redo system of the entire project? (In Omni, this is a native part of the DAW's core).

I'd love to hear how this looks from your side, because we want Omni to be the best possible environment for uncompromising Linux users!

[audiojunkie]

I have another question—does OMNi DAW support X11 plugins?

[rockheyday]

I love that! I would advise that you add a minimum to the 'pay-what-you-want' donations. PWYW has a history of not doing too well with monetization.

You are totally right, PWYW does not work well for the developer! It should be monetised because he spends so much time for the project.