Metadata & timecode Continues to count up on held frames

[skydog_3487]

Summary:

When Metadata & Timecode effect reads clip timecode and encounters a held frame it continues counting up rather than displaying the frame number of the held frame.

Steps to reproduce:
1. Add transparent video layer to v2. Add the Metadata & Timecode effect.
2. In the effect Controls Panel set "Line 1: Metadata" to "Source Timecode" or "Clip Timecode." Choose either "Top Clip" or V1 for Source Track
3. Add a video file under the transparent video on v1.
4. Right click on the video on v1 “Add Frame Hold” and play the clip

What should have happened:

With the the old timecode effect, when using "Timecode Source: Clip" it would read the TC of the media and if it came to a would simply hold that frame number, and resume counting once the clip continued. (So if I have a five frame clip and held frame 3 for 3 extra frames it would count: 1, 2, 3, 3, 3, 3, 4, 5). I would expect this same functionality with the updated effect.

What actually happens:

The new Metadata and Timecode Effect continues counting up rather than reading the timecode (so using the example above we would get 1, 2, 3, 4, 5, 6, 4, 5).

Specs:

Premiere Pro: v 23.6.7 (Build 1), OS: Windows 11 Enterprise (version 10.0.22631 Build 22631), Processor: Intel Xeon Gold 6246R CPU @ 3.40GHz, 3392 Mhz, 16 Cores GPU: NVIDIA Quadro RTX 5000 RAM: 96.0 GB

[R Neil Haugen]

First, you list being on 23.x, and ... at the moment, we are at the probably last 24.x build. 25.x will be the 'current' shipping version as of 14 October, first day of Adobe MAX.

So you're listing this almost two series out of date. What is happening on the public beta 25.x series would be more useful.

[Mitch W]

Hi Skydog,
Can you explain this a bit more? With the old Timecode effect, I couldn't target a track like I can with the Metadata & Timecode effect, so placing the Timecode effect on Transparent Video in V2 won't work in the same way. I can place the Timecode effect directly on the clip in V1 but if I add a hold frame, the Timecode effect continues counting normally over the hold frame area. It does this whether I've selected 'Clip' or 'Media' as the Timecode Source for the effect. The Timecode effect never displays the same timecode value for every frame of the frame hold. To me, it appears that the old Timecode effect and the new Metadata & Timecode effect behave very similarly in that regard.
What have I got wrong here? 

[skydog_3487]

Hey Mitch,

Thanks for getting back to me.

I’ve created a very basic timeline so you can see how I’m applying the effects:

https://chuckshare.s3.amazonaws.com/Copied_Timecode_Overlay_Test.zip

Here is the output from that project. You can download this video from the vimeo page if you want to frame by frame it. If you notice the freeze is at frame 208. In the first it holds 208 for 6 frames and then moves on to 209 once the playback resumes. However on the Metadata and Timecode Effect it counts up to 213 (through the hold frames) and then jumps back to 208 when motion begins again:

https://vimeo.com/1017763969/47d1bb51b0?share=copy


Here is how it is laid out:

V2: Transparent video with effect.
V1:Video clip

Here are the settings I’m using for each effect:

TIMECODE
Position: 960 540
Size: 15%
Opacity: 40%
Field symbol: checked
Format: Frames
Timecode Source: Media
Time Display: 24
Offset: 1
Starting Timecode: Option Grayed Out
Label Text: None
Source Track: Video 1

METADATA & TIMECODE
Size: 15%
Opacity: 40%

Line 1
Metadata: Source Timecode
Position: 875.1 995.1
Size: 100
Metadata Label: Deselected
Source Track: Top Clip
Source Track Label: Grayed out
Field Symbol: Deselected
Format: Frames
Time Display: Grayed Out
Offset: +00:00:00:01
Starting Timecode: Grayed out

Line 2-5
Metadata: None

-- 
Cheers,
Chuck

[Mitch W]

Ah! I see which step I missed now. Okay, I'll get this bug logged. Thanks for the project and detailed steps to repro.

[R Neil Haugen]

Thanks for posting back, and doing such a good clean job. That's so necessary for getting real bugs fixed. Too many simply say "it's broke, fix it" ... which if the devs can't replicate it, is useless.

Your posts have been very useful. As another user, thank you!

[Kevin-Monahan]

Updating the status of this bug report.