Export and Render Queue

Oraphim's current beta exposes delivery through focused Export and Render Queue panels rather than a permanent bottom workspace. Export defines what should be rendered; Render Queue owns execution, progress, cancellation, persistence, logging, and the FFmpeg-backed encode path.

Choose the resource first

Export can target exportable project resources such as timelines and compositions, plus supported timeline-backed audio/color resources. Confirm the resource before choosing a codec. A correct preset applied to the wrong timeline is still a wrong deliverable.

Final export resolves the original source media, not a lower-resolution playback proxy. Proxy media is deliberately a performance optimization rather than a mastering source.

Current delivery families

Oraphim's verified beta paths include:

• H.264 in MP4 or MOV for common review, web, and social delivery.
• HEVC 10-bit in supported MP4/MOV configurations when the required capability is available.
• ProRes 422 HQ MOV for high-quality 10-bit 4:2:2 masters.
• ProRes 4444 MOV when an alpha-preserving master is required.
• DNxHR HQX MOV and MXF DNxHR HQX professional delivery paths.
• PNG, OpenEXR, DPX 10-bit, and TIFF 16-bit RGBA image-sequence workflows.
• WAV PCM for audio-only delivery.

See Export formats for the format-by-format reference and Professional master workflow for finishing-oriented examples.

Queue and verify a job

1. Open Export and confirm the intended source resource.
2. Choose the closest delivery preset, then verify frame size, frame rate, range, quality, audio, alpha, or HDR requirements that matter for the job.
3. Choose a writable output location and a filename that identifies the version.
4. Add the configured job to Render Queue.
5. In Render Queue, inspect the source, destination, and format before starting the encode.
6. Start rendering and watch the queue state rather than assuming the application is idle.
7. Open the completed file or image sequence and inspect the actual deliverable.

Hardware encoding is capability-probed rather than guaranteed on every machine. Where supported by the installed GPU/driver path, Oraphim can select NVIDIA NVENC, Intel Quick Sync, or AMD AMF; otherwise use the available software path. Treat hardware availability as a machine capability, not as a property of the project file.

Example: review file versus finishing master

For a client review, an H.264 preset close to the requested resolution is usually the efficient starting point. Render a short test, verify picture and audio, then deliver the full file.

For a finishing master, decide what the next system requires before choosing a format. A ProRes 422 HQ or DNxHR HQX master is different from an alpha-bearing ProRes 4444 file, and both are different from an OpenEXR/DPX/TIFF image-sequence handoff. If transparency is required, verify it in the resulting file rather than assuming an RGBA-capable format was configured correctly.

A completed progress bar is not the final quality check. Review frame range, resolution, frame rate, audio, color, transparency, and visible artifacts in the actual rendered output.