Strip info doesn't use custom frame rate base #65398

New Issue

ChristopherAnderssarian · 2019-06-01T16:25:27+02:00

2019-06-01 16:25:27 +02:00

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

Demo.blend

**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** ![1.PNG](https://archive.blender.org/developer/F7082057/1.PNG) [Demo.blend](https://archive.blender.org/developer/F7082060/Demo.blend)

ChristopherAnderssarian commented

2019-06-01 16:25:27 +02:00

Added subscriber: @ChristopherAnderssarian

Richard Antalik was assigned by Brecht Van Lommel

2019-06-02 00:47:53 +02:00

Richard Antalik commented

2019-06-10 08:30:11 +02:00

I guess high prio for this.

tintwotin commented

2019-06-10 10:13:16 +02:00

Added subscriber: @tintwotin

tintwotin commented

2019-06-10 10:13:16 +02:00

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

ChristopherAnderssarian commented

2019-06-10 11:28:06 +02:00

@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.
@iss On the subject of timecodes a while ago I made a #53661 (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)

@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. @iss On the subject of timecodes a while ago I made a #53661 (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. ![movig.PNG](https://archive.blender.org/developer/F7097348/movig.PNG) 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*)

Richard Antalik commented

2019-06-11 23:17:58 +02:00

@ChristopherAnderssarian
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.

@tintwotin any thoughts about this?

@ChristopherAnderssarian 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. @tintwotin any thoughts about this?

ChristopherAnderssarian commented

2019-06-11 23:40:29 +02:00

In #65398#699619, @iss wrote:
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...

> In #65398#699619, @iss wrote: > 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...

blender-admin commented

2019-06-19 19:49:37 +02:00

This issue was referenced by da83f70754

This issue was referenced by da83f70754b6e5eb6d96b94b0d1d554bdb9120fd

Richard Antalik commented

2019-06-19 19:53:18 +02:00

Changed status from 'Open' to: 'Resolved'

Richard Antalik closed this issue

2019-06-19 19:53:18 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Strip info doesn't use custom frame rate base #65398