# Video-related questions **URL:** \ **Category:** Developers Live Q&A\ **Created:** [September 29, 2026, 5:17pm UTC](https://forums.creativeclouddeveloper.com/t/video-related-questions/12228 "2026-09-29T17:17:40Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![RuHowe](https://avatars.discourse-cdn.com/v4/letter/r/41988e/32.png) [@RuHowe](https://forums.creativeclouddeveloper.com/u/RuHowe)\ **Post date:** [September 29, 2026, 5:17pm UTC](https://forums.creativeclouddeveloper.com/t/video-related-questions/12228/1 "2026-09-29T17:17:40Z")
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? ---
**Author:** ![bbb\_999](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/bbb_999/32/4247_2.png) [@bbb\_999](https://forums.creativeclouddeveloper.com/u/bbb_999)\ **Post date:** [September 29, 2026, 5:38pm UTC](https://forums.creativeclouddeveloper.com/t/video-related-questions/12228/2 "2026-09-29T17:38:00Z")
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! 😉 captions : Sounds like a fine feature request for us, and (potentially) a market opportunity for the forseeable future. ---
**Author:** ![RuHowe](https://avatars.discourse-cdn.com/v4/letter/r/41988e/32.png) [@RuHowe](https://forums.creativeclouddeveloper.com/u/RuHowe)\ **Post date:** [September 29, 2026, 5:39pm UTC](https://forums.creativeclouddeveloper.com/t/video-related-questions/12228/3 "2026-09-29T17:39:58Z")
Thank you, Bruce! And thanks for the pointer to the other forum.