Intake
Receive source jobs from SABnzbd or manual operator queues and normalize metadata into one visible task list.
PIPELINE DEEP DIVE
The Vetrra pipeline is designed for operators who want end-to-end visibility across ingestion, encode policy, subtitle handling, OCR, and final deployment. Each stage has explicit responsibilities and explicit failure surfaces.
STAGE MAP
Receive source jobs from SABnzbd or manual operator queues and normalize metadata into one visible task list.
Resolve naming, folder targets, path templates, and title normalization before heavy processing begins.
Inspect streams, validate track layout, and establish the container state that downstream stages inherit.
Apply hardware-aware FFmpeg profiles with operator-visible bitrate, ETA, acceleration, and fallback signaling.
Extract, validate, and classify subtitle streams, including language flags and forced-track rules.
Reassemble validated media tracks into the final container with explicit operator review surfaces.
Use local Ollama vision models to parse poster text and keep media artwork classified with the rest of the library.
Validate final output structure, generate quality reports, and deploy the asset into its target library path.
DEPENDENCY MODEL
Handles encode, stream inspection, and hardware acceleration decisions surfaced directly in the operator UI.
Supports stream topology awareness, mux policy, and container integrity during processing and deployment.
Feeds structured intake into the queue so acquisition and processing remain connected rather than fragmented.
Enable local OCR and poster parsing without shipping library data or artwork to cloud APIs.
The product proof section now frames media inside a faux workspace chrome that matches the application's shell geometry. Poster OCR, gallery handling, and diagnostics sit inside the same system language as the rest of the pipeline.
OPERATOR OUTCOME
Vetrra does not hide complexity. It concentrates it into one interface so the operator can see where a job lives, which external dependency is active, what acceleration path is engaged, and why a final file is or is not ready to deploy.