Now in Beta: Content Credentials in Premiere Pro and Media Encoder

[eckiAMETeam]

We are excited to announce the first implementation of Content Credentials in Premiere Pro and Media Encoder! This implementation aims to support transparency about the usage of Adobe’s generative AI features such as (Adobe Firefly).  

Content Credentials are a new kind of tamper-evident metadata. They enable creators to add extra information about themselves and their creative process directly to their content at export or download. This information allows creators to receive more recognition for their work, connect with others online, and enhance transparency for their audience.  

Content Credentials are part of a growing ecosystem of technologies available through the Content Authenticity Initiative (CAI). Adobe, along with our 2500+ CAI members, is dedicated to restoring trust online by creating a standard way to share digital content without losing key contextual details such as who made it and when and how it was created.  

What’s new: When exporting a Premiere Pro sequence that contains one or more Adobe AI generated assets, either directly from Premiere Pro or through Media Encoder, both applications will now display a notification that Content Credentials will be included in the exported assets for supported formats. Currently, these formats are: 

• MP4 

• QuickTime MOV 

• AVI 

• WAV 

• MP3 

• JPEG 

• PNG 

• TIFF 

  

You can read more about this feature on our support page here. Exported files with Content Credentials can be verified here. 

[R Neil Haugen]

This looks like a listing of "containers" ... it would also be useful to get the specific codecs within those containers that will or won't be supported.

[Francis-Crossman]

The metadata that gets injected is specific to the container, not the codec inside the container, so you should expect the same support for all codecs that a container supports.  If you find different, that's a bug we need to investigate.

[R Neil Haugen]

Thanks for the clarification, Francis. That then makes this extremely useful.

Perhaps if the original post was edited to add that information, it would be more clear to all readers.

I asked simply because, of long experience, containers at times do have different ... behaviors? ... something ... with different codecs. Clarity is always a Good Thing in pro workflows, of course.

[Shebbe]

The first link to CAI seems to be broken as of writing this post.

[eckiAMETeam]

Thanks! I just corrected it.

[baaronkun]

Can this feature be disabled ?