Time Remapping component is completely inaccessible via scripting (ExtendScript AND UXP premierepro API) in Premiere Pro 26.3.0

UXP UXP Developer Tool
1

Title: Time Remapping component is completely inaccessible via scripting (ExtendScript AND UXP premierepro API) in Premiere Pro 26.3.0

Summary

Neither the legacy ExtendScript/CEP API nor the current UXP premierepro module (API “Since 25.6”) exposes the built-in Time Remapping component on a video clip’s TrackItem. This makes it impossible to build any plugin/extension that programmatically creates speed ramps, speed bumps, or variable-speed keyframes — a core, common editing workflow.

Environment

  • Premiere Pro 26.3.0 (2026), macOS
  • Tested via both:
    • Legacy CEP/ExtendScript (hostscript.jsx, PlayerDebugMode enabled)
    • UXP plugin using require("premierepro"), manifest host.minVersion: 25.6.0

What’s missing

VideoClipTrackItem.getSpeed() and .isSpeedReversed() exist and are read-only. There is no setSpeed, no enableTimeRemapping, and critically:

  • TrackItem.getComponentChain() / VideoComponentChain.getComponentAtIndex() never returns a “Time Remapping” component — only “Opacity” and “Motion” are ever present, even when Time Remapping is actively enabled and keyframed on the clip via the Effect Controls panel UI.
  • VideoFilterFactory.getDisplayNames() / getMatchNames() do not list “Time Remapping” as an insertable effect (confirmed — searched the full list for anything matching /remap|time|speed/i; only “Metadata & Timecode Burn-in” and “Posterize Time” matched).
  • The QE DOM (app.enableQE()), historically a backdoor for capabilities missing from the public ExtendScript API, returns false in this build — no documented way to re-enable it.

Reproduction (UXP)

const ppro = require("premierepro");

const proj = await ppro.Project.getActiveProject();

const seq = await proj.getActiveSequence();

const track = await seq.getVideoTrack(0);

const items = await track.getTrackItems(ppro.Constants.TrackItemType.CLIP, false);

const clip = items[0]; // clip already has Time Remapping enabled + keyframed via the UI

const chain = await clip.getComponentChain();

const count = chain.getComponentCount();

for (let i = 0; i < count; i++) {

const c = chain.getComponentAtIndex(i);

console.log(await c.getDisplayName(), await c.getMatchName());

}

// -> logs only "Opacity" / "AE.ADBE Opacity" and "Motion" / "AE.ADBE Motion"

// -> Time Remapping component never appears, regardless of clip state

Impact

Speed ramping / variable-speed effects are one of the most common editing techniques in short-form and social video work. There is currently no supported way — old or new API — for a plugin to automate this. Given Premiere Pro is deprecating ExtendScript/CEP in favor of UXP (per the announced Sept 2026 timeline), this looks like a capability that was dropped rather than migrated, and needs to be added to the UXP premierepro component/effect model (e.g., exposing Time Remapping as a component on the chain, or adding a dedicated TrackItem.getTimeRemap() / similar API with keyframe access analogous to ComponentParam).

Ask

Please expose the Time Remapping component (and its Speed parameter) through VideoComponentChain / a dedicated API, with the same keyframe/action model already available for other component params (createSetTimeVaryingAction, createAddKeyframeAction, createSetValueAction, etc.).

bbb_999 2

While [above] seems like AI output, it is factually correct.

We will address new API feature requests, once we get closer to ExtendScript ↔ UXP parity.

3

I was using Claude code to write a plugin to make speed ramps easier to create - so human directed, but yes, this is what it told me to send you to get the best results/answers. Thanks for the reply! Is there any “best guess” timeline on when you might achieve ExtendScript - UXP parity?

4

Adobe cannot comment on the specific feature set of unannounced product releases, and…

Current plan = MAX 2026.