Page MenuHome

Improvements to "Setup Scene" in the MovieClipEditor
Needs RevisionPublic

Authored by Sebastian Koenig (sebastian_k) on Sep 6 2014, 10:55 PM.

Details

Summary

There are 3 changes here:

  1. Enable sky/environment in the foregroundlayer:

In Blender Internal it wouldn't matter because the sky wouldn't be rendered anyway because of the premultiplied alpha. In cycles that makes sure objects can be illuminated by world color or texture

  1. Set AO to 0.05 if using Cycles.

Ambient Occlusion in Blender Internal will only make things darker, hence strength can be 1. An AO value of 1 in Cycles however would light up the scene way too much. A value of 0.05 adds a resonable hint of light which can help to eliminate noise. If the user doesn't want that he'd have to disable AO anyway.

  1. Change the size of the cube in foreground layer to dimensions of (1,1,1), which is a better starting value for most test scenes, and also move the mesh up 1 Blender Unit so that the cube sits on the ground. That makes reviewing the tracking scene easier. Besides, the lower part of the default cube would be cut off by the background plane anyway.

Diff Detail

Event Timeline

Sebastian Koenig (sebastian_k) retitled this revision from to Improvements to "Setup Scene" in the MovieClipEditor.
Sebastian Koenig (sebastian_k) updated this object.
Sebastian Koenig (sebastian_k) updated this object.
Sebastian Koenig (sebastian_k) updated this object.

Looks good to me, but I am not especially qualified to answer here. Sergey?

Also nice work on hacking the code :)

release/scripts/startup/bl_operators/clip.py
463

Should be a 4-space indent. Maybe you are accidentally using hard tabs?

This revision is now accepted and ready to land.Sep 6 2014, 11:02 PM
release/scripts/startup/bl_operators/clip.py
463

Oh indeed. Thanks! Now I only have to find out how to edit the patch.... But that's for tomorrow. :)

Sebastian Koenig (sebastian_k) edited edge metadata.

Fixed the issue with spaces.

First part has been already committed using the patch @Sebastian Koenig (sebastian_k) published in IRC. With second part i don't agree, most of the time you run this operator with the default scene, where the cube is 2x2x2. In that case there'll be no extra sample object created. And it'll be crappy to have different looking result when using default and empty scenes as a base point.

Sergey Sharybin (sergey) requested changes to this revision.Jan 19 2015, 1:03 PM

So either we consider patch applied (since the sky is fixed since ages now) and close it or someone need to look into more general-purpose auto-setup which would work just fine when running from default scene.

This revision now requires changes to proceed.Jan 19 2015, 1:03 PM

Would deleting the default cube (if at 0,0,0 and 2x2x2) and replacing with new, adjusted cube be better?

Would still be weird but at least more consistent.

Also, instead of deleting/creating it you can change it's verts positions:

for v in meshes.vertices:
    v.co /= 2.0
    v.co[2] += 0.5

would be a bit different for edit mode, but that you'd better ask cambo about.

This has grown stale; Sebastian, want to update this and get it landed?