VSE: 'Jump to endpoint' function (screen.frame_jump) in metastrip uses project bounds instead of meta bounds #91403

New Issue

David Salvo · 2021-09-14T14:38:23+02:00

David Salvo commented

2021-09-14 14:38:23 +02:00

System Information
Operating system: Linux-5.4.0-84-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-13 23:08, hash: 9b0b78d58f
Worked: Unsure

Short description of error
Jump to endpoint/startpoint function in a metastrip seeks start/end of render range, not metastrip range. This function already adjusts to context when a preview exists (it seeks start/end of this range), and it would be expected that it would do the same in a metastrip (seeking the start of metastrip in particular would be a fairly common action).

Note: Potentially tricky in the case where there is a preview range set, but user is inside a metastrip, but I believe it should prioritize any preview bound(s) that are within the metastrip range, otherwise seek further until it hits the metastrip bound(s).

(This is related in essence to https://developer.blender.org/T90633)

Exact steps for others to reproduce the error

Create metastrip smaller than project/render range
Enter meta
Use 'Jump to endpoint' function in either direction -- it will skip past metastrip bounds all the way to the render range bounds (which are basically muted in a metastrip)

**System Information** Operating system: Linux-5.4.0-84-generic-x86_64-with-glibc2.31 64 Bits Graphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-13 23:08, hash: `9b0b78d58f` Worked: Unsure **Short description of error** Jump to endpoint/startpoint function in a metastrip seeks start/end of render range, not metastrip range. This function already adjusts to context when a preview exists (it seeks start/end of this range), and it would be expected that it would do the same in a metastrip (seeking the start of metastrip in particular would be a fairly common action). Note: Potentially tricky in the case where there is a preview range set, but user is inside a metastrip, but I believe it should prioritize any preview bound(s) that are _within_ the metastrip range, otherwise seek further until it hits the metastrip bound(s). (This is related in essence to https://developer.blender.org/T90633) **Exact steps for others to reproduce the error** - Create metastrip smaller than project/render range - Enter meta - Use 'Jump to endpoint' function in either direction -- it will skip past metastrip bounds all the way to the render range bounds (which are basically muted in a metastrip)

David Salvo commented

2021-09-14 14:38:23 +02:00

Added subscriber: @slinkeepie

Philipp Oeser commented

2021-09-14 14:51:19 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-09-14 14:51:19 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2021-09-14 14:51:19 +02:00

Probably has the same reasons than #90633 (VSE: "Frame all" inside metastrips uses global frame range instead of metastrip frame range) indeed, but will keep separate for now and confirm.

Richard Antalik commented

2021-10-07 07:41:32 +02:00

Added subscriber: @iss

Richard Antalik commented

2021-10-07 07:41:32 +02:00

Changed status from 'Confirmed' to: 'Archived'

Richard Antalik closed this issue

2021-10-07 07:41:32 +02:00

Richard Antalik commented

2021-10-07 07:41:32 +02:00

Issue here is that this is screen operator, not sequencer one so this is not related to #90633.

Will close this report as this is not a bug.

I have created patch D12774, but I am not very happy with implementation, but perhaps better than duplicating operator for sequencer only.

Issue here is that this is screen operator, not sequencer one so this is not related to #90633. Will close this report as this is not a bug. I have created patch [D12774](https://archive.blender.org/developer/D12774), but I am not very happy with implementation, but perhaps better than duplicating operator for sequencer only.

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

VSE: 'Jump to endpoint' function (screen.frame_jump) in metastrip uses project bounds instead of meta bounds #91403