Migrating from SPBokeh 1.0.0
SPBokeh retains persistent parameter IDs so earlier project values and keyframes can map to the updated controls. However, some visible names and panel positions changed, and rendering improvements can change the look of an older shot.
Renamed parameters
| SPBokeh 1.0.0 | Current name |
|---|---|
| Focus Depth | Focus Distance |
| Depth Range | Focus Range |
| Depth Feather | Focus Falloff |
| Occlusion Strength | BG Exclude |
Earlier development builds may also have used names such as Depth Transition, Blur Falloff, or Background Exclude. Search the current parameter reference under the updated name.
Why an older project may look different
Some newer controls have different defaults in new instances than in a project that predates them. SPBokeh supplies compatibility values when an older project doesn't contain those controls:
| Parameter | Compatibility value for older projects without the control | New-instance default |
|---|---|---|
| Swirl Transition | 0 | 0.25 |
| Edge Feather | 0.25 | 0.10 |
| Foreground Blur | Off | On |
| Opacity Fade | 0 | 0.10 |
| Defocus Blend | 0 | 1 |
| Falloff Curve | Smooth | Smooth |
Existing saved values take precedence. Edge, foreground, color, and rendering fixes can still change pixels even when values and keyframes are restored correctly.
Check expressions and scripts
Expressions that reference a control by its display name may need the new name; check expressions that use a numeric property index against the current host property order. Numeric expression indices are not the same as SPBokeh's internal persistent parameter IDs.
For important work, keep a copy of the older project, open it in the updated release, and compare key shots at the intended render resolution. Pay particular attention to subject edges, foreground overlap, and animated focus changes.