Rob Womack
Forum Replies Created
-
That worked! Thanks.
I figured I was making three lefts to take a right, but the loopIn, loopInDuration and loopOut functions confuse me, for some reason.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
If you want to try expressions, check out Dan Ebberts’ motionscript site. He breaks down the math and demonstrates lots of options: https://www.motionscript.com/articles/bounce-and-overshoot.html
If you want it more realistic, I’d suggest playing around with Newton2 (https://aescripts.com/newton). It takes a bit of getting used to, and the tutorials are fairly basic, but there’s a lot of cool realistic physical details you can add to your animations.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
That’s it! I’m going to remember you in my memoirs, Dan.
So, normalizing the vector is what I currently don’t get. You normalize it to make it a unit vector of length 1. So, if my distance is 3.45678 pixels, normalizing represents 3.45678 as 1 unit, right? But each integer difference in the slider value moves the object by 1 pixel, even though we’re multiplying. In my mind, the slider value of 1 would mean 1 * 3.45678, which would leave it where it is. A value of 2 would mean it moves away from the camera 6.91356 pixels. Clearly, this is not the case. What am I misunderstanding here?
And thanks again.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
So, if I want my bounding box to follow the object behind other objects and be affected by the depth of field of the camera, I’m going to have to fake it then, right? That’s why I was translating into camera space – so I could keep it locked tight and not have to futz with camera blur effects and masking and such.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
Well, that works fantastically. Thanks Dan! How come it works in Comp space but went out of whack in the cam space?
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
Thank you sir. I was unaware you could use the instanceof operator to identify a Light.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
My biggest issues with FCP-X is that for all intents and purposes, it is an iMovie update not FCP, and that it does not fit into any professional workflow with ease. Unless of course, you color corrected and mixed from within Final Cut (which I used to do), in which case this is not an issue. Attempting to change the paradigm of video editing is all well and good, and I wish them luck although I think this effort is doomed, but I don’t think it’s fair to characterize negative reactions as whining when a professional’s tool of choice is changed so dramatically with no hope of backwards compatibility (except with iMovie). You might shoehorn FCP-X into a workflow, but it is not designed to do that. FCP-X is the workflow, and a fairly limited one at that. No secondary color correcting? No multitrack recording and mixing? Fine, but no other way to do that? Or to even view your video on a broadcast monitor? Poor.
I say that it is an update to iMovie simply because of the fact that you can open old iMovie projects, but not FCP projects, that FCP-X and iMovie share many of the same interface features and nomenclature, and that the paradigm is an extension of the iMovie paradigm. Maybe they didn’t work off the iMovie codebase. But who cares? They removed interoperability and added extremely gutted versions of Color and Soundtrack Pro (which was already hobbled), and this is a good thing? Yes, if you cut with iMovie, then it is a very good thing. In any case, you can call this FCP-X 1.0 but it isn’t. It is supposed to be Final Cut Pro 10 and it only works with old versions of iMovie, and in all practicality this makes it an iMovie update.
As far as the backwards compatibility thing goes, allowing us to operate FCP7 on the same machine is a weak compromise, because eventually FCP7 will not work on the MacOS. Then what? Sorry, sir, but you’re screwed. At least when OSX first arrived, there was a way to operate all the OS9 applications from within OSX. Not FCP, though.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
It only does this in Final Cut on a variety of projects that share the same footage files. Quitting FCP restores the normal behavior, so I don’t think it’s an OS issue. I just have to go through each project in the browser and manually save, or else I have to go to the autosave vault.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
Try rendering in the background, if you’re not already (https://aescripts.com/bg-renderer/). Also, a boost in RAM will be very beneficial. I believe the error comes from not having enough memory, so it might be other apps are running? Or you don’t have enough RAM to render out your project.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency” -
There’s a free script from Popcorn Island (https://www.popcornisland.com/after-effects/final-cut-2-after-effects/) that I use that moves sequences from FCP to AE. It doesn’t touch the plug-ins, but I don’t mess with the plugins in FCP too much, because of the limited manipulation of keyframes. I find FCP too awkward for much other than color correction, so the PI_FCP2AE script is perfect for me and it’s free. I highly recommend it.
Robert Womack
Creative Bridgekeep
http://www.CurrentMarketing.com
“Louisville’s Leading Interactive Marketing Agency”