People like you don't get enough credit. You don't have to do anything for the community your are busy and have a dream job but you still give back and that is great! I sincerely thank you!
i echo triplej96 sentiments, thanks for even attempting to help us
Hahahaha, you guys are crazy. Your welcome, but I'm just like everyone else, maybe a little lazier than most, who got a few lucky breaks and took them.
what compositing software do you use at work? I"m guessing AE sometimes but do you use NUKE or FUSION too? I've only used AE thus far but I hear a lot of vfx houses you node base compositors.
It depends on where I'm working. I use whatever the shop uses. At the first place I worked at, we used AE, and that's what I learned on, so it's my favorite. At Cafe FX, we used Fusion, at R&H, we use our own proprietary software called Icy, and sometimes we use Shake for certain things. In the Other Software thread here at SImplyCG, I made a post with collected screenshots of proprietary software, so if you go look there, you can see screenshots of old Icy and the current Icy.
Yes, alot of places use node based things, because visually, it's easier to see your project as a whole. When you pre-comp in AE, it's hides things from you. People don't like that, even though every node based program has a way of "collapsing" a node, which while not exactly like pre-comping, does hide a portion of your project from you like pre-comping does. No one complains about this, they think it's a good feature. It's a little biased that hiding portions of your project gets praised in one program and derided in another. Ah well... I am ranting. Anyway, if you plan on getting into the field, I'd advise learning at least one node program as well, doesn't matter which, it's easy to adapt. But nodes and layers do require a bit different approach, even though they are doing exactly the same things, just showing you the info in a different way. The most important thing is to learn techniques. For example, lightwrap - if you understand what lightwrap is, and how to make it from scratch, you should be able to do it pretty easily in either layers or nodes.
have u had a chance to peep under the hood and try and figure how i can get trackerViz to stick that shape to the attach point instead of the feature region?
I tested what you said, and yep, it did the same thing for me, made the mask points at the feature center, not the attach point. I'll add it to the list of things to fix for v.2. I myself can barely only script a wiggle expression, so unfortunately, I can't go into the script and fix it. But tomorrow I will jot it down on the official list. Thanks for finding it!!
As a workaround, if you use solids instead of trackers, you should be ok. Because when you apply the track data to a solid first, it uses the attach point. Then just set TrackerViz to Layers instead of Trackers, choose Layers to Shape, and it will work as you want it to.
Hope that helps!
also when dealing with a difficult roto job ( major camera movement, blended colors etc.,) do u have any tips u or any of our fellow compositors live by??
Yes, but if I told you'd, I'd endanger my job.
Just kidding! I do, but maybe this isn't the thread to do it in. Roto tips would get long, and I suppose this thread should stay a bit focused on TrackerViz. But if you have any problem areas or questions, start a thread somewhere here, and maybe even throw up a few screengrabs of what you think would be a tricky area, and let's get into it!
holy long post, batman!