March 8, 2021, 14:47 (GMT) |
Merge branch 'master' into temp-gpencil-io |
March 8, 2021, 14:46 (GMT) |
Merge branch 'master' into greasepencil-object |
Revision 8defd9d by Jeroen Bakker (compositor-cryptomatte-workflow, temp-compositor-cryptomatte-picker) March 8, 2021, 14:03 (GMT) |
Cryptomatte read layer names from session. |
March 8, 2021, 13:14 (GMT) |
Fix Cycles CUDA build error with Visual Studio 2019 v16.9 Something in this update broke the floor() function in CUDA, instead use floorf() like we do everywhere else in the kernel code. Thanks to Ray Molenkamp for identifying the solution. |
March 8, 2021, 13:05 (GMT) |
Fix Cycles CUDA build error with Visual Studio 2019 v16.9 Something in this update broke the floor() function in CUDA, instead use floorf() like we do everywhere else in the kernel code. Thanks to Ray Molenkamp for identifying the solution. |
Revision 950c536 by Jeroen Bakker (compositor-cryptomatte-workflow, temp-compositor-cryptomatte-picker) March 8, 2021, 12:49 (GMT) |
Merge branch 'master' into compositor-cryptomatte-workflow |
March 8, 2021, 12:08 (GMT) |
VSE: Automatic proxy building Add `Proxy Setup` enum to user preferences with 3 choices: Manual, For Added strips and Automatic. With `For Added strips` Only build proxies when adding movie strips. With `Automatic` setting, proxies are built when preview size changes as well. TODO: - Decide what to do when workspace has multiple previews with different preview sizes. See `seq_get_preview_size()` - Solution may be to change current design to allow only one size or just build multiple sizes. Additional possible improvements: - Cancel running job if preview size is changed while building proxies - Use proxy of different size while building proxies for new size. it would be best to do after some refactoring, so in separate patch. ref T85469 Maniphest Tasks: T85469 Differential Revision: https://developer.blender.org/D10363 |
March 8, 2021, 11:47 (GMT) |
VSE: Simplify proxy settings - Remove Full Render size from VSE preview size. Use just 100% instead - Add Use Proxies checkbox to control whether proxies are used globally - Move preview size to top so it is most prominent - Set default to 100% preview size and use proxies (could be separate patch as well) Design task: T85469 {F9735445} No change has been done to individual strip setting as users may need to turn proxies on/off individually. I think it would be best if size selection will be managed when automatic proxy building is enabled. In that case proxy panel can be simplified a lot. This is probalby better to leave for separate patch Maniphest Tasks: T85469 Differential Revision: https://developer.blender.org/D10362 |
March 8, 2021, 10:18 (GMT) |
[WIP] Use H264 codec for proxies Same patch as D10394, but using H264 codec with small GOP size (2 frames in this case). Main reason to use H264 is smaller filesize, current patch produces about 3x smaller files. Playback is also about 1.5x faster than MJPEG Complexity of this patch is much higher though, because encoder must work in own threadpool and encode frames with own gop size. This means that scaled frames from encoder must be allocated per packet, which leads to worse performance overall. Patch is still about 3x faster than original. Interesting thing is that there is no performance improvement when running transcoding in more than 4 threads. Possible ways to improve performance are to reuse memory for packets and frames, which would require redesign, where threads would wait for data to be written. Another possibly much cleaner method would be to decode portions of input into multiple streams and remux these into proxy file. In both cases managing complexity would be fairly important as it can get out of hand quite quickly. Maniphest Tasks: T85469 Differential Revision: https://developer.blender.org/D10630 |
March 8, 2021, 00:57 (GMT) |
Merging latest USD import changes. |
Revision 42bf732 by Michael Kowalski (temp-usd-importer-T81257-merge, usd, usd-importer-T81257-merge) March 7, 2021, 20:10 (GMT) |
USD Import: Convert to Z Up option. Added a Convert to Z Up import option and logic to rotate imported root objects 90 degrees about the X-axis if this option is checked and the USD stage up-axis is Y. |
March 7, 2021, 20:02 (GMT) |
apply changes from code review branch |
March 7, 2021, 19:21 (GMT) |
Fix compile errors |
March 7, 2021, 17:06 (GMT) |
Merge branch 'master' into sculpt-dev |
March 7, 2021, 16:50 (GMT) |
GHOST: Vulkan: Fix compilation error |
March 7, 2021, 16:36 (GMT) |
Merge branch 'master' into cycles_procedural_api |
March 7, 2021, 16:28 (GMT) |
Merge branch 'master' into tmp-vulkan |
March 7, 2021, 16:22 (GMT) |
Merge branch 'master' into tmp-vulkan # Conflicts: # source/blender/blenkernel/BKE_global.h # source/blender/gpu/intern/gpu_context.cc # source/blender/windowmanager/intern/wm_window.c # source/creator/creator_args.c |
March 7, 2021, 14:34 (GMT) |
Merge branch 'master' into cycles_procedural_api |
March 7, 2021, 12:40 (GMT) |
XR: Move actions from keymaps to actionmaps Previously, properties for XR actions were stored in keymaps but they are now stored in a separate XR "actionmaps" system. Although the actionmap system/API has many similarities to the keymaps, it is significantly less complex since it does not involve any diff-ing of default/addon/user configurations (at least at the moment). Another big distinction between keymaps and actionmaps is that actionmaps and properties are saved to blend files. This allows users to set up a VR scene with actions and properties and share working versions with others, without the need to import/export config files. However, actionmap import/export is also supported via the addon. There is still a fair amount of refactoring left to do but at least this commit removes XR involvement from the keymaps while preserving most of the existing XR action functionality (i.e. default actions and user-configurable actions). |
|
|
|


Master Commits
MiikaHweb | 2003-2021