Codecs & Workflow Integration
Fits your existing workflow.
Support for industry-standard codecs, ingest interfaces, packaging formats, and APIs means Lemonflex integrates cleanly into existing broadcast and media workflows.
Codecs & Workflow Integration at a glance
Standard codecs
H.264, HEVC, AV1. Standards only, no proprietary codec.
Broad ingest
SDI, ST 2110, SRT, RTSP, RTMP, and file input are all accepted.
Standard packaging
HLS, LL-HLS, DASH, and CMAF work with existing players as-is.
API control
REST and gRPC connect to MAM, schedulers, and CI pipelines.
How it works
Three touchpoints with your existing systems.
Upstream
Sources from cameras, switchers, and MAM are normalized on ingest.
Control plane
APIs and webhooks let your orchestration tooling drive the pipeline.
Downstream
Output reaches origin, CDN, and storage in standard formats.
Key specifications
Technical specifications
Complete list of supported formats and interfaces.
- Video codecs
- H.264 · HEVC · AV1
- Profiles
- Baseline – Main 10
- Audio
- AAC · AC-3 · Opus (passthrough)
- Containers
- MP4 · MPEG-TS · fMP4 · MKV
- Bit depth
- 8 / 10-bit
- Baseband
- 3G / 12G-SDI
- Uncompressed IP
- SMPTE ST 2110
- Compressed IP
- SRT · RTSP · RTMP · RIST
- Files
- Local · NFS · S3 · GCS
- Packaging
- HLS · LL-HLS · DASH · CMAF
- Captions & metadata
- CEA-608/708 · WebVTT · SCTE-35
- DRM
- AES-128 · Widevine · FairPlay integration
- API
- REST (OpenAPI 3.1) · gRPC
- SDKs
- Python · Go · Node.js
Frequently asked questions
Anything not covered here, we answer in a technical meeting.
Do you use a proprietary codec?
No. Output is H.264, HEVC, or AV1 — standard codecs only. Playback works without changing players or CDN, and no vendor lock-in is created.
Can it drop into an existing FFmpeg-based pipeline?
Yes. File-based batch workflows can be driven via CLI and API, and replacing only the encoding step in existing scripts is a common adoption path.
Are SCTE-35 markers and captions preserved?
SCTE-35 signals and CEA-608/708 captions pass through, and WebVTT conversion is supported. You can keep your ad insertion workflow intact and replace only the encoding stage.
How do we integrate with MAM or a scheduler?
Through REST and gRPC APIs plus webhooks. Job submission, status queries, and completion notices are exposed as standard interfaces, so your existing orchestration tooling can call them directly.
Your video infrastructure,
one level up.
Start with a single card and scale as needed. We design the demo, the rollout, and the technical review with you.