The Leadership Opportunity: Become the Developer Relations Specialist (DevRel)
We are searching for a visionary Community Architect—the first of four new Founders to join the Project Owner and define the technical legacy of OLMS.
This is a high-visibility, unpaid leadership role, but the return is professional capital: Founder status, verifiable public portfolio, and absolute priority for future commercial roles.
This opportunity is specifically tailored for ambitious students, thesis candidates, or early-career professionals in DevRel, Community Management, or Technical Marketing seeking a decisive career advantage.
Why OLMS Guarantees Your Professional Prestige
- Founding Member Status (Permanent): You will be formally listed as the Developer Relations Specialist, OLMS Leaders Team—a permanent, verifiable title on our site and documentation, recognized as a Project Founder.
- Professional Email Address: As DevRel, you will be granted a permanent professional email address: devrel@openlivemixingsystem.org.
- Recruitment Authority & Team Building: Your initial mission is to lead the Talent Hunt to select and onboard the three highly-skilled technical Supervisors (Architect, UX/UI, Full-Stack Developer). You define the Core Team's skill matrix.
- Verifiable Portfolio & Published Content: You will drive the project's narrative, creating high-quality, public content (The Technical Manifesto, Blog Posts, Applied Thesis Case Studies) that serves as solid proof of your expertise for top-tier future employers.
- Priority Equity/Paid Role Access: The first four Supervisors (including DevRel) have absolute priority for paid or equity positions should the project enter the Proprietary Business Phase (monetization via advanced plugins and SLAs).
The Mission: Transform Technical Obsession into a Global Community and Market Credibility.
You will be the vital bridge, translating our obsession with < 5 ms RTL and ZERO X-runs into a compelling, clear narrative that attracts high-caliber contributors and validates our vision to the industry.
Contact the Project Owner to Initiate Your Candidacy: founders@openlivemixingsystem.org
The Core Challenge: Inside the Real-Time Engine (Technical Deep Dive)
OLMS is built on a custom Linux distribution utilizing a Real-Time (RT) kernel and the PipeWire (PW) audio server. This stack is engineered for extreme stability and ultra-low latency, crucial for professional live sound.
| Component | Functional Detail | Core Objective | Key Performance Indicators |
|---|---|---|---|
| Base Platform | Custom Linux Distribution with Real-Time (RT) kernel. | Ensure minimum possible latency (goal: < 5 ms round-trip). | Round-Trip Latency (RTL) objective: < 5 ms. |
| Mixer Core | LV2 Host Orchestrated Architecture, managed by the OLMS Orchestrator Daemon (Level 3 Logic). | Provide a professional, stable mixing engine fully controllable remotely. | Control via Web Browser (HTML5/JS) using OSC. |
| Audio Server | PipeWire (PW) configured to operate with maximum Real-Time (RT) priorities to minimize latency. | Manage audio I/O and routing with maximum efficiency and redundancy. | ZERO (0) X-runs in one hour of stress testing under load. |
| Scalability & Redundancy | Core-Level Failover (Software Redundancy): Engine A / Engine B running in parallel on a single Mini-PC for immediate, glitch-free switching. | Ensure ZERO X-runs in 1 hour and maintain RTL < 5 ms regardless of DSP loads, with automatic failover. | Switching Time (Failover): < 1 ms (imperceptible). |
Distributed Signal Processing (DSP Farm)
To ensure unlimited scalability of processing power beyond the limits of a single Master PC, OLMS adopts a Distributed Processing (DSP Farm) model based on a Master/Slave architecture over Ethernet, complementary to the internal core-level failover.
| Role | Primary Function | Workload |
|---|---|---|
| Master PC (Core RT) | Management of physical audio I/O, Redundancy (Core-Level Failover), system clock, and control interface (OSC Bridge). | Light loads (Mix Bus, critical I/O, Failover Logic). Must maintain latency < 5 ms. |
| Slave PC(s) (N-Units) | Execution of high-intensity DSP plugin loads (e.g., Anti-Feedback System, complex Reverbs, Amp Simulator), delegated by the Master. | Heavy loads, managed by the Master. |
Technical Specifics: Stability, Latency, and Architecture
The OLMS vision is predicated on creating a system with Plug-and-Play reliability. This demands strict control over every layer of the stack, exceeding the capabilities of standard consumer operating systems.
Core Objectives
- Round-Trip Latency (RTL): The absolute engineering objective for the production system is consistently < 5 ms. The tolerance for the initial PoC (Proof-of-Concept) is < 10 ms. This latency must be achieved reliably from physical input through LV2 Host processing to physical output.
- Stability (X-runs): The system must guarantee ZERO (0) X-runs during an extended, one-hour stress test under typical live load conditions. X-runs are catastrophic failures in live sound.
Base Platform & Kernel Configuration
We require a custom, minimal Linux distribution. The key to our performance lies in kernel optimization:
- RT Kernel: Using the Real-Time kernel ensures audio threads receive maximum CPU priority, preventing critical audio processing from being preempted by system background tasks (e.g., networking, file I/O).
- Kernel Configuration: Meticulous tuning is required to minimize system jitter and maximize audio thread responsiveness.
Audio Server & Multi-Card Certification
PipeWire is chosen for its modern architecture and security benefits, but its configuration is non-trivial for live performance:
- PipeWire Focus: The goal is validated multi-card reliability. We must ensure multiple USB audio interfaces can operate simultaneously without clock drift or X-runs, a common point of failure for legacy systems.
- Legacy Bypass: We are configuring PipeWire to operate with the lowest possible buffer sizes and maximum thread priority, bypassing the limitations of older audio servers like JACK/PulseAudio which often fail under heavy DSP load.
Headless Mixer Core (LV2 Host)
We use the LV2 Host strictly as a processing engine, not a graphical application:
- Control via OSC: All control signals (faders, sends, mutes) are exclusively handled via Open Sound Control (OSC) commands sent over the network. This eliminates the CPU load associated with rendering a complex GUI.
- Resource Dedication: By running the LV2 Host in headless mode, the CPU dedicates maximum resources to DSP (plugin processing and mixing stability), which is critical for maintaining the sub-5 ms RTL target.
Product Benefits for the Professional Audio Niche
OLMS is designed to empower every player in the live sound ecosystem.
Benefits for Service Providers & Sound Engineers
- Guaranteed Stability: The Core-Level Failover system ensures ZERO audible glitches and guaranteed uptime under load, addressing the critical vulnerability of PC-based systems.
- Unlimited Headroom: The DSP Farm architecture enables virtually unlimited processing power for complex productions (heavy reverb, advanced processing) without sacrificing the Master's critical sub-5 ms latency guarantee.
- Cost & Logistics Efficiency: Allows transformation of common, affordable PC hardware into dedicated, certified rack mixers, reducing dependency on expensive proprietary hardware.
Benefits for Musicians & End Users
- Professional Accessibility: Provides access to a professional-grade mixing core (LV2 Host orchestrated) with a lower barrier to entry.
- Total Wireless Control: Full control via a Web Browser User Interface (HTML5/JS) over OSC, enabling control from any Wi-Fi connected tablet or smartphone.
- Ecosystem of Certified Features: Access to deeply integrated, proprietary, and certified premium functionalities via the Marketplace, such as the Anti-Feedback System (AFS) or Virtual Sound Check Suite.
Benefits for Plugin Developers
- Curated Marketplace Access: Opportunity to sell proprietary, high-value plugins through the "Certified and Curated" Marketplace.
- RT Stability Validation: Sales are based on guaranteed RT Stability and Latency Certification, providing a strong competitive advantage over generic software solutions.
- Code Protection: Proprietary UI/Audio modules can be dynamically injected into the GPLv3 GUI slots without modifying the core open source code.
Monetization and Future Growth (The Open Core Model)
OLMS adopts a Hybrid Open Core model, balancing the critical need for community contribution (GPLv3) with a clear path towards commercial sustainability (Proprietary).
| Component | License | Role & Monetization |
|---|---|---|
| The Open Source Core | GPLv3. | Includes the OLMS Distro, the RT Kernel, PipeWire, the LV2 Host Headless configuration, the Web Control Interface (GUI), and the OSC Bridge Server. |
| Monetization | Proprietary. | Monetization focuses on additional plugins and services sold through a Certified and Curated Marketplace. The competitive advantage for sales is based on guaranteed RT Stability and Latency Certification (objective < 5 ms round-trip, ZERO X-runs in 1 hour). |
The Proprietary Marketplace & Certified Value
The monetization strategy is managed by the Project Owner and focuses on the proprietary ecosystem. The proprietary barrier is built on Advanced Logic Modules that extend the GPLv3 OLMS Orchestrator Daemon, ensuring that features like the Anti-Feedback System (AFS) and Live Auto-Mixer are implemented as proprietary extensions to the Orchestrator's core.
Proprietary Plugins (Functionality Examples):
- Anti-Feedback System (AFS).
- Live Auto-Mixer (Advanced dynamic algorithm for vocal/drum mixing).
- Virtual Sound Check & Calibration Suite (Tools for acquisition, virtual soundcheck looping, and RTA location analysis).
- Advanced Wireless Security & Diagnostic Pack (Real-time Wi-Fi network monitoring and advanced PipeWire (PW) and RT Kernel diagnostics).
- Multi-Fader OSC Controller Extension (Advanced routing and personalization functionalities for network control).
The Founding Team Incentive:
Should the project reach the commercial phase, the 4 Leads/Supervisors will be given absolute priority for an offer of a paid role, a supply contract, or an equity stake in the commercial company, recognizing their fundamental role in the launch of the GPL Core.
The Leaders Team (The Founding 5)
Our core structure requires five Founders. The Project Manager is establishing the technical vision, and your mission is to help recruit the remaining three technical leaders to fulfill the Proof-of-Concept tasks.
Project Owner
Project Manager, Technical Vision, Sound Engineer: the project's origin
Francesco Nano brings over 15 years of experience in audio engineering and education. Since 2009, he has been the owner of scuolasuono.it, an online sound engineering course. His formal training includes studies at the Accademia del Cinema di Bologna and the Scuola di Alto Perfezionamento in Saluzzo. After a 20-year pause, Francesco recently returned to live sound engineering, transitioning from analog mixers to digital solutions like the UI24R. His hands-on experience with DAWs revealed critical limitations in current live mixing technology, inspiring the creation of OLMS. As an active live sound engineer for a band, Francesco serves as the project's primary user and field tester.
Filled
Developer Relations
DevRel Specialist / Community Leader
Will lead the talent hunt to select and onboard the three highly-skilled technical Supervisors (Architect, UX/UI, Full-Stack Developer). Will define the Core Team's skill matrix and create high-quality public content (Technical Manifesto, Blog Posts, Applied Thesis Case Studies) to attract contributors and validate the project's vision.
Technical Architect
Lead Architect / Core Maintainer
Will be responsible for configuring and validating the Monolithic RT Core with core-level redundancy and a failover mechanism. The objective is to guarantee ZERO X-runs in one hour of stress testing and a Round-Trip Latency of less than `5 ms` (with a tolerance of `10 ms` for the initial PoC), managing the routing `1 Input → LV2 Host → 1 Output` remotely controlled via PoC-2.
UX/UI Designer
Lead UX/UI
Will create a static HTML/CSS page of a Master Fader, completely responsive and optimized for touch devices.
Full-Stack Developer
Lead Developer (Control)
Will develop a functional Bridge Server and JS/OSC integration to connect the PoC-1 Fader to Ardour's Master Fader, demonstrating immediate movement and control.
(All initial Leadership positions are non-monetary, grant permanent Founder status, and guarantee absolute priority for involvement in the future commercial phase.)
The MVP Task: "The Core Fader"
The objective is to redefine the initial Proof of Concept (PoC) of the OLMS project into a Minimum Value Product (MVP) called "The Core Fader". This is a strategic step aimed at validating the system’s core value before proceeding with the development of more complex features.
The MVP focuses on proving Real-Time stability combined with the fundamental user experience.
Primary Objectives
"The Core Fader" must demonstrate the system's feasibility through three key and interconnected outcomes:
- Real-Time Stability Validation: We must achieve the critical goal of ZERO (0) X-runs in one hour of stress testing, confirming that the system is capable of sustaining reliable live audio load.
- Ultra-Low Latency Target (RTL): The audio Round-Trip Latency (RTL) must be less than 5 ms, ensuring an immediate and professional response.
- Functional Remote Control: The entire system, consisting of the Real-Time Kernel, PipeWire, and LV2 Headless Host, must route 1 Input→1 Output and its level must be remotely controllable via the OSC protocol.
Essential Components of the Task
To achieve these objectives, the team must focus on the minimum integration of four essential components, all strictly Open Source (GPLv3):
- Audio Core (Architecture): Installation and configuration of a Linux system with a Real-Time Kernel and PipeWire, optimized for 1×1 audio routing through the LV2 Host Headless instance.
- Control Logic: Development of the base logic for the Orchestrator and the OSC Bridge Server, sufficient to translate a fader movement command into an action on the audio channel within the Mixer Core.
- User Interface (UX/UI): Creation of the static HTML/CSS mockup for the Master Fader, ensuring it is responsive and perfectly usable on touch devices like tablets and smartphones.
- Technical Certification: Execution of stress tests to document and certify that the remotely controlled audio maintains the required latency and stability (ZERO X-runs).
The success of this MVP will validate the fundamental model of the digital rack mixer, unlocking the next phase of development and the commercial ambitions of the OLMS project.