Blender Git Commits

replacing step function

Fix for scons files missing physics include folder.

Replace region tracker with autotracker in Blender

The title actually tells it all, this commit switches
Blender to use new autotrack API from Libmv.

From the user point of view it means that prediction
model is now used when tracking which gives really
nice results.

All the other changes are not really visible for users,
those are just frame accessors, caches and so for the
new API.

Major refactor of Libmv C-API

Basically the idea is to split it into smaller pieces,
because current file became unmanageable.

This commit also includes implementation of all C-API
for the autotrack pipeline.

Pretty much straightforward changes, nothing to be
mentioned specially.

Initial commit of unfinished AutoTrack API

This starts the creating the new AutoTrack API. The new API will
make it possible for libmv to do full autotracking, including
predictive tracking and also support multiple motion models (3D
planes etc).

The first goal (not in this patch) is to convert Blender to use
the new API without adding any new functionality.

This API currently contanins:

- Frame accessor to access frames which are stored in Blender side.
- New Tracks implementation
- New Reconstruction implementation

Currently this API only tested on doing the same frame-to-frame
tracking as the old API allowed to do. But it also supports now
predictive tracking which is based on the Kalman filter.

Yet another attempt to solve OSX issues, restore sequence sounds too, or
sounds get added to two sequence and file descriptors leak

Revert "Merge branch 'terrible_consequencer' into testbuild"

This reverts commit 18c6c0146627b006ff094e0eb0050f81cdf2a379, reversing
changes made to 5d9396c0a41873dff0fe438eaeb21744e13025c1.

Merge branch 'terrible_consequencer' into testbuild

Added separate damping for bending springs.

The bend damping factor was hardcoded to the same value as the stiffness.
Now it has its own factor in the settings and button in hair dynamics.

Cycles; Camera ray nodes initial commit

This commit lays down an initial playground for the camera ray nodes.

The idea of this nodes is to be able to have a control over the rays
which are being casted from the camera in order to gain several use
case scenarios:

- Panorama cameras with custom mapping (kinda generalized way doing
what Daniel Basso tried to address in T35428).

- Distortion rendering, to produce renders which matches the footage
precisely, improving motrack work flow in general.

- Some possible artistic scenarios.

It's the very beginning and loads of stuff to be done, but it's
already possible to render a distorted images on CPU using the same
exact distortion model as used by the motion tracker.

Committing the stuff in order to be able to gather early feedback
about how exactly this nodes are expected to work from the artists
point of view, and hopefully someone will pick the work up and help
finishing it all up.

Some technical details:

- Camera nodes are using pynodes, so no changes to the blender itself
is to be done. This leads some limitations and corners on the usage,
but that's probably something to be addressed for pynodes in general.

That said, current annoyance is:

* Modifying node declaration in the cycles addon doesn't update the
files, leading to wrong render results. Not sure how it's expected
to be handled actually.

* Some operators like Ctrl-X are not re-linking noodles correctly.

* Muting is impossible.

* Some major update issues, mainly in cycles viewport. This also
involves dependency graph stupidness into here.

- Nodes are implemented using SVM, which is really easy to use and
extend. Would also make it possible to have custom socket types, for
example in SVM we can have socket type named "Ray" which would pass
all the origin, direction length via a single noodle.

In OSL it's not so trivial by the looks of it, so for now we stick
to a stupid regular socket types.

- Supporting OSL could be a rather tricky business via pynodes and
could involve quite some work in here. Also it'll stress OSL with
something it wasn't really designed to do, but it might just work.

- Since inverting the distortion is an optimization problem which is
rather tricky to implement on GPU, only CPU supports camera ray
nodes at this moment.

- The above thing might be solved if we bake distortion into a grid
and use as a lookup table from the kernel. Would also help performance
by avoiding solving optimization problem for each single camera ray
at each sample.

- Some stuff might be totally broken at this moment, use with care
and don't forget to back your files up before doing experiments.

Real quick example: ftp://ftp.blender.org/sergey/camera_nodes.blend.png

Minor corrections to the types

New data types for sequencer.

Uses struct hierarchies to reduce the data used per strip.

Also changed sequence -> strip. Might be better to use NSequence for
editing as well.

Merge branch 'master' into terrible_consequencer

Set the length threshold for hair simulation to 10% again (from 1%).

With the default 5 substeps the simulation can otherwise still become
unstable. This is just a preliminary measure anyway until the length
variance can be fixed properly.

Fix for outdated root array size when changing the particle amount
during simulation.

Fix for hair chain testing in the cloth modifier.

Bending springs are en-bloc and not interleaved with other springs, so
this can't be used as a test for hair roots. Use consecutive indices
instead.

Completed the implementation of bent rest shapes for hair.

Basically follows the Pixar approach from "Artistic Simulation of Curly
Hair".

Gooseberry request: Backdrop for sequencer.

Fix for crashes on release build when rendering, big kudos for Lukas Toenne

Merge remote-tracking branch 'origin/master' into multiview

Conflicts:
release/datafiles/locale
source/blender/blenloader/intern/versioning_270.c