Activity › Forums › Apple Final Cut Pro Legacy › Motion tab keyframing broken in FCP 6
-
Motion tab keyframing broken in FCP 6
Posted by Gordon Gurley on April 29, 2008 at 11:45 pmIf anyone can tell me different, I’d love to hear it.
Gordon Gurley replied 18 years ago 4 Members · 10 Replies -
10 Replies
-
Walter Biscardi
April 29, 2008 at 11:57 pm[Gordon Gurley] “If anyone can tell me different, I’d love to hear it.”
Ok, I’ll tell you different. Works here, has always worked here. All motion elements.
Walter Biscardi, Jr.
Biscardi Creative Media
HD and SD Production for Broadcast and Independent Productions.STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!
Read my Blog!

-
David Bogie
April 30, 2008 at 2:47 pmUmm, putting it as kindly as possible, this would come under “user error.”
You will soon figure out what you’re doing wrong.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Gordon Gurley
April 30, 2008 at 4:58 pmSorry for such an inflammatory post. I’ve been using FCP since 1.25, and to see the motion tab functionality deteriorate over the years has been frustrating. We rely on it to do quick and dirty motion graphics and it was part of the reason to move to FCP and away from Avid.
But maybe that’s my problem: I’m stuck in and old way of doing it and haven’t figured out the “new way”.
But on the other hand, it’s not just me. All my editors are having this problem and are bringing it to me to figure it out.
That’s why I’m here.
-
Fred Miller
April 30, 2008 at 5:27 pm“Broken” is a pretty vague. A little more detail might help me…help you.
BTW – Motion tabbing works OK here.
FCP Studio 2
Dual 3Gg Quad Core
5Gg RAM
KONA 2
OS 10.4.11 -
Gordon Gurley
April 30, 2008 at 6:00 pmFCP 6.03
QT 7.4.5
Intel and G5
10.4.11
AJA and native
Sony CRT, JVC LCD
XSAN 1.4.2DV timeline ( please don’t flame me for using DV. I’m in education, and DV has been a great format for what we do. I’m not making BMW commercials here).
Place a still (tif, jpeg, png, psd) over DV footage. Keyframe scale and position. Render.
All hell breaks lose. Sometimes the still appears to go into “low res mode”, ala setting your canvas to 1/4 res. Sometimes it doesn’t look so bad, but the animation “jumps”. Sometimes it’s just one frame that’s bad, sometimes it’s skipping all over the place.
Changing sequence settings sometimes helps. But I haven’t been able to isolate the problem because often when the problem goes away, it goes away completely, ie I can go back to the settings that were having the problem and it will render fine.
Could it have anything to do with the fact that I’m on shared storage?
-
Fred Miller
April 30, 2008 at 6:58 pmThe only thing from your specs that raises my eyebrow is the version of QT that you’re on. Can you recall when things started going bad? Was it after an update?
FCP Studio 2
Dual 3Gg Quad Core
5Gg RAM
KONA 2
OS 10.4.11 -
David Bogie
April 30, 2008 at 9:17 pm[Gordon Gurley] “DV timeline ( please don’t flame me for using DV. I’m in education, and DV has been a great format for what we do. I’m not making BMW commercials here). Place a still (tif, jpeg, png, psd) over DV footage. Keyframe scale and position. Render. All hell breaks lose. Sometimes the still appears to go into “low res mode”, ala setting your canvas to 1/4 res. Sometimes it doesn’t look so bad, but the animation “jumps”. Sometimes it’s just one frame that’s bad, sometimes it’s skipping all over the place. Changing sequence settings sometimes helps. But I haven’t been able to isolate the problem because often when the problem goes away, it goes away completely, ie I can go back to the settings that were having the problem and it will render fine.
Could it have anything to do with the fact that I’m on shared storage? “
This is totally different than your OP. We just wrote you off as a hopeless noob. We get LOTS of those around here, squealing and whining about the silliest things.
What you’re describing is a rendering issue and not a function of the motion controls. As Fred is trying to figure out, when did you notice things stopped functioning? Does this happen with all types of media or all types of rendering or just jpegs with motion?
Back in the olden days of SCSI RAIDs, I’d immediately jump to suggesting the controller card, the connections, the cables, or the terminators. Shared storage can be an issue if that’s where everything is located, source media and render media. If you have a separate media drive locally, try using it for two or three short clips and a jpeg or two. Be sure to change your render scratch to point to eh local drive.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Gordon Gurley
April 30, 2008 at 10:51 pmWe just did the big upgrade to FCS2 and upgraded to the latest QT. That’s when I noticed this problem. But we’ve been having similar problems for a while now. Maybe a year or so. The old problem has been that scaling anything looks bad. But the erratic animation is a new “feature”.
Gordon Gurley
Director of Operations
Stanford Video -
Gordon Gurley
April 30, 2008 at 10:53 pmread the response above. I’ll try rendering locally and see if that changes anything.
Gordon Gurley
Director of Operations
Stanford Video -
Gordon Gurley
April 30, 2008 at 11:17 pmOK, I’ve at least isolated something here. Keyframing anything in “Drop Shadow” or “Distort” motion tabs seems to be causing problems.
Gordon Gurley
Director of Operations
Stanford Video
Reply to this Discussion! Login or Sign Up