I've come across a very annoying bug in AE, in conjunction with Cineware. I have a Scene using multiple cameras, and everything was working fine until I changed
the animation keyframes of the last cam, 'Cam3'.
'Cam3' (as seen in the C4D scene) was initially animated the following way: A-->B1__B2-->C //the keyframes 'B' have the same value, and the interval 'B1___B2' corresponds to a full stop.
I changed the animation tempo by:
As visualized here:
The problem is that AE/Cineware extracts the wrong camera data:
|The scene||The Data|
|How C4D displays and renders it||A-->X1-->C|
|How Cineware displays and renders it in AE Comp||A-->X1-->C|
|Which data Cineware extracts in AE Comp||A-->X2-->C|
The data that Cineware extracts can't be found inside the scene itself, but must be buffered/coded in a location that one can't see or access.
You can download the C4D scene by following the link: LINK
Import the file to AE, extract the scene and have a close look at the light named 'null' and 'cam3'. I paranted a second instance of the 'Text' Text Object to 'null', in order to visualize that 'null' ends at the exact same coordinates as the 'Text' Text Object.
If the data extracted by AE was right, then 'null' would stay in the center of the Text Object at all times. But as you can see, 'null' starts moving without its paranted Text Object, which is the result of 'cam3' starting to move in AE, while 'cam3' remains steady in C4D; it ends at the right coordinates and the right time though.
Can anyone confirm this issue? Have I found a bug? Does anyone have a solution to this problem? Is there a possibulity to flush the cache?
Can't have a look at your file since I'm far away from home, but it seems to mee you are simply using out of range adjustments on the tangents and AE simply clamps the results, bringing it back to the original base interpolation. The parenting might also have some weird influence. Anyway, why not simply bake the keys in the C4D?
Didn't think about baking the keyframes, true. I'll try this tomorrow.
Just checked the keyframes again and couldn't see anything uncommon about my setup and the keyframes.
Baking the keys did the trick. Thank you, Mylenium!