Before I crack on with following this up with Autodesk support, I am curious to know if anyone else has seen strangeness like this before.
I am in a 2026 project, 25fps and the alembic cameras that I importing seem to have three key frames for every frame.
060_200.cam.video_1.def.cmm.v2.zip (13.3 KB)
Try using:
abcls your_file.abc
This should list header info including framerate
oh - now in broad daylight, on a big display, the animation curves are not linear so the keyframes have tangent handles…
What channels are they associated with? A Camera3D node has multiple channels, so you coud very well have different values for the Position X, Y, and Z for example…
These are all on one animation track and they are not tangents. If I try and move them they suddenly snap to the actual frame. They exist in the sub frame area.
I’ll get it sent off to support for analysis I just wanted to check and see how unique it was before I started the process
What happens if you scale the track on x by 1000%? do the tangent handles scale as well?
If they do then you need to look inside the alembic header to see how the time was quantized.
if they don’t you just need to switch your animation curves to linear and the handles will go away.
you forced me to open the file - the keyframes are indeed tripled - which suggests that the authoring platform isn’t clean.
Ahh. Thanks @philm
I am always being told that it is something I am doing that is the problem 
Or that “all the other software programs see it fine” it must be flame that is broken.
My first instinct is that it is converting the values of bezier tangent handles into sub-keyframes. otherwise, they would be spaced evenly between the keyframes. But that’s just a first impression. . . .
EDIT: This things pretty screwed up. I can’t even get the keyframes to snap to the frames after I get rid of the extras.
Please contact the support and provide them with the file so they can investigate the issue.
timewarps from avid aafs often have fractional keyframes like this as well. as a workaround something I’ve gotten away with in the past is averaging the animation channel by a very small value <=1 which usually clears out the keyframes between frames without a noticeable change to the animation, though camera tracks could certainly be more fiddly.
I tried that with this thing and it cleared the keyframes that were on integers and left most of the sub-keyframes.
To fix sub-keyframes:
That doesn’t really work in this case because there are already keyframes on the nearest frame.
Similar thing happened to me. If you select the fps from where the alembic is exported, it works well. In this case your Flame project is 25 fps. If your camera matchmove project uses 23.97 select that value from import options.
