# Odd camera keyframes

**URL:** <https://forum.logik.tv/t/odd-camera-keyframes/13288>\
**Category:** Flame Questions\
**Tags:** action, alembic\
**Created:** [July 28, 2025, 5:29am UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288 "2025-07-28T05:29:20Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [July 28, 2025, 5:29am UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/1 "2025-07-28T05:29:20Z")

</div>

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.

 ![alembicCamera](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/f/f6b3249976e11f991c449316654675cdc106255c.png)

[060\_200.cam.video\_1.def.cmm.v2.zip](https://forum.logik.tv/uploads/short-url/rc130wnMbsXKCwCKPVJ9EfQotTR.zip) (13.3 KB)

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [July 28, 2025, 8:08am UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/2 "2025-07-28T08:08:19Z")

</div>

Try using:

abcls your\_file.abc

This should list header info including framerate

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [July 28, 2025, 1:56pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/3 "2025-07-28T13:56:08Z")

</div>

oh - now in broad daylight, on a big display, the animation curves are not linear so the keyframes have tangent handles…  
🤣

---

<div class="post-metadata">

**Author:** ![fredwarren](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fredwarren/32/158_2.png) [@fredwarren](https://forum.logik.tv/u/fredwarren)\
**Post date:** [July 28, 2025, 2:46pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/4 "2025-07-28T14:46:20Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [July 28, 2025, 7:21pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/5 "2025-07-28T19:21:08Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [July 28, 2025, 7:36pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/6 "2025-07-28T19:36:05Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\
**Post date:** [July 28, 2025, 7:47pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/7 "2025-07-28T19:47:02Z")

</div>

you forced me to open the file - the keyframes are indeed tripled - which suggests that the authoring platform isn’t clean.

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [July 28, 2025, 8:03pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/8 "2025-07-28T20:03:31Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [July 29, 2025, 1:58am UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/9 "2025-07-29T01:58:31Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![fredwarren](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fredwarren/32/158_2.png) [@fredwarren](https://forum.logik.tv/u/fredwarren)\
**Post date:** [July 29, 2025, 11:43am UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/10 "2025-07-29T11:43:32Z")

</div>

Please contact the support and provide them with the file so they can investigate the issue.

---

<div class="post-metadata">

**Author:** ![dazedinheaven](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/dazedinheaven/32/8669_2.png) [@dazedinheaven](https://forum.logik.tv/u/dazedinheaven)\
**Post date:** [July 29, 2025, 3:58pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/11 "2025-07-29T15:58:25Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [July 29, 2025, 4:15pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/12 "2025-07-29T16:15:18Z")

</div>

I tried that with this thing and it cleared the keyframes that were on integers and left most of the sub-keyframes.

---

<div class="post-metadata">

**Author:** ![fredwarren](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fredwarren/32/158_2.png) [@fredwarren](https://forum.logik.tv/u/fredwarren)\
**Post date:** [July 29, 2025, 4:40pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/13 "2025-07-29T16:40:34Z")

</div>

To fix sub-keyframes:

1. Select the Keyframes
2. Open the Context menu of a keyframe
3. Snap Keyframe to Closest Frame

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [July 29, 2025, 4:50pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/14 "2025-07-29T16:50:11Z")

</div>

That doesn’t really work in this case because there are already keyframes on the nearest frame.

---

<div class="post-metadata">

**Author:** ![alperoktay](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/alperoktay/32/2934_2.png) [@alperoktay](https://forum.logik.tv/u/alperoktay)\
**Post date:** [July 29, 2025, 9:35pm UTC](https://forum.logik.tv/t/odd-camera-keyframes/13288/15 "2025-07-29T21:35:41Z")

</div>

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.
