Ooloi exists for specific reasons. These goals describe the constraints that shape the system’s architecture and implementation.
Quality Without Licensing Constraints
Ooloi is designed to produce professional engraving output without dependence on proprietary licensing.
This is addressed architecturally rather than commercially: deterministic layout, backend-authoritative rendering, and explicit separation between core functionality and extensions.
Open Source as a Preservation Mechanism
Music notation software is part of long-term cultural infrastructure. Scores may need to remain accessible for decades.
Open-source licensing ensures continued access to both the software and its file formats independent of any single vendor, organisation, or business model.
Extension Without Core Compromise
Ooloi separates its core from specialised functionality.
A plugin architecture allows domain-specific, experimental, or niche features to be developed independently, without delaying or destabilising the core system. This includes alternative notation systems, research tools, playback engines, and import/export formats.
Lessons Incorporated from Igor Engraver
Igor Engraver failed for non-technical reasons, including externally imposed feature expansion that compromised architectural focus.
Ooloi addresses this structurally. The core is deliberately narrow. Extension happens at the periphery. The system does not require feature accumulation in order to remain viable.
Technical Constraints
Certain technical choices are treated as non-negotiable because they enable required capabilities:
These choices exist to support musical work, not as ends in themselves.
Complexity as a First-Class Case
Large orchestral scores, contemporary notation, and non-standard pitch or rhythmic systems are not treated as edge cases.
The system is designed so that simple music remains simple, while complex music remains representable without special modes or exceptions.
Evaluation Criterion
Ooloi is successful only if the system itself demonstrates these properties in use. Goals are not guarantees. They are validated – or invalidated – by execution.
Quality Without Licensing Constraints
Ooloi is designed to produce professional engraving output without dependence on proprietary licensing.
This is addressed architecturally rather than commercially: deterministic layout, backend-authoritative rendering, and explicit separation between core functionality and extensions.
Open Source as a Preservation Mechanism
Music notation software is part of long-term cultural infrastructure. Scores may need to remain accessible for decades.
Open-source licensing ensures continued access to both the software and its file formats independent of any single vendor, organisation, or business model.
Extension Without Core Compromise
Ooloi separates its core from specialised functionality.
A plugin architecture allows domain-specific, experimental, or niche features to be developed independently, without delaying or destabilising the core system. This includes alternative notation systems, research tools, playback engines, and import/export formats.
Lessons Incorporated from Igor Engraver
Igor Engraver failed for non-technical reasons, including externally imposed feature expansion that compromised architectural focus.
Ooloi addresses this structurally. The core is deliberately narrow. Extension happens at the periphery. The system does not require feature accumulation in order to remain viable.
Technical Constraints
Certain technical choices are treated as non-negotiable because they enable required capabilities:
- Multi-threaded computation — large scores must remain responsive
- GPU-accelerated rendering — interaction must scale with visual complexity
- Cross-platform execution — macOS, Windows, and Linux are supported equally
These choices exist to support musical work, not as ends in themselves.
Complexity as a First-Class Case
Large orchestral scores, contemporary notation, and non-standard pitch or rhythmic systems are not treated as edge cases.
The system is designed so that simple music remains simple, while complex music remains representable without special modes or exceptions.
Evaluation Criterion
Ooloi is successful only if the system itself demonstrates these properties in use. Goals are not guarantees. They are validated – or invalidated – by execution.