New masking - object mask data in the external file

[Kamil Pekala]

Hello, I'm the author of a Premiere Pro plugin called "Mask To Transform" which is able to convert the tracked mask into position/scale/rotation keyframes that can be applied to a Trasnfrom effect to e.g. make motion graphics "stick" to an object in the scene etc. My plugin is officially available in Exchange: here's the link https://exchange.adobe.com/apps/cc/105713/mask-to-transform

Now with the new masking soluion in Beta my customers are writing to me that my plugin stopped working and it would be amazing if I can make it work with the new (and admittedly pretty awesome) object masking. The problem is that the object mask data sits in a binary file on disk and there doesn't seem to be an easy way to read it. 

So my question is: for the purposes of extention development is there a way to somehow read the data stored in these object mask files?

Thanks,

Kamil

[Bruce Bullis · Accepted solution]

Hi Kamil,

Sorry, Adobe has no plans to expose or document the contents of those files. 

[We'd be happy to help with the "stopped working" part, provided some actionable specifics...?]

[Kamil Pekala]

Any other way to access the mask keyframes data? Using ExtendScript or via a C++ plugin?

[Ginge_]

SO... Just confirming - Adobe think that it's intuitive + productive to make mask data not copy/pasteable? So if I've got a mask on a layer, and I wanted to copy the mask to another layer, you're saying that's not possible? Because surprize - it's not! Something that has been in the product for years, something that just makes logical sense, and now it's been removed for quite literally 0 reason? Well Adobe, looks like I'll be on the market for a much better editing software - one that is created by a company that KNOWS how to actually edit, not make gimmick updates which make editor's workflows less productive, with no logical explanation as to why the change was made. GREAT JOB ADOBE! Not surprized though.

[Kamil Pekala]

Nah. It is copy/paste-able but it's not readable in anyway from the plugin SDKs' perspective 😞