Steve Roberts
Forum Replies Created
-
Indeed. Storyboard it out. Get a buddy to sit in a car and take a snap. Do an animatic.
When in doubt, board it out.
-
What exactly do you want to be random? The layer order (top to bottom) in the timeline?
You can click any of the columns in the Project window to sort them differently, then drag into the timeline, and they will maintain that sort. It’s not random, but it could be on size, date or duration, for example.
… or there seems to be a script mentioned at the bottom of this link:
-
I’m sorry you’re having this trouble, as it sounds pretty frustrating. I also don’t know how to solve it right now, but if we get a discussion going, maybe something will come up.
1. It may be RAM, as this sort of random thing sometimes happens when RAM usage reaches a certain point and a certain RAM chip is accessed. Can you open OSX’s Activity Monitor and monitor RAM usage to the freeze point?
2. Stab in the dark. Can you disable OpenGL?
3. Has this machine always behaved in this manner? If not, what changed before the trouble started?
-
Don’t forget … the driver would be in the seat if you shot the car right-side up and flopped the shot. If the car were really upside-down, he’d probably be lying on the ceiling of the car (Men in Black), unless he were belted-in pretty well. Then the audience would expect the gag when he has to undo the seat belt and get out.
Well, I would.
And he’d need a short haircut.
-
Is everything (layers and comps) the same length (running time)?
-
They’re two different specs — there’s no need for them to match. 🙂
By the way, PAL is squeezed differently too. Off we go, merrily into the land of confusing video specs…
-
1920×1080. Why? Because that works out to 16×9, where 120 is the common factor.
720×540 works out to 4×3. Like 640×480.
-
Search the COW for “fold” or “paper airplane”.
-
Try setting the frame rate in AE to 23.976, not 23.98. FCP is doing 23.976, but calls it 23.98.
4/5 of 30 fps is 24 fps.
4/5 of 29.97 fps is 23.976 fps. -
[Bohdan Stehlik] “I supposed nudging, moving and slightly rotating around progressive footage is easier, because there won’t be any problems with the fields. Not sure if that assumption is correct.
“You are correct. If the footage were interlaced, its fields must be separated (interpret footage) if you are going to move/rotate/scale/blur/distort the footage. Fieldskit will give a more accurate result if the footage was 60i, because, technically, the full frames don’t exist in that kind of footage, and they have to be created by AE or Fieldskit.
However, if your footage was shot 24P, then the original full frames do exist, and Fieldskit will give you the same thing as separating fields.