Page MenuHome

Strip info doesn't use custom frame rate base
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 7
GPU: ASUS Strix Radeon Vega 64, Divider version: 19.4.1
CPU: Intel Core i7-5960X

Blender Version
Broken: 2.80, blender-2.80.0-git.cc600de6695a-windows64

Short description of error

The timecode in the strip info panel it doesn't consider the custom frame rate base (and only uses the FPS as a base).

Exact steps for others to reproduce the error

Related Objects

Event Timeline

Brecht Van Lommel (brecht) lowered the priority of this task from Needs Triage by Developer to Waiting for Developer to Reproduce.
Richard Antalik (ISS) lowered the priority of this task from Waiting for Developer to Reproduce to Confirmed, High.Jun 10 2019, 8:30 AM

I guess high prio for this.

The problem is not in the panel, but in the frames to SMPTE conversion.

@Peter Fog (tintwotin) What do you mean? There is correct conversion in the timeline, but that value is not used in the panel... Unless you mean that the panel does it's own calculations.
@Richard Antalik (ISS) On the subject of timecodes a while ago I made a T53661: Timecode placeholders suggestion, a poor one (before I knew that "This is a bug tracker").
But I feel that it makes sense here, as for example, the playhead jumping back and forth between 2 and 3 digits.


And whatever fix to show the 3rd digit on the start, end and duration will screw up the alignment...

If this is something you would like to work on I'd be more than happy to make it (look like) a proper papercut task. (Hopefully it's a Bug request)

@Christopher_Anderssarian
I would agree with :FFF format for frame regardless of framerate. Each time I look at strip length now, I have to think about the format. But according to https://en.wikipedia.org/wiki/SMPTE_timecode, the format is HH:MM:SS:FF, which we are violating already.

@Peter Fog (tintwotin) any thoughts about this?

I would agree with :FFF format for frame regardless of framerate.

Not what I had in mind (but good for a quick fix). That placeholder wouldn't be needed 99% of the time.

Keeping SMPTE (Full) TimeCode Style the way it is (or possibly adhering better to the standard...) and adding an adaptive Timecode Style, one that adds the placeholders automatically...