Blender Git Loki

Merge branch 'master' into compositor-cryptomatte-workflow

enable view2d buttons keymap

This mainly activates the page up/down keys.

GPencil: Apply object scale to thickness

The thickness must be multiplied by object scale.

initial support for rows for selected vertices

Start of Cylinder node, add distance float socket

Merge branch 'master' into temp-gpencil-io

Sculpt IPMask: Use the new mask filter in the pie menu

Cycles: avoid updating global memory bounce state for shader evaluation

Cycles: basic support for transparent shadows

Missing still is volume shadows and support for continuing to trace if the
max number of hits is exceeded.

Cleanup: Moved conversion to float to CryptomatteHash.

Cleanup: Introduce CryptomatteHash struct.

Cryptomatte: Lookup name by encoded hash.

use new spreadsheet icon

Merge branch 'master' into temp-spreadsheet-editor

Cleanup: moved cryptomatte manifest functions.

Cryptomatte manifest reader.

With the cryptomatte manifest reader it is possible to construct a
cryptomatte layer from a manifest.

Merge branch 'master' into temp-cryptomatte-manifest-parser

Merge branch 'master' into geometry-nodes-mesh-primitives

Merge branch 'master' into temp-vse-fast-scrubbing

VSE/FFmpeg: Scrubbing performance optimization

Decode only I-frames when scrubbing

This means, that scrubbing is as fast as possible, but not precise.

With some files with extreme GOP lengths, this may be not optimal, as
seeking would jump from one place to another.
Another issue is, that when zoomed in to movie strip, fine scrubbing is
not possible.

Both issues can be resolved by decoding exact frame on second request.
In first case this would cause UI to be laggy. In both cases this may
also cause glitchy behavior.

To eliminate glitchy behavior, there would have to be a buffer where
previous frames are stored and determine if seek has to be precise or
not. This analysis would have to be heuristic ultimately, and it could
significantly increase code complexity.

Also this analysis would be best done from VSE, because with imprecise
seeking, cache needs to be disabled, because image does not correspond
to what should be displayed.
If analysis is done on VSE side, when switching to precise scrubbing,
cache can remain active and scrubbing backwards, which is very likely
can be aided by cache. FFmpeg can't seek backwards efficiently.

Ultimately this patch assumes that files are encoded with fairly short
GOP sizes. If file is not optimal, proxy system is best solution for
achieving best performance.