Revision 0d37f82 by Sergey Sharybin July 16, 2012, 10:50 (GMT) |
Color management: support of configurable input color space This adds a user-defined input color space name for image and movie clip data blocks. Support for this thing for other data blocks is still a TODO. Input color space is being used on loading file to convert loaded image buffer from this space to scene linear space, later this space is never used in a pipeline. Color space name was wrapped into own structure like it's done for display and view settings. This helps keep code de-duplicated in RNA and it'll help when likely more options are added into input color space settings (i.e. flag whether image could be color managed or it's a non-color data). This implied quite of internal refactoring: - Made routines around threaded display buffer calculation more general, so any kind of color transform could be performed using the same technique. - Added function to convert given float buffer from given input color space to output color space. This is a public function which could be used in such a things as compositor node. - Added function to convert ImBuf's content to scene linear space. Currently used only for images and clips. Should be added to any image/movie-related data blocks such as sequencer strips, but that a bit more long-term plan. - If input color space is set to NONE then no buffer transform would be performed on image loading. It'll behave in the same way as using scene linear as input space. |
Revision 5a033ca by Sergey Sharybin July 16, 2012, 10:50 (GMT) |
Color management: cleanup of ocio config file - Minor style cleanup - Made scene linear space rec709 instead of aces Reference space is still aces - Get rid of hardcoded rec -. rec709 transformation on view transforms This would make view transform be applied on a reference color space how it's supposed to be. Since scene linear is rec709 such a hardcoded transform isn't needed anymore. This also fixes wrong Log view transform which used to look really weird and now it's nice and smooth. - Also made changes to SPI and Nuke configurations to make them behave properly with reference space of aces. - Renamed Nuke's rec709 space to nuke_rec709. Probably it could be replaced with scene rec709, but that's requires more investigation. |
Revision 9a385d1 by Campbell Barton July 16, 2012, 10:36 (GMT) |
add 2d version of interp_weights_poly_v3 |
Revision 407347f by Campbell Barton July 16, 2012, 09:41 (GMT) |
mask fill/cyclic toggle wasnt refreshing compo nodes |
Revision a2e2489 by Campbell Barton July 16, 2012, 08:53 (GMT) |
correct own naming error BLI -> BKE |
Revision 284d942 by Campbell Barton July 16, 2012, 08:48 (GMT) |
svn merge ^/trunk/blender -r48937:48953 |
Revision 4cacff2 by Campbell Barton July 16, 2012, 08:42 (GMT) |
fix for linking with scons. |
Revision 5b04685 by Campbell Barton July 16, 2012, 08:26 (GMT) |
handy cmake list macros for inserting items into a list before/after existing items |
Revision 60cfbae by Campbell Barton July 16, 2012, 07:23 (GMT) |
mask blending modes: lighten/darken/multiply/replace |
Revision 8e7aa50 by Campbell Barton July 16, 2012, 07:04 (GMT) |
fix crash for empty or single vertex layers. |
Revision 6f01b0b by Campbell Barton July 16, 2012, 06:39 (GMT) |
small speedup for mask rasterizer, only do single sided check for triangle intersection. |
Revision 4f6cc9a by Mitchell Stokes July 16, 2012, 03:43 (GMT) |
BGE: The Action Actuator now returns correct values to work with the Actuator Sensor. |
Revision 9d2a957 by Tamito Kajiyama July 15, 2012, 22:30 (GMT) |
Sphere radius and Kr derivative epsilon (removed in revision 43902) were recovered in the Parameter Editor mode. Several users requested the recovery as the removal of the two parameters was considered over-simplification for advanced users. As in the Python Scripting mode, the two parameters are in the "advanced edge detection options" section and disabled by default. Also the lower limit of Kr derivative epsilon was changed from 0 to -1000 so as to permit a negative value. |
Revision 8c77b35 by Campbell Barton July 15, 2012, 16:57 (GMT) |
Revision 701a16c by Campbell Barton July 15, 2012, 16:16 (GMT) |
moving mask rasterizer file, this breaks building, will fix next commit |
Revision 1723d51 by Campbell Barton July 15, 2012, 15:11 (GMT) |
replace fminf with minf |
Revision b67b73e by Bastien Montagne July 15, 2012, 12:53 (GMT) |
"Fix" [#32033] In the execution result of with_automatic_weight, the difference is seen right and left. This auto/heat vgroup creation seems to be fuzzy/unstable (each run gives a slightly different result). I have not the competences (nor time) to investigate that laplacian stuff, so for now just adding an option when parenting to an armature with envelope/heat, to mirror weights along the X axis (as it is done by default when doing it from the Weight Paint mode). |
Revision 380c5d6 by Campbell Barton July 15, 2012, 11:35 (GMT) |
math function to get the intersection point between 2 lines (not 2 segments which we already have). |
Revision 474b922 by Campbell Barton July 15, 2012, 11:33 (GMT) |
fix: node background image move operator didn't take zoom into account when clamping pan bounds. |
Revision 0c087e5 by Sergey Sharybin July 15, 2012, 10:51 (GMT) |
|
|
|


Master Commits
MiikaHweb | 2003-2021