June 11, 2021, 14:27 (GMT) |
Fix T89033: segfault reordering animation channels Fix segmentation fault that can occur when reordering animation channels. Under some specific conditions, the list "act->curves" is empty in the "join_groups_action_temp" function. In particular, this happens when a scene contains an action that has not been pushed down, and with no keyframe in it. Reviewed By: sybren Differential Revision: https://developer.blender.org/D11569 |
Revision 605ce62 by Jacques Lucke June 11, 2021, 14:21 (GMT) |
Nodes: cache socket identifier to index mapping While this preprocessing does take some time upfront, it avoids longer lookup later on, especially as nodes get more sockets. It's probably possible to make this more efficient in some cases but this is good enough for now. |
Revision 7b30a3e by Jeroen Bakker June 11, 2021, 13:55 (GMT) |
Performance: Use parallel range for ImBuf scanline processor. Scanline processor did its own heurestic what didn't scale well when having a multiple cores. In stead of using our own code this patch will leave it to TBB to determine how to split the scanlines over the available threads. Performance of the IMB_transform before this change was 0.002123s, with this change 0.001601s. This change increases performance in other areas as well including color management conversions. Reviewed By: zeddb Differential Revision: https://developer.blender.org/D11578 |
Revision 7b76a16 by Jeroen Bakker June 11, 2021, 13:51 (GMT) |
Sequencer: Do not redraw during playback. When using large sequences including audio the drawing of the audio on top of the strip takes a lot of time. This effects the playback performance heavily. During the animation playback performance there was a solution for this by only drawing the playhead overlay. This was reverted for the sequence editor as it didn't update the color strips when they were animated. This patch checks if there are animated color strips if so the full screen is redrawn, otherwise only the playhead is redrawn. Reviewed By: ISS Differential Revision: https://developer.blender.org/D11580 |
Revision 0eb9351 by Germano Cavalcante June 11, 2021, 13:49 (GMT) |
Refactor: use 'BLI_task_parallel_range' in Draw Cache One drawback to trying to predict the number of threads that will be used in the `task_graph` is that we are only sure of the number when the threads are running. Using `BLI_task_parallel_range` allows the driver to choose the best thread distribution through `parallel_reduce`. The benefit is most evident on hardware with fewer cores. This is the result on an 4-core laptop: ||before:|after: |---|---|---| |large_mesh_editing:|Average: 5.203638 FPS|Average: 5.398925 FPS ||rdata 15ms iter 43ms (frame 193ms)|rdata 14ms iter 36ms (frame 187ms) Differential Revision: https://developer.blender.org/D11558 |
Revision 2330cec by Germano Cavalcante June 11, 2021, 13:45 (GMT) |
Refactor: Draw Cache: use 'BLI_task_parallel_range' This is an adaptation of {D11488}. A disadvantage of manually setting the iter ranges per thread is that we don't know how many threads are running in the background and so we don't know how to best distribute the ranges. To solve this limitation we can use `parallel_reduce` and thus let the driver choose the best distribution of ranges among the threads. This proved to be especially beneficial for computers with few cores. **Benchmarking:** Here's the result on an 4-core laptop: ||master:|PATCH: |---|---|---| |large_mesh_editing:|Average: 5.203638 FPS|Average: 5.398925 FPS ||rdata 15ms iter 43ms (frame 193ms)|rdata 14ms iter 36ms (frame 187ms) Here's the result on an 8-core PC: ||master:|PATCH: |---|---|---| |large_mesh_editing:|Average: 15.267482 FPS|Average: 15.906881 FPS ||rdata 9ms iter 28ms (frame 65ms)|rdata 9ms iter 25ms (frame 63ms) |large_mesh_editing_ledge: |Average: 15.145966 FPS|Average: 15.520474 FPS ||rdata 9ms iter 29ms (frame 65ms)|rdata 9ms iter 25ms (frame 64ms) |looptris_test:|Average: 4.001917 FPS|Average: 4.061105 FPS ||rdata 12ms iter 90ms (frame 236ms)|rdata 12ms iter 87ms (frame 230ms) |subdiv_mesh_cage_and_final:|Average: 1.917769 FPS|Average: 1.971790 FPS ||rdata 7ms iter 37ms (frame 261ms)|rdata 7ms iter 31ms (frame 258ms) ||rdata 7ms iter 38ms (frame 252ms)|rdata 7ms iter 33ms (frame 249ms) |subdiv_mesh_final_only:|Average: 6.387240 FPS|Average: 6.591251 FPS ||rdata 3ms iter 25ms (frame 151ms)|rdata 3ms iter 16ms (frame 145ms) |subdiv_mesh_final_only_ledge:|Average: 6.247393 FPS|Average: 6.596024 FPS ||rdata 3ms iter 26ms (frame 158ms)|rdata 3ms iter 16ms (frame 148ms) **Notes:** - The improvement can only be noticed if all extracts are multithreaded. - This patch touches different areas of the code, so it can be split into another patch if the idea is accepted. These screenshots show how threads behave in a quadcore: Master: {F10164664} Patch: {F10164666} Differential Revision: https://developer.blender.org/D11558 |
Revision fe22635 by Jacques Lucke June 11, 2021, 12:55 (GMT) |
Nodes: add utilities to check if there are undefined nodes/sockets |
Revision c0367b1 by Sebastian Parborg June 11, 2021, 12:05 (GMT) |
Fix: VSE search in mpegts files would fail ffmpeg_generic_seek_workaround did work properly and our start pts calculation was wrong. Reviewed By: Richard Antalik Differential Revision: https://developer.blender.org/D11562 |
Revision 4adbe31 by Sebastian Parborg June 11, 2021, 12:04 (GMT) |
Fix: VSE indexer seeking not working correctly Because of the added sanity checks in rB14508ef100c9 (D11492), seeking in proxies would not work correctly any more. This is because it wasn't working as intended before, but in most cases this wouldn't be noticeable. However now when the sanity checks are tripped it is very noticeable that something is wrong The indexer tried to use dts values for time stamps when we used pts in our decode functions to get the time positions. This would make it start in the wrong GOP frames when searching. Now that we enforce no crossing of GOP frames when decoding after seek, this would lead to issues. Now we correctly use pts (or dts if pts is not available) and thus we don't have any seeking issues because of time stamp format missmatch. Reviewed By: Richard Antalik Differential Revision: https://developer.blender.org/D11561 |
Revision 1fb2eaf by Sebastian Parborg June 11, 2021, 12:04 (GMT) |
Fix: VSE timecodes being used even when turned off. Reviewed By: Richard Antalik Differential Revision: https://developer.blender.org/D11567 |
June 11, 2021, 09:55 (GMT) |
LineArt: Fix crash due to empty duplicollection. |
Revision e9c8ae76 by Jeroen Bakker June 11, 2021, 09:37 (GMT) |
Performance: Split ImBuf sampling. When sampling ImBuf can be a char or a float buffer. Current sampling functions added overhead by checking which kind of buffer was passed every pixel that was sampled. When performing image processing this check can be removed outside the inner loop adding 5% of performance increase in the `IMB_transform` operator. |
June 11, 2021, 09:13 (GMT) |
Fix T88068: Alt+I now respects keying set Remap {key Alt I} from `anim.delete_key_v3d` to `anim.delete_key`. This makes it keyframe removal symmetrical with keyframe insertion ({key I}). Both the default keymap {key Alt I} and the Industry Compatible keymap {key Alt S} have been updated. Reviewed By: sybren, #animation_rigging Maniphest Tasks: T88068 Differential Revision: https://developer.blender.org/D11528 |
Revision 28617bb by Jeroen Bakker June 11, 2021, 07:34 (GMT) |
Sequencer: Transform ImBuf Processor. Inside the sequencer the cropping and transform of images/buffers were implemented locally. This reduced the optimizations that a compiler could do and added confusing code styles. This patch adds `IMB_transform` to reduce the confusion and increases compiler optimizations as more code can be inlined and we can keep track of indices inside the inner loop. This increases end-user performance by 30% when playing back aa video in VSE. Reviewed By: ISS, zeddb Differential Revision: https://developer.blender.org/D11549 |
Revision 84f025c by Campbell Barton June 11, 2021, 06:27 (GMT) |
Cleanup: use sentences for pose slide comments |
June 11, 2021, 05:53 (GMT) |
June 11, 2021, 05:40 (GMT) |
Cleanup: pose slider use enum types use enum types in `tPoseSlideOp` instead of `short` Reviewed By: sybren, campbellbarton Ref D11364 |
June 11, 2021, 05:38 (GMT) |
Cleanup: pose slider use strncpy use `STRNCPY` instead of `BLI_strncpy` Reviewed By: sybren, campbellbarton Ref D11363 |
June 11, 2021, 05:36 (GMT) |
Cleanup: pose slider data types - change vec2f to float[2] - pass rctf as pointer - change `const struct rctf` to `const rctf` |
June 11, 2021, 05:29 (GMT) |
Cleanup: pose slider rename "percentage" to "factor" This patch changes occurrences of percentage to factor. There are some usages of percentage left in there on purpose. They are distinguished as follows: - factor is 0-1 float - percentage is 0-100 int Ref D11361 Reviewed by: sybren, campbellbarton |
|