UXP: Razor tool and marking clipped sections

Question

Hi everyone,I'm building a premier pro plugin with uxp and stuck with a problem as I'm facing a challenge to mimic the razor tool feature.I'd like to - Programmatically create these cut sections in my original video/sequence
- Add markers or tags to indicate which parts came from the original source- Place them in a new sequence one after another- Export srt file programmatically- Extract video metadata programmatically
Is there any way to do this using the UXP APIs, or would I need to fall back to CEP (ExtendScript) to achieve it?
Thanks

bbb_999 · Accepted Answer

There is not yet any UXP API that mimics the razor tool.In PPro, all markers and metadata associated with trackItems, are actually attached to the backing projectItem; it's not possible to have different markers and metadata for each trackItem. [Same for CEP+ExtendScript and UXP.]Placing trackItems in a sequence = no problem. [This is the same for CEP+ExtendScript and UXP.]Export .srt file = no problem. You would use an output preset (.epr file) that specifies whatever settings you want. [Same for CEP+ExtendScript and UXP.]Which video metadata do you mean? As mentioned, each projectItem has XMP metadata (which includes markers); width/height info is included in that. [Same for CEP+ExtendScript and UXP.]

VideoQuickFix · Answer

For anyone blocked on this today, there's a workaround path: Premiere's Control Surface SDK (the native C++ plugin layer) can dispatch the host's internal commands in their proper UI context, including "Add Edit," which is the blade-at-playhead operation behind Cmd+K. Position the playhead and set track targeting from your UXP panel, dispatch Add Edit natively, and you get true razor semantics: each piece keeps correct source mapping, fully undoable, because it's the exact operation the UI runs.

Building a control surface plugin just for one command is a lot of overhead, so I'll share what we did: we hit this same wall building a commercial panel, put our native plugin behind a local WebSocket, and have since documented the API and opened it up for free. It includes get.commands (dumps the host's full command registry with context IDs, so you can find Add Edit and anything else) and exec: (dispatches any of them). Docs: https://videoquickfix.io/vqf-engine/api

On the markers question from the original post, still true that trackItem-level markers aren't a thing; they attach to the projectItem. The pattern that's worked for us is sequence markers at the boundaries you care about (creatable from UXP), which a native plugin can also locate by name via the Marker Suite. Not per-clip metadata, but enough to identify and process sections reliably.

Caveat before anyone gets too excited: macOS only for now (Windows build is in slow development, wife just had a baby). Disclosure: I built the engine, it's what runs under our VertForge plugin. Happy to answer questions if anyone tries this route.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.