Blender Git Loki

Cycles: Log number of samples which PathTraceWork will render

Allows to monitor how many samples were scheduler for rendering
between updates.

Cycles: Move denoising call inside of PathTrace::render_samples

Preparation for the pathTrace being responsible for scheduling samples,
denoising, and display updates.

Temporarily alters the render_samples() call.

Should be no functional changes.

Cycles: Rename WorkScheduler to WorkTileScheduler

Makes it explicit which part of rendering work is being scheduled.

Cycles: Move GPUDisplay to PathTrace

The end goal is to have PathTrace to have full control over things like
resolution divider, number of samples scheduled for rendering, picking
the best moment to perform denoising based on an empirical measurements
in order to achieve best responsive interface as well as the best
render times.

This change moves ownership of the GPUDisplay from Session to PAthTrace
so that PathTrace can start using it directly.

Should be no functional changes so far, just preparing code and API
needed for the end goal.

Merge branch 'master' into soc-2020-io-performance

Initial raw liboverride-dedicated view in the Outliner.

Disclaimer: this is merely a copy of the Libraries (aka blend file)
view, with some minor tweaking.

Pose Library: add `POSELIB_OT_apply_pose_asset` operator

Add operator `POSELIB_OT_apply_pose_asset` that does the same as executing
(instead of invoking) `POSELIB_OT_blend_pose_asset` with
`blend_factor=1.0f`. This will replace the Python equivalent in the
pose library add-on.

FFmpeg: improve threading settings

Generalize threading settings in proxy building and use them for encoding
and decoding in general. Check codec capabilities, prefer FF_THREAD_FRAME
threading over FF_THREAD_SLICE and automatic thread count over setting it
explicitly.

ffmpeg-codecs man page suggests that threads option is global and used by
codecs, that supports this option. Form some tests I have done, it seems that

`av_dict_set_int(&codec_opts, "threads", BLI_system_thread_count(), 0)`

has same effect as

```
pCodecCtx->thread_count = BLI_system_thread_count();
pCodecCtx->thread_type = FF_THREAD_FRAME;
```

Looking at `ff_frame_thread_encoder_init()` code, these cases are not
equivalent. It is probably safer to leave threading setup on libavcodec than
setting up each codec threading individually.

From what I have read all over the internet, frame multithreading should be
faster than slice multithreading. Slice multithreading is mainly used for low
latency streaming.

When running Blender with --debug-ffmpeg it complains about
`pCodecCtx->thread_count = BLI_system_thread_count()` that using thread count
above 16 is not recommended. Using too many threads can negatively affect image
quality, but I am not sure if this is the case for decoding as well - see
https://streaminglearningcenter.com/blogs/ffmpeg-command-threads-how-it-affects-quality-and-performance.html
This is fine for proxies but may be undesirable for final renders.

Number of threads is limited by image size, because of size of motion vectors,
so if it is possible let libavcodec determine optimal thread count.

Performance difference:
Proxy building: None
Playback speed: 2x better on 1920x1080 sample h264 file
Scrubbing: Hard to quantify, but it's much more responsive
Rendering speed: None on 1920x1080 sample h264 file, there is improvement with codecs that do support FF_THREAD_FRAME for encoding like MPNG

Reviewed By: sergey

Differential Revision: https://developer.blender.org/D10791

FFMPEG: refactor seeking

Split seeking section of `ffmpeg_fetchibuf()` function into multiple
smaller functions.

Conditional statements are moved to own funtions with human readable
names, so code flow is more clear.

To remove one branch of seeking, first frame is now decoded by
scanning, which will do only one iteration. So nothing has technically
changed.

Reviewed By: sergey

Differential Revision: https://developer.blender.org/D10638

Pose Library: allow blending in flipped poses

Allow a flipped pose asset to be blended into the current pose.

Cleanup: Rename `POSELIB_OT_blend_pose` to `POSELIB_OT_blend_pose_asset`

Rename the pose blending operator to `POSELIB_OT_blend_pose_asset`, so that
we can make an operator `POSELIB_OT_apply_pose_asset` without colliding
with the old `POSELIB_OT_apply_pose` operator (from the current pose
library system instead of the new one).

No functional changes.

LineArt: Remove BINARY_WEIGHTS option.

Revert "Cleanup: Use new utils provided by the asset system to get temp asset IDs"

This reverts commit b0395ba7186c1b0e1aede546b9ce2cfa41f5ffe7.

Merge remote-tracking branch 'origin/master' into asset-browser-poselib

Geometry Nodes: Add Attribute Clamp Node

This adds a Clamp node for Geometry Nodes Attributes.

Supports both Min-Max and Range clamp modes.

Float, Vector, Color and Int data types supported.

Reviewed By: HooglyBoogly, simonthommes

Differential Revision: https://developer.blender.org/D10526

Cleanup: Replaced unneeded branch with assert.

Merge branch 'master' into cycles_procedural_api

Revert "Action: flip action data using pose contents"

This reverts commit d219b09a4802fff37189442de55720da6a03ea78. It was
accidentally committed to this branch, and is superseded by the actual
commits mentioned in D10781#274991

Fix library linking for editors/asset

Add missing libraries to fix a linker error.

Cleanup: redundant expression