shifathosn
/
filmcraft
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

NEST11: the architecture doc says a plain nest's layers go into the frame plan 

docs/architecture.md still listed every nested sequence among the things
rendered on the CPU and handed to the GPU as one image. Since NEST11 that
holds only for nests that are not plain.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
justjohn12345 2026-10-06 20:53:53 -04:00
parent e13151d87b
commit 1ebc1440e7
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/architecture.md
View File

@ -265,7 +265,9 @@ file ──► codecs (MP4/MOV, MKV, audio) demux + decode, GOP-aware see
working image at the size the CPU decodes it, each effect runs as compute passes with the CPU
reference's math (effects, then Motion, then Opacity / blend, as on the CPU), and the result is
placed like any layer. Other standard effects, effect and opacity masks, adjustment layers,
nested sequences and non-dissolve transitions are rendered on the CPU for that layer or frame
nested sequences (except a plain one, whose own layers go into the plan: same frame size and
colour settings as its parent, nothing on the clip that changes the picture, every layer inside
blended normally) and non-dissolve transitions are rendered on the CPU for that layer or frame
and handed to the GPU as an image (a layer image keeps its clip's blend mode), so both paths
give the same picture. Setting `FILMCRAFT_CPU_COMPOSITE=1`
forces the CPU path in the desktop app.