View Full Version : Rotoscope and stereo question

04-02-2012, 10:41 PM
I have a curiosity

For the people wich are working on rotoscope for stereo conversion, what's the rythm of work for doing all that mask and rotoscope stuff?

4 frames per day?
8 frames per day?
1 second ( 24 frames ) per day ?
More than 5 seconds per day?

wich tools is the more advanced actually in this area?

NUKE ( http://youtu.be/qDy3Y2HC2Is )
FUSION ( http://youtu.be/YMB0wgt_pv4 )
COMBUSTION ( http://youtu.be/RlU9XwWJpQk )
AFTER EFFECTS Rotobrush ( http://youtu.be/L2_KFA4LkSA )
AFTER EFFECTS Mocha ( http://youtu.be/_X5fPr1A2mE )
BLENDER Roto bezier ( http://youtu.be/FvMYn0z4Wvs )
SilhouetteFX ( http://youtu.be/jSD2eJOprh8 )
Shake ( http://youtu.be/WOVtCYh9wEg )


04-03-2012, 12:15 AM
We used Silhouette, basically because it has python scripting.

Mocha is very attractive because of its superior planar tracker, but we were getting Silhouette to auto populate and auto ingest into the pipeline via python.

Nuke's roto was appalling for what we needed.

As for the work itself - it depends on the shot.
Wispy hair, any kind of organic shapes, motion blur will slow you down to a crawl, but trackable solid shapes can make it easier.

Roughly 1 shot per day (30 -60 frames) though tough shots 3-4 days.
I was in charge of the pipeline setup for roto at Gener8 in Vancouver.
We did Narnia, Harry Potter, Priest3d, GhostRider2

04-03-2012, 02:48 AM
Just to add:

I would count in blender _only_ if you are used to the interface, Also essential features are missing, like individual mask blurring. (At least when I used it for that : 2.4x times).
Not sure about the rotobezier concept itself, I did hoped they would extend the old hooks on curve points (=Nulls on each point controling curve points) workflow a bit more , since I do think it provides far better flexibility, and in general a better workflow than shapekeys, especially if you want to focus on the motion of a few points / Manipulate the individual keyframes of each point.

AE + Mocha, not my favorite, but imho a good bang for bucks ratio.

04-03-2012, 06:50 PM
Thanks Tranimatronic and tischbein3 fro sharing info.

Nice to hear that python scripts automates a bit more the process.

Blender is a bit far, but it's also nice to know they are worried with all the fx process.