Hardware vs. Software Encoding

Encoding a video (compressing it into an H.264 or H.265 file) requires massive mathematical calculations. How Oraphim performs these calculations drastically affects your render times.

In the Render Settings panel (under the Video tab), you will see an Encoder dropdown. The options available depend entirely on the physical hardware inside your computer.

Software Encoding (Native)

If you select Native, Oraphim uses your CPU (Central Processing Unit) to calculate the compression.

• Pros: It produces the absolute highest mathematical quality at very low bitrates. It is highly stable.
• Cons: It is extremely slow. Rendering a 10-minute 4K video using the CPU might take 30 to 40 minutes, depending on your processor.

Hardware Encoding (GPU)

Modern graphics cards (GPUs) contain dedicated microchips physically hardwired to encode H.264 and H.265 video.

Depending on your system, you might see:

• Nvidia NVENC: Appears if you have an Nvidia GeForce or RTX card.
• AMD VCE / AMF: Appears if you have an AMD Radeon card.
• Intel QuickSync: Appears if you have an Intel CPU with integrated graphics.
• Apple Hardware: Appears if you are on a Mac with M-series Silicon (M1/M2/M3).

If you select a hardware encoder, Oraphim offloads the mathematical heavy lifting to the GPU.

• Pros: It is incredibly fast. A 10-minute 4K video that takes 40 minutes on the CPU might render in 2 or 3 minutes using NVENC or Apple Silicon.
• Cons: Historically, hardware encoders were slightly less efficient than CPU encoders (meaning a 10 Mbps hardware file might look slightly more blocky than a 10 Mbps software file). However, modern hardware encoders are now so advanced that the visual difference is virtually imperceptible to the human eye.

Best Practice: Always use Hardware Encoding (NVENC / Apple) for daily drafts and YouTube uploads to save time. Only switch to Native (Software) encoding if you are delivering a master file to a broadcast network with extremely strict, low-bitrate QC requirements.