http://motionographer.com/2007/06/14/ae-to-c4d-a-new-more-comprehensive-solution/

I think I can make that work. It sounds like maybe it should be the next thing on my list?

Pretty much all the hard work is done now. With the first version, I was just trying to get everything together for a working solution. With the amount I learnt in the process, I can see that a lot more is possible.

For example, I should be able to create the camera rig in C4D instead. So C4D is matching AE, not the other way around. Given another week or two I could probably also export frame rate, duration, zoom / field of view, nulls, layer planes and maybe even lights.

It partly depends on what feedback I get, so it’s good to find some positive comments. If you have specific requests, you should reply to my AEtoC4D thread on http://www.aenhancers.com

Paul

I appreciate the follow up. I’ll post an update in the body of the post for those who don’t read comments.

Best,

Dale

Here’s a link to the project:
http://www.paul.tuersley.btinternet.co.uk/scripts/riggedCam_noXYZ.zip

The sliders that were controlling position are now reading the Null’s position instead. This means it should still work with the v1.0 script, because it’s currently exporting those slider values.

Paul

Sorry if it wasn’t clear what I meant before, Dale.

I do a lot of camera animation in AE and it would FANTASTIC to be able to export the moves to C4D, but I’m pretty wedded to visible motion paths, at least in the XZ plane. So it would be great if this script could be adapted for standard cameras.

I’m going to post a comment over on your original rig thread as I’m drifting further off topic for this one.

But listen: A big thanks! I can already imagine some more linear moves that this might come in handy for. I’ll buy you a beer in London anytime.

Steve

Glad you find it useful, but I’m sort of along for the ride on this one. You can buy Paul and Stu a beer next time they are in your town.

And now I see what Steve was requesting… and you’re right Steve the camera movement is controlled via the expression so we’d need to integrate into the AE tools which is not set up in this script.

Dale

This now needs the final step to make this the bomb. As Steve mentioned above, because you are forced to animate the camera through the camera rig expression controls, you cannot use AE camera pan/dolly/orbit tools or manual tweaking of the motion path. This makes the camera control a bit tedious, even though I can see the benefits in the camera rig.

The trick (and this is the thing no-one seems to be able to crack) is to convert the key-frame data from an actual AE camera to C4D space. Then we can animate cameras as normal - run the script - and see it mirrored into C4D.

This is already a lot better than any results seen so far, so congratulations on achieving this. Look forward to further updates.

Should you get around the real-ae-camera-data, you realise you’ll have free beer waiting in most cities

The script simply sets up a camera with expressions. The camera will still behave like any other camera. Or am I misunderstanding the question?

Dale

Am I correct in assuming that the camera rig used for this script does not have motion paths visible in the comp window, and hence cannot easily be animated along curves? Please forgive me if I’m missing the obvious and sorry for posting slightly off-topic.

Steve