Page MenuHome

Sequencer: Invalid timecode values makes strip drawing a mess.
Open, Confirmed, LowPublic


System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build

Blender Version
Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-08 13:24, hash: rB81b68f7279cd
Worked: (optional)

Short description of error
When invalid values are used in the timecode panel the strips will become a mess.

Exact steps for others to reproduce the error
Add a movie strip.
Open the Sidebar - Timecode.
Play around with the sliding values.

Gif of the procedure and the bug:



Event Timeline

Is this new issue?
I mean it should be easy to fix, but not sure if I should look for what caused this.

Just checked 2.73. Same bug.

Sebastian Parborg (zeddb) triaged this task as Confirmed, Medium priority.

I don't know if changing the 'End' value to a label is a fix for the above mentioned bug?

But as shown in the gif in the bug report, it also includes the Strip & Hold Offset values. So maybe it's better to leave End as it was(as a know bug), until there is time for a proper fix, or if not, then use the alignment code from Playhead for the End value, so it won't be misaligned?

I don't know if changing the 'End' value to a label is a fix for the above mentioned bug?

Nope. It's quite easy to limit the value.
I will get to this eventually but this bug is super low priority

According to this comment it is a way to workaround that bug:

Campbell Barton (campbellbarton) raised the priority of this task from Confirmed, Medium to Confirmed, High.

These were internal variables for cutting strips and not meant to be exposed.

Editing these values can easily create an invalid state.

Further, these values are hard to understand.

Unless a fix is trivial, would remove these buttons for 2.8x release.

We could have an operator to reset these start/end cut values, eg: "Reset Cut Limits", which users can run if they need to set the limits back to the source strip.

The offset(hard/soft cut) values have been exposed as buttons in many years(without limits on invalid values). Here they are in Blender 2.72:

Campbell Barton (campbellbarton) lowered the priority of this task from Confirmed, High to Confirmed, Low.Jul 11 2019, 9:29 AM

You're right, (was looking at the edit strip panel which only has start frame & length).

The way they are presented makes them more prominent in 2.8.

Lowering priority since this issue isn't new in 2.8x.

So is the UI change with 'End' going to be rolled back for now?


Master is frozen.
only critical bugfixes are allowed

Knife-cut and Transform have checks to ensure invalid start/end cases don't happen.

Some buttons were exposed that allow this - which is unfortunate.

This case looks like a bug and isn't properly handled by tools & draw code.

Instead of using buggy/low quality code as an excuse to make this weakness more prominent, why not try and solve the problem?

Possible solutions:

  • Separate RNA properties to expose to the interface, frame_final_end_ui for example.
  • Add clamping to frame_final_end, then use a function strip.frame_final_set(start=a, end=b) so these values can be updated, or omitted to use the current value.

@Richard Antalik (ISS) Could this be added to a VSE To Do list here on