Page MenuHome

Video Sequence Editor (VSE) Module
Open, NormalPublic

Description

Design task to coordinate the VSE (video sequence editor) project.

This is a curated list of items agreed on by module owners.

Order of importance:

  • Very Important - These we should handle before the next release.
  • Somewhat Important - These issues would be nice to do as soon as possible.
  • Less Important - Extra polish, nice to have.
  • ? Incomplete - Tasks needing more details before implementing.

Long Term Projects

Development may span multiple release cycles.

Medium Term Projects

Development should be possible in a single release cycle.

Paper Cuts

Small improvements and polish.

Details

Type
Design

Event Timeline

I came across this old patch: https://developer.blender.org/T6882
This patch adds the ability to select the adjoining handles on adjacent strips with a single click.

When working on the VSE Reworked project, the ability to easily select adjoined handles for rolling adjoined cuts wasn't possible through python. This type of edit is as common as ex. sliding the contents of a strip, so it definitely belongs in the VSE toolbox. So I would suggest it was added to the list above. I don't know if I can or should just add it to the list? @Richard Antalik (ISS) What would you prefer, as procedure for adding things to the list?

Brecht Van Lommel (brecht) changed the edit policy from "Custom Policy" to "BF Blender (Project)".EditedMay 27 2019, 9:40 AM

Only module owners should add things to the list, which they take responsibility to review and accept.

I'd like to start contributing to the VSE itself instead of working on add-ons. But it's still not clear what the target is for the project, what are the intended or supported use cases, and which contributions would be welcome or not.

Who are the target uses or users? What's the scope of the project?

I can help with rewriting operators to Python, as an exercise to work with the C codebase. I'd gladly help to clean up and add features proposed by @Peter Fog (tintwotin), splitting them in individual patches to make review manageable.

Could you confirm it's okay to add new operators in Python? If not, I can work in C. But if we can work in Python, we're at least a few devs who'd like to contribute to the VSE.

As I said on the chat, I'm ready to get started contributing, I would just like to know that I can work on something that's wanted by the Blender team or as part of the project.

@Richard Antalik (ISS) each item added should be a task.

Otherwise this task risks becoming a forum thread where people ask about items in this list which aren't explained or referenced elsewhere (as has already happened).

@Richard Antalik (ISS) each item added should be a task.
Otherwise this task risks becoming a forum thread where people ask about items in this list which aren't explained or referenced elsewhere (as has already happened).

I will add them. I guess I could add diffs where the work is already in progress?

Richard Antalik (ISS) updated the task description. (Show Details)

There is no need to add diff's, add the tasks that describe whats planned.

For example, say someone wants to work on or ask questions about SIMD / GPU image processing library or Rewrite most operators in python - there is currently no details about these tasks, the motivation for adding them, possible down sides... etc.

Richard Antalik (ISS) updated the task description. (Show Details)