Discuss: New Metadata & Timecode Burn-in effect

[mattchristensen]

New in Premiere Pro Beta 15.2, the Metadata & Timecode Burn-in effect replaces the existing Clip Name and Timecode effects. This new effect takes advantage of our modern graphics engine and GPU acceleration for smooth playback while also offering an array of new types of metadata that you can burn into your video whether you need a simple watermark, timecode burn-in, or detailed attributes for high-end VFX workflows.

The Metadata & Timecode Burn-in effect can display 6 types of timecode and 20 types of project metadata. Apply the effect to a single clip or to an Adjustment Layer over your whole timeline. When applied to an Adjustment Layer you can set the Source Track the effect will read. Or, leave it set to Top Clip and the effect will use whichever clip is on the highest track. If you often need to display more than one type of metadata, you can apply another instance of the effect and then create an Effects Preset containing all your instances of the effect in one easy to re-use preset.

As we continue working to finish up this new effect we may make modifications that will cause existing versions of the effect to appear offline. If this happens you will need to re-apply the effect.

Note: Metadata & Timecode Burn-in effect is not yet available on Apple silicon Macs, but will be coming soon. If you use an M1 Mac and want to test this effect, you can run the Premiere Pro Beta in Rosetta mode by opening the Beta section in Creative Cloud, finding Premiere Pro, then choosing "Open (Intel)" from the ellipses (three dots) menu.

We look forward to your feedback on this new effect. Thank you!

Metadata & Timecode Burn-in in the Effects panel

Metadata and Timecode options in the new effect

[Path 88 Productions]

Nope.  Just goes to zero.  NG.  I'll DM with a sample audio file.

[Path 88 Productions]

14:42:38:00 vs. 14:43:30:22

[Path 88 Productions]

I've been attempting to find a solution via Adobe's phone call support.  Under their tech-advisement I was requested to use the previous Beta version to check the time code issue.  

Same problem.  Attached are screen grabs.  

Pay close attention to the metadata browser for a clue.  You can see that the "Dynaminc Media" --> "start time code" --> "time value" is accurate and the numbers we want to use @13:36:34  

However, the "Origination time" is not; it’s off by 16 seconds @13:36:50  Also, the incorrect time code that is ultimately displayed via the effect is also listed at the bottom of the metadata window @ 13:37:22.

I have no idea why there should be a bunch of different numbers here, but there it is.  Surely there's a reason for these sorts of numbers that are part of the file's metadata....whatever or whyever that is is a mystery to me.  I'd suggest allowing the new timecode effect to simply have the option to access the "Start Timecode" reading --and that would solve the problem, but I'm not a developer, whatta I know?  Not much.

If possible, it would be great if I could get a developer to address and explain this issue here so that future folks can know the problem.  There’s something going on with the Broadcast wav polyphonic (BWF.P) .wav files and the meta data timecode effect that I’m completely ignorant about. 

At the end of the day I'd just like to know if the Metadata And Timecode Burn-In effect can or cannot work as I’m currently trying to implement it on our audio files.  If it can’t, fine, I’ll simply stop trying to use it on audio files and consider the current iteneration of the effect to not fit the task I'm trying to do.  Works well otherwise.

Thanks!

[Bruce Bullis]

> I'd just like to know if the Metadata And Timecode Burn-In effect can or cannot work as I’m currently
> trying to implement it on our audio files

Today, it cannot.

We're tracking the issue as DVAPR-4245951; we'll keep you informed of our progress (I put your email in  the bug).  Thanks for the detailed explanations and testing!

[Path 88 Productions]

Many thanks for letting us know.  I'll work around the limitation until there's a fix.  Hope you guys can get the MetaDataTimecode effect sorted --because the effect is really a GREAT feature for Premiere.

[Guest]

Do you know if the field "creation date" will be added in the metadata and timecode burn-in please ?

[kevinc35445866]

Well that was easy... Thank you

[danw71857413]

Is there any technical information that would allow me to understand how the Metadata is being pulled from JPG images in the timeline?  I have a time lapse of the May 2024 Aurora with a few hundred JPGs on the timeline.  I am trying to use the "Metadata & Timecode Burn-in" feature to display the time each picture was taken.  Over the course of the time lapse this would display as a time code that tracks the progress of the aurora with accurate local time.

So far I have tried writing the proper value to the XMP Dublin Core "Description" field of the JPG.  But in Adobe Premiere, when I select "Description" for this JPG nothing is displayed.  Please provide some additional documentation on exactly what fields are being pulled from JPG files so that I can populate the field properly.  Thank you!

[Bruce Bullis]

Project items representing image sequences in PPro will be interepreted as having the timebase specified in PPro's Prefs --> Media --> Indeterminate Timebase. 

The metadata effect's 'Line 1' param chooses the source of the metadata; it's likely that, because a 'Description' field is not expected to change or vary across each frame of a given project item, that the effect isn't going to re-access the description field of each constituent .jpg, in that image sequence. 

One possible approach: Instead of importing the .jpg files as an image sequence, change PPro Prefs --> Timeline --> Still Image Default Duration to a suitable value, then import each individual image, and apply the metadata effect. The effect will then look at Description field for each particular .jpg, rather than the Description field from the aggregate project item that gets created, when you import those images as a sequence. 

[Trevor_Asq]

Isn't it more that the metadata effect reflects the 'project' description metadata, rather than the 'clip' (i.e. xmp) metadata?

Does seem crazy that there's no creation date metadata available in the effect.

[Bruce Bullis]

Fun: There is no such thing as a 'clip', in PPro; there are only project items, and track items. 

Yes, the metadata effect relies on the project item's metadata. Track items have no specific metadata of their own, either XMP or PPro's private project metadata; all track items created from a given project item, have their parent project item's metadata. That's what motivated my suggestion to, instead of trying to use the metadata from the still image sequence 'aggregate project item', Dan might be more successful with a bazillion project items, each of which had its own (accurate) metadata.

[danw71857413]

Thank you Bruce I would like to try this: how do I "create a bazillion project items"?  I am fairly skilled with PPro but I am not clear on what you are proposing exactly but I'd like to give it a shot.  Thanks again!

[danw71857413]

Hi Bruce thank you for reaching out.  I have imported each JPG file as an individual image.  The first few JPGs also have an XMP Dublin Core "Description" field that is properly populated in each individual JPG.  I have applied the metadata effect to the first few images just to test that it works, but it does not.  Perhaps Premiere is looking at some other place for the metadata but I am unclear on how to resolve this.  Thank you again for your response!

[Bruce Bullis]

Frustrating! 
Send me an example .jpg (with valid metadata), and I'll play with it further.

[danw71857413]

Thanks Bruce, I have send you the requested JPG.  I have set the "Description" as Dublin Core within the JPG itself, as you will be able to see via a metadata viewer.