Steve Roberts
Forum Replies Created
-
Unless ReTimer has been revamped, I’d prefer Twixtor 4.5.
Either may or may not help your footage, depending on the motion in your footage, its direction relarive to camera, how far it moves between frames, and what else is happening in the frame. They operate by interpolating motion between frames, but …
… say you have a rotating spoked wheel where the wheel rotates 180 degrees between frames. Then the wheel would look identical on each frame, so when interpolating, the plugin might just create another identical frame. How would the app know to generate a frame where the wheel is rotated to some other angle? They’re pretty clever nowadays, but there are limits.
I had slo-mo footage of children running in front tall grass, and Twixtor was able to slow it down 50 %. Normally, the grass would have messed it up, but it worked.
At any rate there should be a downloadable demo for each, including help files.
Steve
-
If you pickwhip the rotation value of one layer to (say) the Y-position value of another layer, the rotation value will match the position value. The numbers will match. If the position value is 397, the angle will be 397.
So that’s how they work.
If your position values change, your rotational values should change. Given your stated result, I’d say you either used orientation (not rotation) or the position values didn’t change. Not sure though.
What is the result you want? (not the solution or the method)
Is there a range, where if position goes from 0 to 1094, you want the angle to go from 0 to 90? -
If you pickwhip the rotation value of one layer to (say) the Y-position value of another layer, the rotation value will match the position value. The numbers will match. If the position value is 397, the angle will be 397.
So that’s how they work.
If your position values change, your rotational values should change. Given your stated result, I’d say you either used orientation (not rotation) or the position values didn’t change. Not sure though.
What is the result you want? (not the solution or the method)
Is there a range, where if position goes from 0 to 1094, you want the angle to go from 0 to 90? -
I haven’t run across that problem before, so I don’t know if AE looks to the first image or needs to see that all images are 32-bit TGAs with alpha.
So … can you re-render the first frame with an alpha to fool AE on import?
Steve
-
That’s easy. Select the TGA sequence, and file>interpret footage>main. Reinterpret the sequence as 29.97 fps.
Since a sequence has no frame rate (it’s just a bunch of stills with convenient numbering), there’s no guarantee that AE will interpret it as you want. It assumes 30fps. You should be able to change that assumption by altering the “interpretation rules.txt” file.
Steve
-
Regarding drop frames and such on FCP, it all depends on the data rate of your codec. Your drive should be able to play DV and Photo-JPEG.
Ideally, you should have your footage on another external firewire drive so you’re not making the system drive work the OS and the footage at the same time.
Anyway, for more info, feel free to check out the FCP forum at the COW or elsewhere.
Steve
-
You cannot import any 3D objects into AE without the Zaxwerks Invigorator plugin. You can import some scene files from Maya, but that would be cameras and nulls only, if I recall.
AE is designed to import images that have been rendered from 3D apps. Anything else is basically a special case.
Steve
-
Yes. The disk speed requirements are somewhat less stringent from those for video editing, since editing assumes you want some kind of real-time playback from disk, which is not possible on AE, no matter what the platform.
To see your composition play back in AE, you create a RAM preview. You wait and watch the images render and store in RAM, then when all the appropriate RAM space is filled (or sooner, if you have chosen a short preview), the frames will play back at the proper frame rate (or half that if you’ve set it to do that).
AE generally is more dependent on processor speed and amount of RAM (up to 2 GB for the app) than disk speed. However, faster disk speed can allow your render to happen faster, since AE wouldn’t have to take as long to find the footage.
So yes, go ahead.
Steve -
Did you try messing with the physics time factor?
-
No worries — sometimes the threads cover an alternate solution to the problem, so they don’t always appear when you search a certain way. The thread covered wide angle distortion, not CC sphere specifically.
Though that may not help you … 🙂
Steve