Video-related questions

UXP Developers Live Q&A
1

I’m sure we won’t have time to talk about these things today, but here are some blockers that I’m working around.

Editable titles
Is there any supported way to set the text of a Premiere-native Essential Graphics title from outside Premiere? I think UXP cannot read or write Source Text, and OTIO and FCP XML carry titles as an opaque blob.
I’ve reverse engineered reading them & styles from the .prproj, and I’m testing writing back, but relying on this feels fragile.

Masks:
Will UXP ever be able to read and write masks - shape, feather, expansion, keyframes?
Could Premiere write them into its OTIO metadata?
I am having to read them from prproj and the sidecar data. But can’t write them back.

OTIO round tripping:
Could Premiere’s OTIO support follow the OTIO metadata convention by keeping other apps’ metadata keys on import? Could it add stable clip and track ids and a marker type to its own metadata, as it already does with a GUID for markers? And could it read marker colour back on import? OTIO has no id field, and FCP XML ids change on export/import. Or could we/should we think about handling this kind of roundtripping using a plugin, augmenting what’s available in OTIO?

Captions - in OTIO and VTT export: Could Premiere’s OTIO export include caption tracks, as a subtitle track or markers? Today captions need a separate SRT, so they fall out of any OTIO round trip. Web app players like mine use VTT, so I have to convert everything that comes from Stornaway, which is a simple conversion but a pain. Would be super easy to add VTT export as it’s almost the same as SRT. Or again, should I just add to our future plugin?

2

Editable Titles: Support for “New Text Layer” is on our post-parity feature request list.

Masks: Also post-parity. You won’t be able to read them, but you’ll be able to apply them.

OTIO: [My old team was responsible for Pr’s initial OTIO support.]

Most of what you mention requires plumbing support across Pr, unrelated to OTIO. “stash and persist other metadata keys upon import, and pass them along at export” = Presumably, this would be Pr private metadata, attached directly to the OTIO’s timeline.

Read marker color on import = I don’t know what we’d do with that data; Pr will already have 16 defined marker colors, which are not guaranteed to match that imported, right?

It will be Some Time™ before round-tripping OTIO files will be supported, by any OTIO client. [Like, we’ll probably have hover cars before then…]

could we/should we think about handling this kind of roundtripping using a plugin, augmenting what’s available in OTIO?

Sounds like a market opportunity! :wink:

captions : Sounds like a fine feature request for us, and (potentially) a market opportunity for the forseeable future.

1 Like
3

Thank you, Bruce! And thanks for the pointer to the other forum.

1 Like