2025-04-15 Sequencer meeting notes

Meetings
1

Attendees

  • Thomas Dinges
  • Aras Pranckevičius
  • Richard Antalik
  • John Kiril Swenson
  • Sebastian Parborg

Notes

  • Richard:

    • Created WIP PR for scene strip invalidation #136974. Has some issues to solve, but in general it works
    • Landed tab filtering for properties editor #115624. It is now possible to move strip properties to this editor and reorganize VSE workspace

  • John:

    • Landed Blade tool cursor #136749
    • Landed improvements to Slip operator #137072
      • Accumulative precision mode, Cursor wrapping, content clamping, reorganized header and refactored operator code.
    • Next plans to work on Split operator improvements and constant zoom in timeline when resizing the editor

  • Sebastian worked on audio subsystem improvements

  • Aras plans to visit HQ to discuss VSE cache simplification and hardware acceleration of image processing

Practical Info

This is a fortnightly video chat meeting for planning and discussion of VFX & Video in Blender. Any contributor (developer, UI/UX designer, writer, …) working on these areas in Blender is welcome to join and add proposed items to the agenda.

For users and other interested parties, we ask to read the meeting notes instead so that the meeting can remain focused.

6 Likes
2

Is this only just so strip properties can be displayed on the Properties editor or does it serve other purposes? For what other workflows would/could it be used?

3

Yes pretty much. There are other motivating factors, like the fact, that combined sequencer/preview editor mode is causing design issues and we would like to resolve these by not having this editor mode.

Personally I work with as small timeline editor as possible, where I can see ~4 strip properties all at once which is not great. Having these in another editor that can be 80% of screen height would be really really nice.

1 Like
4

I must admit, this argument does not make sense to me at all. Having VSE strip properties in the general properties does not solve the problems that the Sequencer/Preview mode solves, as it doesn’t combine Sequencer and the Preview sidebar content in one sidebar, and it doesn’t collect Sequencer and Preview menus in one menu where there is enough vertical height to always open the ever expanding VSE menus in the same direction. All NLEs out there have the menus on top and not just in the timeline area. Imagine, the 3D View having all it’s main menus in the lower 1/3 of the screen? That’s pre 2.49 UI design.

Having the general Properties exposed in the Video Editing workspace is also exposing a lot of redundant stuff for the video editing needs. The Video Editing workspace has a rendering tab. So, it is already easily accessible.

Removing it from the Video Editing workspace, the chosen resolution and fps, should be optionally exposed on the right side of the statusbar. The VSE render settings should be exposed in a pop-up File Browser sidebar, when exporting, like the audio export options.

And the Story Tools workspace mock-up doesn’t even leave space for the Properties area. Same thing will happen with the Video Editing workspace if proper 3 point editing with a source and a program preview monitor is implemented as it is industry standard.

The only design issue the sequencer/preview editor mode introduces is that each mode needs a menu of it’s own. Accessing Preview related operators in a Preview menu shouldn’t be hard to comprehend for users, just like a Text menu lets the user access text related options. Or the Compositor having the Preview(Backdrop) integrated in the same editor. Having the Preview integrated in the Sequencer is a problem blown out of proportions, and exposing some VSE properties in the general properties will not solve that.

1 Like