For Ordinis Player users
On Windows, choose it in Settings › Playback. Anything it cannot play yet is played by the VLC engine instead, without you doing anything.
Ordinis Media Engine · inside Ordinis Player
The Ordinis Media Engine (OME) is the playback engine Ordinis is building for Ordinis Player. It is written in Rust, reads your files with its own code, decodes them with the decoders already in your operating system and keeps picture and sound in step.
Who it’s for
OME is not a separate app. It works inside Ordinis Player, behind the same controls, library and settings.
On Windows, choose it in Settings › Playback. Anything it cannot play yet is played by the VLC engine instead, without you doing anything.
Media files are the main way into a player. OME’s readers are written in a memory-safe language and tested with millions of damaged files.
Reading, timing, sync and presentation are Ordinis code. Third-party code is used only as codecs or operating-system services, below a clear interface.
Under the hood
Separate stages with bounded queues between them. When you seek, every queue is flushed and stale packets are dropped.
Ordinis-written readers for Matroska and WebM, and for MP4, MOV, M4A and fragmented MP4. They report tracks, durations and timestamps, and find the right keyframe when you seek.
Chosen at run time from what your computer offers. Windows: Media Foundation for H.264, HEVC (with Windows’ HEVC extension), AV1 and VP9 video and AAC, MP3, AC-3, E-AC-3 and FLAC audio. Linux: dav1d for AV1 and libopus for Opus. Hardware decoders are detected through VA-API and Direct3D 11.
Sound drives the clock; each picture is shown when it is due. Audio that belongs before the start of a file or a seek target is trimmed to the exact sample.
Frames are converted and drawn into the Player’s own window on Windows and on Linux.
The Player talks to OME through a small, stable interface: open, play, pause, seek, volume, tracks. The VLC engine sits behind the same interface, so the Player can use either one.

Proof, not promises
Results from our November 2026 test runs, on test files made for each case.
Privacy and security
A player opens files from anywhere. OME is built so that a bad file is refused, not run.
Written in Rust, with unsafe code limited to the thin layers that talk to the operating system.
Each file reader is tested with millions of mutated files, and every crash ever found is kept as a regression test.
Sizes and counts in a file are checked before anything is allocated, so a file that claims millions of entries is refused at once.
OME plays files on your computer. It sends nothing anywhere.
Encrypted tracks are shown as encrypted and never decrypted.
Formats such as H.264, HEVC and AAC are decoded by the operating system’s own decoders.
Platforms
Files OME does not cover are played by the VLC engine in Ordinis Player.
Part of the family
OME lives inside Ordinis Player and plays your local files when you choose it in Settings › Playback. The library, controls and Aura stay the same.
On Ordinis OS, OME uses the open-source dav1d and libopus decoders and detects the computer’s hardware decoders.
Recent milestones
Support us
Ordinis is independent. If an app helps you, you can support its development.
Support usPayments are handled securely by Stripe.