1973bad86c
The final image produced by the compositor can have domain translation on it (e.g. caused by a Translate or Transform node). Similar to how the regular compositor viewer node remembers the output domain translation, do the same in the compositor modifier. Bubble back that translation up to VSE rendering code, where it is then added to regular strip transform. In order to make this "bubble up" part easier, refactored modifiers so that instead of soup of parameters they all get a struct ModifierApplyContext with all the relevant data. Added a new VSE render test that covers various compositor transformation nodes (translate, rotate, transform, corner pin). Pull Request: https://projects.blender.org/blender/blender/pulls/147695
4 lines
130 B
Plaintext
4 lines
130 B
Plaintext
version https://git-lfs.github.com/spec/v1
|
|
oid sha256:dccdb936dccaa6e659f9a46d576ed866a8cbb159dd3eb5d3eb81b4d3b5b76d5c
|
|
size 88705
|