June 7, 2021, 14:58 (GMT) |
FFmpeg: Fix H264 lossless render not lossless While encoder parameters for lossless encoding are set correctly, output is not lossless due to pixel format being set to `AV_PIX_FMT_YUV420P` which is inherently lossy due to chroma subsampling. This was reported in T61569 and was merged to T57397, but there were 2 bugs - one for encoding and one for decoding. Set pixel format to `AV_PIX_FMT_YUV444P` when rendering lossless H264 files. This format isn't available in `codec->pix_fmts[0]` and it looks, that it has to be hard-coded. Reviewed By: sergey Differential Revision: D11458 |
June 7, 2021, 14:58 (GMT) |
Cleanup: Fix build warnings |
June 7, 2021, 14:58 (GMT) |
Cleanup: make format |
June 7, 2021, 14:58 (GMT) |
GHOST/wayland: set swap interval to 0 The Wayland server will not update hidden surfaces. This will block the main event loop and thus also block updates to visible windows in a multi- window setup. |
June 7, 2021, 14:58 (GMT) |
GHOST/wayland: handle return values for data sources |
June 7, 2021, 14:58 (GMT) |
Boolean exact: speedup by parallelizing a plane calculation. This patch is from erik85, who says: This patch makes populate_plane inside polymesh_from_trimesh_with_dissolve run in parallel. On a test file with a boolean between two subdivided cubes (~6 million verts) this gives a 10% speed increase (49.5s to 45s) on my 6 core CPU. Also there is an optimization of other_tri_if_manifold to skip the contains-call and get the pointer directly. This reduces CPU time for find_patches from 5s to 2.2s on the same test file. |
June 7, 2021, 14:58 (GMT) |
WM: only use the tablet drag threshold for mouse button events Keyboard click-drag events now use the "Drag Threshold". This resolves a problem where keyboard click drag events used a much smaller threshold when using a tablet. |
June 7, 2021, 14:58 (GMT) |
June 7, 2021, 14:58 (GMT) |
Cleanup: use doxy sections for node_relationships.cc |
June 7, 2021, 14:58 (GMT) |
Fix T88762: UI using tab to enter next button could clamp the hard min/ max unneccessarily Since rB298d5eb66916 [which was needed to update buttons with custom property range functions correctly], using tab would always clamp (hardmin/hardmax) properties which were using FLT_MAX / INT_MAX as range in their property definitions. The clamping of rB298d5eb66916 was copied over from rB9b7f44ceb56c [where it was used for the softmin/softmax], and while the re-evaluation of hardmin/hardmax is needed for custom property range functions, the clamping should actually not take place. There are many properties using FLT_MAX / INT_MAX etc. and while it probably would be good to update these with ranges that make more sense -- not using FLT_MAX / INT_MAX would not have done the clamping here -- there should not be an arbitrary limit to these and they should stay as they are. Maniphest Tasks: T88762 Differential Revision: https://developer.blender.org/D11473 |
June 7, 2021, 14:58 (GMT) |
cmake: use absolute path for Wayland libraries |
June 7, 2021, 14:58 (GMT) |
VSE: Add strip-time intersection test function Use SEQ_time_strip_intersects_frame function to test if strip intersects with frame. Note: There are cases where this function should not be used. For example splitting strips require at least 1 frame "inside" strip. Another example is drawing, where playhead technically doesn't intersect strip, but it is rendered, because current frame has "duration" or "thickness" of 1 frame. Reviewed By: sergey Differential Revision: https://developer.blender.org/D11320 |
June 7, 2021, 14:58 (GMT) |
GHOST/wayland: fix non-moving normal cursor |
June 7, 2021, 14:58 (GMT) |
LibOverride: fix previous commit (rB826bed4349fa). |
June 7, 2021, 14:58 (GMT) |
VSE: Remove JPEG reference from proxy panel Proxies doesn't use MJPEG codec anymore, but text still referenced it. |
June 7, 2021, 14:58 (GMT) |
Fix swapped x/y in event simulation script Incorrect area center calculation, also correct comments. |
June 7, 2021, 14:58 (GMT) |
GPencil: New operator to Normalize strokes Sometimes is required to reset the thickness or the opacity of the strokes. Actually this was done using a modifier, but this operators solves this. Reviewed By: mendio, filedescriptor Maniphest Tasks: T87427 Differential Revision: https://developer.blender.org/D11453 |
June 7, 2021, 14:58 (GMT) |
Revert "EEVEE: AOVs not same as cycles." This reverts commit 730a46e87d261543c9550ddef406894e14d5bea6. |
June 7, 2021, 14:58 (GMT) |
EEVEE: AOVs not same as cycles. EEVEE uses hashing to sync aov names and types with the gpu. For the type a hashed value was overridden making `decalA` and `decalB` choose the same hash. This patches fixes this by removing the most significant bit. |
June 7, 2021, 14:58 (GMT) |
EEVEE: AOVs not same as cycles. EEVEE uses hashing to sync aov names and types with the gpu. For the type a hashed value was overridden making `decalA` and `decalB` choose the same hash. This patches fixes this by removing the most significant bit. |
|