- April 15, 2013 at 7:48 pm
while we wait for the adobe elves to deliver Neo – AKA – FCP8, I’ve been pushing more stuff through CS6 to get el brain in gear.
and my good god but I have missed adobe’s abilities when it comes to keyframing.
its effectively after effects keyframing (pre the switch-over to full function curves) and it is LOVELY.
because if there is one thing the FCPX guys need to address – it is keyframing in X – thats one of the things I have genuinely spent quite a bit of time with,
and it really is an unmitigated mess.
- April 15, 2013 at 9:27 pm
WOOO this makes me excited. Gonna make the switch as soon as I can get this batch of projects out the door. No more fumbling with teeny-tiny buggy FCP7 keyframes!
Video editor, animator, composer, producer
- April 15, 2013 at 10:02 pm
and also maybe hold off til 7 if you’re jumping in, it’s four weeks out – 6 is good, but 7 is effectively the mother lode. It actually is warp drive FCP8.
ProRes native – speedgrade looks as adjustment layers drops – the entire nine yards. It’s a mental release.
- April 16, 2013 at 6:01 am
Those curves look like what AE had back in like version 6.0 (not CS6). I’m surprised Adobe doesn’t just take the AE keyframe and curves engine and build it right into PrPro.
- April 16, 2013 at 9:03 am
[Erik Lindahl] “Those curves look like what AE had back in like version 6.0 (not CS6). I’m surprised Adobe doesn’t just take the AE keyframe and curves engine and build it right into PrPro.”
Essentially, we did. 😉
- April 16, 2013 at 9:09 am
Take the AE CS 6 engine or the AE 6.0 engine? 😉
Not to be bitter but it looks like it’s from the 1990’s instead of 2000’s. With the Mercury Engine PrPro could be an AMAZING online tool. It just seems to fall a bit short every time I try to do that “online” stuff there and I end up in AE for even simple things.
- April 16, 2013 at 9:20 am
I agree that the UI could use a bit of updating. However, when we added the graphing view in AE CS2, not many people really gravitated towards it. It’s a tricky proposition on how to update it and guarantee acceptance. Good thing today is that the key framing is powerful and familiar.
If you have ideas about how it should be done, be sure to file a feature request…
Dennis – Adobe guy
- April 16, 2013 at 12:38 pm
to be fair this makes absolutely no sense – you’re suggesting throwing the user into the full keyframe graph editor view?
How exactly is that supposed to work in that real estate? er, the graph editor replaces the timeline in AE?
Does that make sense to you in this context?
My point was actually that I specifically liked to be working in the pre-graph editor keyframe apparatus in this context. Sometimes you really miss it.
You have the same degree of control more or less, but it’s inline and not as dis-orientating as the switch to the graph editor can be.
But more basically – this keyframing completely kicks FCP7, X, and Avid’s asses off the street and down the lane.
- April 16, 2013 at 12:55 pm
Too confusing for my little brain.
Log in to reply.