Render Timing Benchmarks
Expected Render Times
Section titled “Expected Render Times”Onset Engine’s render times depend heavily on the selected visual style preset, the output resolution, and the active render quality (Draft vs. High).
The following table provides approximate relative render times per minute of output. Note: Actual times will vary based on hardware.
| Preset / Mode | 720p (Draft) | 1080p | 4K |
|---|---|---|---|
| Draft Mode (FFmpeg Concat) | Fastest (< 30s) | N/A (Forced 720p) | N/A |
| RAW / STANDARD | ~1x baseline | ~2x baseline | ~6x baseline |
| AGGRESSIVE / AMV | ~1.5x baseline | ~3x baseline | ~8x baseline |
| PRESTIGE / TRAILER | ~2x baseline | ~5x baseline | ~12x baseline |
Factors Affecting Render Speed
Section titled “Factors Affecting Render Speed”Several variables in the editor.py pipeline directly impact how quickly your video finishes rendering:
CPU Cores
Section titled “CPU Cores”The rendering pipeline relies heavily on the moviepy library, which is CPU-bound. Operations like frame extraction, scaling, and compositing utilize multiple CPU cores. A modern CPU with 8+ cores will significantly accelerate STANDARD and PRESTIGE renders.
GPU Hardware Acceleration (Encoding)
Section titled “GPU Hardware Acceleration (Encoding)”Onset Engine utilizes encoder_utils.py to check for hardware encoders.
- NVIDIA: Uses
h264_nvencwith CUDA acceleration. - AMD: Uses
h264_amffor hardware encoding.
Note: GPU acceleration is used for the final H.264 video encoding step, but the frame-by-frame visual effects processing remains CPU-bound.
VFX Complexity
Section titled “VFX Complexity”The style_preset chosen dictates the complexity of per-frame operations:
- Lightweight:
RAWapplies no color grading and relies solely on hard cuts. - Moderate:
STANDARDapplies subtle zooms, transitions, and minor color adjustments. - Expensive:
PRESTIGEandTRAILERutilize intensive processing, such as:- MiDaS Depth Parallax and focus breathing (AI depth estimation).
- Heavy color grading (e.g.,
teal_and_orangeorwarm_film). - Luma-matte transitions and speed ramps.
- Cutout Pop Transitions: Enabling this setting triggers
rembgbackground removal on every transition, drastically increasing render time.
Smooth Motion (60fps Interpolation)
Section titled “Smooth Motion (60fps Interpolation)”If Smooth Motion is enabled, Onset Engine performs a post-render pass to double the framerate (e.g., 30fps to 60fps) using optical-flow motion-compensated interpolation. This can add significant overhead, often doubling the total render time.
Tips for Faster Renders
Section titled “Tips for Faster Renders”- Use Draft Mode: Draft mode bypasses the heavy
moviepypipeline and uses a pureffmpegconcatenation approach. It is extremely fast and skips all VFX, making it perfect for reviewing beat-sync pacing before a final master render. - Lower Output Resolution: If 4K is not required, 1080p will render up to 3x faster while retaining excellent quality.
- Choose Simpler Presets: Opt for
RAWorSTANDARDinstead ofPRESTIGEif you don’t need cinematic depth parallax or heavy color grading. - Disable Expensive Extras: Uncheck “Cutout Pop Transitions” and “Smooth Motion” in the GUI to save massive amounts of processing time.
Hardware Recommendations
Section titled “Hardware Recommendations”Onset Engine gracefully scales based on available hardware, but performance thrives on better specs:
- Minimum Specs:
- Memory: 8GB RAM minimum.
- CPU: Quad-core processor.
- Note: If VRAM is below 6GB, Onset Engine enforces a 1080p safety cap to prevent out-of-memory crashes during NVENC encoding.
- Recommended Specs:
- Memory: 16GB+ RAM.
- CPU: 8-core processor or higher.
- GPU: Dedicated NVIDIA GPU (for
NVENC) or AMD GPU (forAMF) to accelerate the final encoding step.