VSE: "Frame all" inside metastrips uses global frame range instead of metastrip frame range #90633

Closed
opened 2021-08-12 13:54:45 +02:00 by David Salvo · 13 comments

System Information
Operating system: Linux-5.4.0-80-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-08-09 23:26, hash: cb7b4064d6
Worked: Unsure

Short description of error
Using "Frame all" function when tabbed into metastrip will expand view to the global view, not to the bounds of the metastrip itself, which would be expected since view of all outside strips disappears and metastrip range is given render area shading.

Exact steps for others to reproduce the error

**System Information** Operating system: Linux-5.4.0-80-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-08-09 23:26, hash: `cb7b4064d6` Worked: Unsure **Short description of error** Using "Frame all" function when tabbed into metastrip will expand view to the global view, not to the bounds of the metastrip itself, which would be expected since view of all outside strips disappears and metastrip range is given render area shading. **Exact steps for others to reproduce the error** - Create metastrip with range smaller than global strip range - Enter metastrip - Activate "Frame all" view function - Framed view will be same as if you were outside the metastrip [frame-all-in-metastrip-frames-whole-project-range.blend](https://archive.blender.org/developer/F10278631/frame-all-in-metastrip-frames-whole-project-range.blend)
Author

Added subscriber: @slinkeepie

Added subscriber: @slinkeepie
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

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

Can confirm, makes more sense to frame the meta bounds.
Borderline to call this a bug, but will confirm for now.

Can confirm, makes more sense to frame the meta bounds. Borderline to call this a bug, but will confirm for now.

Added subscriber: @iss

Added subscriber: @iss

This is correct behavior, but I think, that for metastrip this could be changed, since it is useful to zoom to it's range.

This is correct behavior, but I think, that for metastrip this could be changed, since it is useful to zoom to it's range.

Added subscriber: @Aidan_Davey

Added subscriber: @Aidan_Davey

Added subscriber: @beco

Added subscriber: @beco

Hi, I would love to work on this if nobody else has started yet!

Hi, I would love to work on this if nobody else has started yet!

@beco I don't think anybody did so feel fere.

@beco I don't think anybody did so feel fere.
Author

In #90633#1224063, @beco wrote:
Hi, I would love to work on this if nobody else has started yet!

Cheers Andrea!

> In #90633#1224063, @beco wrote: > Hi, I would love to work on this if nobody else has started yet! Cheers Andrea!
Andrea Beconcini self-assigned this 2021-10-23 18:22:57 +02:00

This issue was referenced by 82ae7b990a

This issue was referenced by 82ae7b990acfa2c522895322eb052b90f0c3b83a

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sign in to join this conversation.
6 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: blender/blender#90633
No description provided.