Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

OxiMedia

Pure Rust Reconstruction of FFmpeg and OpenCV

Details

External ID
47302515
Source
HN
Company
—
Product
OxiMedia
Website domain
github.com
Launched
March 8, 2026
Cohort
—
Upvotes
11
Upvotes percentile
0.6113161131611317
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Author here. OxiMedia is a clean-room reconstruction of FFmpeg and OpenCV in pure Rust. v0.1.0, 92 crates, ~1.36M lines.Key decisions: `#![forbid(unsafe_code)]` workspace-wide, patent-free codecs only (AV1/VP9/Opus/FLAC -- no H.264/H.265/AAC ever), async on Tokio, zero C/Fortran deps in default features, native WASM target.This is v0.1.0 -- APIs are stabilized but not yet battle-tested at scale. Performance benchmarks vs FFmpeg/rav1e/dav1d coming soon.Feedback on API design welcome, especially the filter graph and transcoding pipeline.GitHub: https://github.com/cool-japan/oximedia

Enrichment

Theme
audio and video developer utilities
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
rust implementation of ffmpeg and opencv
Manually corrected
False

Could you build this?

No Rebuilding massive, multi-codec multimedia and computer vision engines like FFmpeg and OpenCV from scratch in pure safe Rust is an enormous systems engineering effort spanning 92 crates and over a million lines of code.

What it would actually take: This requires implementing dozens of complex container formats (MP4, Matroska) and codecs (AV1, VP9, Opus, FLAC) purely in safe Rust without C dependencies, alongside computer vision algorithms and async I/O with Tokio. The hardest parts are bitstream decoding specifications, complex mathematical transforms (DCT, MDCT), motion estimation, and performance optimization without `unsafe`. This demands deep domain expertise in video compression standards, numerical computing, and years of dedicated systems engineering.

Discussion

11 comments analyzed.

Competitors mentioned: Other codec/container libraries (unspecified), System default codecs via other libraries

Concerns raised: Single commit with 2M lines makes codebase evolution hard to evaluate, Possibly AI-generated code with no disclosure of methods or human review, H.264/H.265 codec support missing due to patent concerns, NVENC support claimed but appears to be no-op/non-functional, Code doesn't smell production-ready despite API stability claims

Feature requests: H.264/H.265 support as optional features, Web demo for WASM functionality, Incremental commit history for evaluation

Competitors

Other products that read as similar to this one — 94 launches clear the similarity bar, closest 8 shown.

Attention rank: #49 of 95 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 127 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.