Blender Git Commits

2.66a:
* Back port r54747 to 2.66a tag to fix Windows compile error.

Merging r54848 through r55059 from trunk into soc-2011-tomato

committed 'a' version

svn merge ^/trunk/blender -c54904 -c54936 -c54937 -c55010 -c55011 -c55012 -c55021 -c55027 -c55028 -c55047 -c55048 -c55051

splash screen for 2.66a

svn merge ^/trunk/blender -c55022 -c55026

Compilefix: add 2 forgotten files frm merge

svn merge ^/trunk/blender -c54969 (manual merge because this file was moved)

svn merge ^/trunk/blender -c54929, also added missing header

svn merge ^/trunk/blender -c54733 -c54738 -c54745 -c54746 -c54748 -c54754 -c54757 -c54760 -c54764 -c54766 -c54767 -c54769 -c54772 -c54776 -c54777 -c54780 -c54781 -c54782 -c54783 -c54788 -c54789 -c54790 -c54793 -c54794 -c54799 -c54816 -c54818 -c54822 -c54824 -c54827 -c54828 -c54833 -c54834 -c54835 -c54837 -c54855 -c54856 -c54862 -c54865 -c54866 -c54868 -c54875 -c54877 -c54878 -c54879 -c54882 -c54883 -c54885 -c54891 -c54899 -c54900 -c54901 -c54903 -c54907 -c54908 -c54910 -c54912 -c54917 -c54920 -c54921 -c54923 -c54928 -c54934 -c54935 -c54942 -c54943 -c54944 -c54945 -c54946 -c54948 -c54954 -c54959 -c54960 -c54961 -c54965 -c54971 -c54972 -c54990 -c54991 -c54993 -c54996 -c55004 -c55007 -c55010 -c55011 -c55012

Oh bummer, it's too early for this patch to be in!

Merging r54846 through r54847 from trunk into soc-2011-tomato

Merging r54751 through r54845 from trunk into soc-2011-tomato

Merging r54570 through r54750 from trunk into soc-2011-tomato

Motion tracking dopesheet

Highlight background depending on number of tracks existing on frame.

This is not so much mathematically accurate displaying where things
shall be improved, but it's nice feedback about which frames better
be reviewed.

Bad frames are tracks < 8, highlighted with red.
OK-ish frame are 8 <= tracks < 16, highlighted with yellow.

Could be some artifacts with color region start/end, this is a bit
unclear what exactly expected to be highlighted -- frames are
displayed as dots, but in fact they're quite noticeable segments.

Merging r53628 through r54569 from trunk into soc-2011-tomato

Fixed for keyframe selection

- Calculate residuals for GRIC in pixel space rather than
in normalized space.

This seems to be how it's intended to be used.

Algebraic H and F will still use normalized coordinates which
are more stable, after this matrices are converted to pixel
space and Ceres refinement happens in pixel space.

- Standard deviation calculation was wrong in GRIC. It shouldn't
be deviation of residuals, but as per Torr it should be deviation
of measurement error, which is constant (in our case 0.1)

Not sure if using squared cost function is correct for GRIC,
but cost function is indeed squared and in most papers cost
function is used for GRIC. After some further tests we could
switch GRIC residuals to non-squared distance.

- Bring back rho part of GRIC, in unit tests it doesn't make
sense whether it's enabled or not, lets see how it'll behave
in real-life footage.

- Reduce minimal correspondence to match real-world manually
tracked footage

- Returned back squares to SymmetricEpipolarDistance and
SymmetricGeometricDistance -- this is actually a cost
functions, not distances and they shall be squared.

Merging r53625 through r53627 from trunk into soc-2011-tomato

Merging r53212 through r53624 from trunk into soc-2011-tomato

svn merge ^/trunk/blender -r50999:51100