Render quality, performance & color
SPBokeh can process frames on the GPU or CPU and offers several quality levels. These controls matter most when previewing large footage, rendering a long sequence, or working with a color-managed project.
Render Quality
| Setting | Use it for |
|---|---|
| Preview | Responsive editing and checking the basic composition. |
| Balanced | A middle ground between detail and processing cost. |
| Final | Higher sampling budget and full internal background working resolution relative to the frame delivered by the host. |
| Auto | Let SPBokeh select a level based on the render context and resolution. New instances use Auto. |
Auto isn't always a fast preview. It measures the resolution the host delivers against the full frame size:
| Resolution delivered | Auto selects |
|---|---|
| 99% or more | Final |
| Above 26%, below 99% | Balanced |
| 26% or less | Preview |
In After Effects, Half and Third preview resolution therefore use Balanced, while Quarter or a custom resolution of 25% uses Preview. Headless render-engine work (aerender, AME, watch folders, jobs without a viewer) always uses Final, whatever the resolution. Premiere Pro has no equivalent signal: an export at full resolution uses Final, and playback follows the same thresholds. If the host reports no usable scale, Auto treats it as full resolution.
Processing Device
Auto (GPU preferred) tries Metal on macOS or D3D12 on Windows and can fall back to CPU when the GPU cannot process a frame. GPU (Metal) or GPU (D3D12) requires the GPU path; it does not silently switch to CPU if that path fails. CPU explicitly uses CPU rendering.
A GPU failure is more likely to come from availability, image dimensions, or resources than from the optical settings. The GPU bridge checks for texture dimensions beyond 16,384 pixels on either side, and practical memory limits may be lower. Use Info > About... to inspect the device and recent Auto behavior where available.
Color Processing
SPBokeh accumulates bokeh in linear light internally. Color Processing tells the plugin how to interpret RGB values coming from the host:
- Automatic (AE): Uses available host color-space and transfer information. In After Effects, it can recognize several transfer curves; when that information isn't available it falls back by pixel depth. Premiere Pro's detection depends on its rendering entry point and pixel format.
- Gamma-Encoded: Treats incoming RGB as sRGB-encoded values.
- Linear: Treats incoming RGB as already linear.
If highlights look unexpectedly dark or bright in an established linear workflow, check the host's actual delivered format and consider selecting Linear explicitly. Some native Premiere Pro floating-point GPU paths are interpreted as sRGB under Automatic because they do not carry an explicit linear-format marker.
Technical details
| Quality | Internal strategy | Sample budget | Background working resolution |
|---|---|---|---|
| Preview | Fast | 800 | Automatic |
| Balanced | Optimized | 1,500 | Automatic |
| Final | Reference | 5,500 | Full relative to the host-delivered frame |
These are sampling budgets, not a fixed number of samples for every pixel. Actual processing varies with bokeh size, depth, quality, source resolution, and backend. At Preview and Balanced the background working resolution is chosen automatically and can drop to half or a quarter; Final always works at full resolution relative to the frame the host delivers. In After Effects, Info > About... shows the level the last render used as long as the instance stays on Auto.