Video Sequence Editor (Sequencer) Module #64682

Design task to coordinate the VSE (video sequence editor) project. This is a curated list of items agreed on by module owners.

Important links:

Order of importance:

{icon circle color=red} Very Important - These we should handle before the next release.
{icon circle color=yellow} Somewhat Important - These issues would be nice to do as soon as possible.
{icon circle color=green} Less Important - Extra polish, nice to have.
? Incomplete - Tasks needing more details before implementing.

Long Term Projects

Development may span multiple release cycles.

? #65720 (Fast image processing library)

Medium Term Projects

Development should be possible in a single release cycle.

{icon circle color=red} #65432 (VSE: Disk cache)
{icon circle color=yellow} #65724 (VSE operators rework)
{icon circle color=yellow} #59540 (VSE timeline manipulation API)
? #65719 (VSE timeline import / export)

Paper Cuts

Small improvements and polish.

{icon circle color=green} #65458 (In the VSE Preview - Text "X & Y" alignments are not working correctly)
{icon circle color=yellow} #57976 (VSE, marker area is invisibly blocking the strips)
{icon circle color=yellow} #54395 (VSE Edit Strip - Original Dimensions shows Proxy Dimensions)
{icon circle color=yellow} #59954 (View all Sequences doesn't show all sequences)
{icon circle color=yellow} #54273 (Large images gets cropped when downscaled in VSE)
{icon circle color=yellow} #51828 (VSE Proxy smaller than 100% produces wrong results when using input Crop or Offset for movie strip)
{icon circle color=yellow} #51077 (Generated movie strip proxy files are never used)
{icon circle color=yellow} #36263 (Pasted strip doesnt have F-Curve keyframes from the original)

Design task to coordinate the VSE (video sequence editor) project. This is a curated list of items agreed on by module owners. Important links: * [Bugs ](https://developer.blender.org/maniphest/query/.10PQctE7l4V) * [Known Issues ](https://developer.blender.org/maniphest/query/3rhA9zNd10G5) * [Unclassified Reports ](https://developer.blender.org/maniphest/query/2ZbkIN0QqKeS) Order of importance: - {icon circle color=red} **Very Important** - *These we should handle before the next release.* - {icon circle color=yellow} **Somewhat Important** - *These issues would be nice to do as soon as possible.* - {icon circle color=green} **Less Important** - *Extra polish, nice to have.* - `?` **Incomplete** - *Tasks needing more details before implementing.* # Long Term Projects Development may span multiple release cycles. - `?` #65720 (Fast image processing library) # Medium Term Projects Development should be possible in a single release cycle. - {icon circle color=red} #65432 (VSE: Disk cache) - {icon circle color=yellow} #65724 (VSE operators rework) - {icon circle color=yellow} #59540 (VSE timeline manipulation API) - `?` #65719 (VSE timeline import / export) # Paper Cuts Small improvements and polish. - {icon circle color=green} #65458 (In the VSE Preview - Text "X & Y" alignments are not working correctly) - {icon circle color=yellow} #57976 (VSE, marker area is invisibly blocking the strips) - {icon circle color=yellow} #54395 (VSE Edit Strip - Original Dimensions shows Proxy Dimensions) - {icon circle color=yellow} #59954 (View all Sequences doesn't show all sequences) - {icon circle color=yellow} #54273 (Large images gets cropped when downscaled in VSE) - {icon circle color=yellow} #51828 (VSE Proxy smaller than 100% produces wrong results when using input Crop or Offset for movie strip) - {icon circle color=yellow} #51077 (Generated movie strip proxy files are never used) - {icon circle color=yellow} #36263 (Pasted strip doesnt have F-Curve keyframes from the original)

Added subscribers: @ideasman42, @mont29, @dfelinto, @Sergey, @brecht

Added subscriber: @tintwotin

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? @iss What would you prefer, as procedure for adding things to the list?

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

There is no content yet.

Added subscriber: @GDQuest

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 @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.

@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).

In #64682#691215, @ideasman42 wrote:
@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?

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.

Added subscriber: @T.R.O.Nunes

Added subscriber: @Pipeliner

Added subscriber: @AndreaMonzini

This comment was removed by @tintwotin

Please don't use this task for discussion.

Added subscriber: @LucianoMunoz

Added subscriber: @Bearcat

Added subscriber: @mendio

Added subscriber: @avantcontra

Added subscriber: @c2ba

Added subscriber: @PhilippeCrassous

Added subscriber: @AndyCuccaro

Added subscriber: @Kdaf

Added subscriber: @gasilvaj

Added subscriber: @MarceloFreitas

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Video Sequence Editor (Sequencer) Module #64682

Long Term Projects

Medium Term Projects

Paper Cuts