Skip to main content
A
athletic_fact6385
Known Participant
August 10, 2026
Question

Negative numbers in CTI are always absolute, not relative

  • August 10, 2026
  • 11 replies
  • 59 views

Issue

When I enter relative values in the CTI like +20 or -20, the negative values always jump to the absolute position (-0;00;00;20), which is inconsistent behavior on one hand but it also makes no sense at all to be navigated to a negative timecode.

Steps to reproduce

Click on the CTI (or open the popup window).

Type +20

The timecode jumps 20 frames forward as expected.

Click on the CTI (or open the popup window).

Type -20

Expected result:

The timecode jumps 20 frames backwards.

Actual result:

The timecode jumps to the absolute time -0;00;00;20

 

Tested with different compositions, different framerates and clean install.

Adobe After Effects version

26.3.0 (Build 87)

Operating system

Windows 11

      11 replies

      Roland Kahlenberg
      Roland Kahlenberg
      Legend
      August 11, 2026

      Not all input fields accept < 0 as a valid input. So, it is not correct to view and expect the same behavior in the CTI input field and a property input field. 

      To be fair, a more consistent approach is to break down the required inputs for the CTI into absolute and relative inputs. 

      All absolute inputs accept + as the default and a - input as a move towards negative time.

      For relative inputs - 
      ++ n defines a time value that moves the CTI to the right, an increment, from its current time position forward
      -- n defines a time value that moves the CTI to the left, from its current time position forward

      This provides UI consistency through clarity, removes unnecessary cognitive overload when results aren’t as expected and ensures burgers are sufficiently thick and juicy.

      The challenge is how will users know they have to input TWO math symbols? Most users will never think of this requirement - this is a peculiar nature of UI-UX - humans expect all UI interactions to be simple, especially when inputting a number - they think it’s just a number - to appreciate they may/can input absolute or relative numbers is furthest from their mind. 

      So, the solution is actually a change in the UI - a toggle button to select between ABS/REL, with tool tips is the best solve, IMO.

      Very Advanced After Effects Training | Adaptive &amp; Responsive Toolkits | Intelligent Design Assets (IDAs) | MoGraph Design System DEV
      A
      athletic_fact6385Author
      Known Participant
      August 11, 2026

      It would be even more consistent and easy if the CTI input is handled exactly like the one in Premiere.

      I see no need to over complicate things and trying to force the logic of property input fields on something has a whole different context regarding its values: navigation.
      Adding buttons also would make it more of a hassle. If I enter absolute, that is already taken care of by the format, either by entering all numbers (0000211) or the whole formatting (0;00;02;11).
      As I say: Premiere does it perfectly. Why not taking something that already works, is known and simple? The only reason After Effects is confusing in that regard, is because the logic of property fields, that has a different context, is copy-pasted onto it.

      You are right, that some input fields won’t accept <0. So when out enter an amount or a calculation that’s <0, the result will be 0. The same should also happen in the CTI. But instead I get a negative time.

      But the CTI has another input problem: I can’t enter calculations. Property fields accept both ways “+5” and “x+5”, the CTI only accepts “+5” but not “0;00;02;11+5”, so you don’t have the way to enter “0;00;02;11-5” at all as you could in property fields. Yet another inconsistency, which makes it even more confusing (especially if the “+ -” way to subtract is unknown). 
      That’s why I say, ditch it all together and make the CTI input completely separate (not talking about the time remapping input as that is a whole other story as one is navigation, the other one property).

      Nishu Kushwaha
      Community Manager
      Nishu KushwahaCommunity Manager
      Community Manager
      August 10, 2026

      Update after checking with the AE team, this is actually working as designed rather than a bug, though the behavior is admittedly unintuitive. Here's how relative timecode entry in AE works:

      - Typing +20 means "move 20 frames forward relative to current position."

      - Typing -20 means "go to the absolute timecode -20" (which lands on a negative timecode).

      - To move backward relative to your current position, type +-20.

      So +-20 will move you 20 frames backward from where you are. AE's timecode navigation has worked this way for a long time.

      Hope that unblocks you. Moving this thread from Bugs to Questions.


      Thanks,

      Nishu

      A
      athletic_fact6385Author
      Known Participant
      August 10, 2026

      Hi ​@Nishu Kushwaha, thanks for your quick answer.

      Could you please explain why it is designed that way? In which case would I need to navigate to a negative timecode?
      I can’t think of a situation where that would be necessary.

      And yes, it is unintuitive because it is inconsistent behavior. 
      When I want to navigate to a specific timecode, I have to enter that timecode completely (when I want to go to 00:00:00:20, I have no other way than entering it like that). Why should it be any different if I would navigate to a negative timecode? The logic should be the same here.

      I guess, you tried to copy the same logic and behavior of relative calculations of other property fields. But there, negative values exist. This however is not true for a timeline. So that’s why it doesn’t make any sense there and thus should be changed.

       

      TLDR: Timecode behaves differently than property fields and such can follow another logic that would be more fitting there.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices