TROUBLESHOOTING

Find the failing stage, then find the failing dependency.

The fastest way to debug Vetrra is to treat the pipeline as a sequence of explicit domains. Determine which stage failed, inspect the corresponding dependency, and confirm whether the issue is local configuration, policy, or source-media quality.

Missing FFmpeg or MKVToolNix

If encode or mux stages fail immediately, confirm the binaries are installed, available on the path, and callable by the desktop application context.

Acceleration is not active

If a job unexpectedly falls back to CPU, validate the GPU driver state, the chosen encoder flags, and whether the source format matches the configured acceleration path.

OCR is slow or missing

Poster OCR depends on a local Ollama vision model. Confirm the model exists, fits the host’s inference capacity, and can be reached by the configured runtime.

Deploy output is wrong

Inspect the organize stage rules first. Deployment problems are often upstream naming, path, or metadata mismatches rather than a final-stage copy problem.

Beta 2 reminder

The product is still in active refinement. Treat diagnostics as a feature surface, keep notes on reproducible failures, and expect the interface and documentation to evolve together.