Adam Wilder
Forum Replies Created
-
Instead of throw, have you tired other behaviors to see if they give you more control? For example, you could do the ken burns effect in a 2D combining the Move, Grow/Shrink, and Fade In/Fade out behaviors. You could do it in a 3D comp with just Move and Fade In/Fade out. If one tool isn’t working for you, another (or another combination) might actually work better.
-
If you want something more rhythmic, you could use the Oscillate behavior applied to the text opacity.
-
First, nice piece of work. Here are a few things I would suggest, please forgive if you’ve already tried some of these.
Shadows
Turn of shadow casting for items that don’t need to cast shadows (like the ground).
If you can get away with it, use the Uniform Shadows when possible.Depth of Field
Go with the Gaussian Blur over the defocus
When the first cards move to the background, trim any layers that you can. If you’re still rendering all your text but it’s getting blurred beyond recognition, why do it. You could also try to switch to baked versions of the cards once they move to the back.As the others have stated, bake everything you can. I’d start with the timelines below the video clips. Good luck.
-
I don’t think this is a codec problem. What’s most likely happening is that your subject is crossing this pole fairly quickly and what you’re seeing is the result of the blending created by the Optical Flow algorithm. For example, take a look at this clip showing the results of optical flow.
https://www.metacafe.com/watch/1270539/super_slow_motion_optical_flow_retiming/
There are two areas where I think you’ll see the type of artifact you are describing. The first is at about 52 seconds. Look at the arm. The second is at about 1 minute, when the frisbee crosses over the logo on the t shirt. In both cases you have significant changes between a short number of frames, and now you’re trying to blend and stretch the data.
Lets say that in real time, there are 3 frames for the frisbee to cross the logo on the shirt. Frame 1, before it crosses, Frame 2, covering the logo, and frame 3. When you slow that down 25%. you’re now generating 12 frames and only three of those are “real” the rest are interpolated and since you don’t have a lot transition information (example: 2 more frame where the frisbee partially covers the logo) in those areas you sometimes get these artifacts. Optical flow is working correctly with the information it has.
The only way you could maybe minimize the results would be to use a different speed, faster or slower (oddly enough sometime slower fixes the problem). You could also try duplicating the clip, use a different frame blending and mask it over the optical flow clip.
-
Why not just use the Basic 3D filter in the Distortion section? While still faking 3D it allows you to control XYZ/HBP rotation. It also allows for you to add a back face input.
-
As specialcase pointed out, you do need to use a codec such as Animation that supports an alpha. Unfortunately, even when you select HDV 1080i codec, Motion will still give you the impression in the export summary box that it will export the file as a Millions+ file (RGBA). HDV does not support an embedded alpha. As a side note, if you’re working with any format that ends in DV, it’s almost always a better idea to export in a lossless codec. DV/HDV are more lossy than a lot of users realize, and you don’t want to crush all your data until you have to.
-
You need to make sure you’ve selected a codec that supports alpha channels. If you are using the export option in Motion, when the save dialog comes up, go to the export preset option and select Lossless+Alpha.
Peter
-
Johan,
Hate to say it, but 5.1 is the update. I’ve known a lot of people who are fighting it buying the upgrade, but the cost to get the Universal version is so small, it’s worth shelling out the cash for the features you might be be missing.
Peter
-
Looks like they’ve fixed it. For those of you who are not familiar with Nodal Compositing, they’ve also updated with some examples of uses for Conduit.
-
I to have been having problems with motion crashes. I’ve tracked it down to using my previewing on a NTSC monitor. As long as I don’t apple-tab to another application, it seems to be fine. Last night, after a short render, I woke up to find Motion locked-up. The worst part of this problem is that the usual option to send a crash report is unavailable because you have to force-quit to get working again. Anyone have any suggestions on the best way to get feedback to Apple on this? I can replicate it every time, so it must be a bug.