Ordinis — Home

Ordinis Media Engine · inside Ordinis Player

Our own engine, under the picture.

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.

Read
Ordinis’s own readers open Matroska, WebM, MP4 and MOV files and split them into packets.
Decode
Your system’s decoders do the heavy lifting: Media Foundation on Windows, dav1d and libopus on Linux.
Sync
An audio-driven clock schedules every frame, so picture and sound stay together.
Present
Frames are drawn straight into the Ordinis Player window.

Who it’s for

An engine you use without noticing

OME is not a separate app. It works inside Ordinis Player, behind the same controls, library and settings.

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.

Built to be safe with any file

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.

Ordinis owns the pipeline

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

From a file to the picture

Separate stages with bounded queues between them. When you seek, every queue is flushed and stale packets are dropped.

Readers

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.

Decoders

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.

Clock and sync

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.

Presentation

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.

A colour-bar test picture with a moving diagonal band and a checkerboard, frame 100 at 4 seconds, as drawn by OME.
Frame 100 of an H.264 test file: decoded by Windows’ own decoder, timed and drawn by OME, with the exact colours of the reference.

Proof, not promises

Checked against the reference, file by file

Results from our November 2026 test runs, on test files made for each case.

26/26Files read identicallyEvery packet of 15 Matroska/WebM and 11 MP4-family test files matched a reference reader: size, timing, keyframes and content. One fragmented-MP4 difference is declared and explained.
2.8 MDamaged files, no crashMutation fuzzing of the Matroska and MP4 readers: 2.8 million generated files, 0 crashes and 0 hangs.
2,500/2,500Frames bit-identicalPictures decoded through OME on Windows were byte-for-byte identical to the reference decode, on five test files.
0.13 msWorst picture–sound gapH.264 with AAC on Windows, measured on a flash-and-beep sync test: no drift, no dropped frames.
132/135H.264 conformance streamsParsed from the official ITU-T test set; the three left out use a feature OME reports as unsupported.
17,707Slice headers identicalEvery slice header of those streams equal to a reference parser, field by field.

Privacy and security

Safe by design

A player opens files from anywhere. OME is built so that a bad file is refused, not run.

Memory-safe code

Written in Rust, with unsafe code limited to the thin layers that talk to the operating system.

Every reader fuzzed

Each file reader is tested with millions of mutated files, and every crash ever found is kept as a regression test.

Limits before memory

Sizes and counts in a file are checked before anything is allocated, so a file that claims millions of entries is refused at once.

Your files stay local

OME plays files on your computer. It sends nothing anywhere.

No DRM circumvention

Encrypted tracks are shown as encrypted and never decrypted.

Licensed decoders first

Formats such as H.264, HEVC and AAC are decoded by the operating system’s own decoders.

Platforms

Platforms and requirements

Windows
Windows 10 and 11, 64-bit, inside Ordinis Player (Settings › Playback). Windows N editions need Microsoft’s Media Feature Pack.
Linux
64-bit Linux, including Ordinis OS: AV1 video with dav1d and Opus audio with libopus
Containers
Matroska, WebM, MP4, MOV, M4A and fragmented MP4
Video
Windows: H.264, HEVC (with Windows’ HEVC extension), AV1, VP9 · Linux: AV1
Audio
Windows: AAC, MP3, AC-3, E-AC-3, FLAC · Linux: Opus
Language
Rust, with a C interface for the Player

Files OME does not cover are played by the VLC engine in Ordinis Player.

Part of the family

How it works with the other Ordinis products

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

What’s new

  • In Ordinis Player · OME can be chosen as the engine in Ordinis Player 2.3.5 and later on Windows, with automatic fallback to the VLC engine.
  • Linux picture · OME draws into its own window inside the Player on Linux, tested with AV1 and Opus.
  • H.264 parser · Checked against the official ITU-T conformance streams.
  • Windows decoding · Media Foundation video and audio decoding, with bit-exact output.
  • First playback · Picture and sound in sync on Windows and Linux test files.

Questions

Does OME replace the VLC engine in Ordinis Player?
Not by default. Ordinis Player still plays with the VLC engine unless you choose OME in Settings › Playback on Windows. A file OME cannot play yet is played by the VLC engine instead.
Is OME a separate app?
No. It works inside Ordinis Player.
Why Rust?
Reading media files safely is the hardest part of a player. Rust is memory-safe by default, and its built-in testing and fuzzing tools fit that job.
Does OME use FFmpeg?
OME’s file readers are its own, and decoding uses your operating system’s decoders, or dav1d and libopus on Linux. FFmpeg serves in our tests as the reference OME is compared with.
Can it play protected streaming content?
No. Encrypted tracks are recognised as encrypted and are never decrypted.
Which formats does it play?
Matroska, WebM and MP4-family files with the codecs listed under Platforms. Everything else in Ordinis Player is played by the VLC engine.

Support us

Support Ordinis

Ordinis is independent. If an app helps you, you can support its development.

Support us

Payments are handled securely by Stripe.