Investigate renaming the "Video Sequencer" editor #89266

Open
opened 2021-06-18 16:38:30 +02:00 by Aaron Carlisle · 26 comments
Member

For a long time, the video editing component of Blender has been referred to as the "Video Sequence Editor" later shorted to just "Video Sequencer".
However, this is slightly problematic as it is confusing with the "Sequencer" view type.
In the future, we may add different view types such as some sort of audio view or some sort of special color grading tooling.
To combat the potential confusion between the "Video Sequencer" editor and "Sequencer" view type, I propose that the editor be renamed to simply "Video Editor" which also complements "Image Editor"

For a long time, the video editing component of Blender has been referred to as the "Video Sequence Editor" later shorted to just "Video Sequencer". However, this is slightly problematic as it is confusing with the "Sequencer" view type. In the future, we may add different view types such as some sort of audio view or some sort of special color grading tooling. To combat the potential confusion between the "Video Sequencer" editor and "Sequencer" view type, I propose that the editor be renamed to simply "Video Editor" which also complements "Image Editor"
Author
Member

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

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

Added subscriber: @Blendify

Added subscriber: @Blendify
Aaron Carlisle changed title from Investigate renaming the "Video Sequence" editor to Investigate renaming the "Video Sequencer" editor 2021-06-18 16:39:41 +02:00

Added subscriber: @ckohl_art

Added subscriber: @ckohl_art

Added subscriber: @tintwotin

Added subscriber: @tintwotin

Editing unrendered(to disk) 3d/2d animation(Scene strips) is imo the unique selling point of the VSE, and the main reason for not using an external NLE. Calling it 'Video Editor', will neglect this feature. Softwares offering to let users organize rendered and unrendered material in to a story are referring to it ex. Sequencer, Timeline or Story Mode.

There are several odd names in the VSE:

My personal wish for the vse is that it becomes the hub where all other elements gets assembled into storytelling, so a "Story hub", but that doesn't sound that catchy either. Maybe we could call it Suzanne?

Another approach is: could we call the Sequencer View Type something different? Personally, I do not have a problem with Sequencer, in the meaning a sequence of strips, but it is actually a timeline. Like all editors in Blender with a playhead also have a timeline, however the "timeline" word is owned by the Timeline editor, so unless the Timeline editor is called something which is along the lines of what it actually is, ex. Playback Controller, Player etc. the Sequencer view type can't be called what it actually is. So that's a bit dead-end too.

Editing unrendered(to disk) 3d/2d animation(Scene strips) is imo the unique selling point of the VSE, and the main reason for not using an external NLE. Calling it 'Video Editor', will neglect this feature. Softwares offering to let users organize rendered and unrendered material in to a story are referring to it ex. Sequencer, Timeline or Story Mode. There are several odd names in the VSE: - Why are [Video ]] strips called [[ https:*dictionary.cambridge.org/dictionary/english/movie | Movie ](https:*dictionary.cambridge.org/dictionary/english/video) strips? - Why are [Audio ]] strips called [[ https:*dictionary.cambridge.org/dictionary/english/sound | Sound ](https:*dictionary.cambridge.org/dictionary/english/audio) strips? - In the source code, why are [channels ]] called machine, and not [[ https:*dictionary.cambridge.org/example/english/audio-track | tracks ](https:*dictionary.cambridge.org/dictionary/english/channel)? - Why is the "[Current Frame ]]" not called [[ https:*glosbe.com/en/en/playhead | playhead ](https:*glosbe.com/en/en/current%20frame)? - In the source code, why is the word "sequence" used as synonym for "strip"? In Blender terminology the users are editing strips. So the really dry naming would be a "Strip Editor", however the NLA is also editing "strips" and "sequences". My personal wish for the vse is that it becomes the hub where all other elements gets assembled into storytelling, so a "Story hub", but that doesn't sound that catchy either. Maybe we could call it Suzanne? Another approach is: could we call the Sequencer View Type something different? Personally, I do not have a problem with Sequencer, in the meaning a sequence of strips, but it is actually a timeline. Like all editors in Blender with a playhead also have a timeline, however the "timeline" word is owned by the Timeline editor, so unless the Timeline editor is called something which is along the lines of what it actually is, ex. Playback Controller, Player etc. the Sequencer view type can't be called what it actually is. So that's a bit dead-end too.
Author
Member

Editing unrendered(to disk) 3d/2d animation(Scene strips) is imo the unique selling point of the VSE, and the main reason for not using an external NLE.

While this feature is unique I think for the most part the community sees it as a video editor, we have a "Video Editing".

While a key feature, I do not think "Storyhub" is the defining feature of the Sequencer, most people will use it as a normal NLE.
I think calling the editor "Video Editor" will promote development in making it a great tool to edit videos.
To promote the storyboarding aspect of the Video Sequencer we can create a dedicated "Storyboarding" workspace.
We could also add a storyboard view type which could allow you to easily sketch with the grease pencil,
add notes, add scene strips, add shot descriptions, add adjust the sequencing of the animation.

There are several odd names in the VSE:

I think all the points you mentioned here are good points and are things that should be changed.

> Editing unrendered(to disk) 3d/2d animation(Scene strips) is imo the unique selling point of the VSE, and the main reason for not using an external NLE. While this feature is unique I think for the most part the community sees it as a video editor, we have a "Video Editing". While a key feature, I do not think "Storyhub" is the defining feature of the Sequencer, most people will use it as a normal NLE. I think calling the editor "Video Editor" will promote development in making it a great tool to edit videos. To promote the storyboarding aspect of the Video Sequencer we can create a dedicated "Storyboarding" workspace. We could also add a storyboard view type which could allow you to easily sketch with the grease pencil, add notes, add scene strips, add shot descriptions, add adjust the sequencing of the animation. > There are several odd names in the VSE: I think all the points you mentioned here are good points and are things that should be changed.

The workspace is already called "Video Editor". Renaming the editor will not promote it, if you really want to promote it, it should have it's own tab in the General workspace:
{F10181274,size=full}

As I understand it the editors shouldn't be named the same as the workspaces? Ex. Compositor vs. Compositing. Which is properly why the workspace is called "Video Editor" and the editor is called "Video Sequencer".

The workspace is already called "Video Editor". Renaming the editor will not promote it, if you really want to promote it, it should have it's own tab in the General workspace: {[F10181274](https://archive.blender.org/developer/F10181274/image.png),size=full} As I understand it the editors shouldn't be named the same as the workspaces? Ex. Compositor vs. Compositing. Which is properly why the workspace is called "Video Editor" and the editor is called "Video Sequencer".

Removed subscriber: @ckohl_art

Removed subscriber: @ckohl_art

Added subscriber: @Miadim

Added subscriber: @Miadim

Following the logic of "Compositor" VS "Composisting" maybe it should be "Video Editor" and "Video Editing" and to be put in the General layout.

I agree "Video Sequencer" isn't very explicit.

Following the logic of "Compositor" VS "Composisting" maybe it should be "Video Editor" and "Video Editing" and to be put in the General layout. I agree "Video Sequencer" isn't very explicit.
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

I vaguely remember people asking to call it "Video Editor" about a million years ago. At that time it was a definite "No" in that we didn't want to call it that because it fulfilled so little of what users would expect of a video editor. The state of it at the time was such that we just didn't want to say that "Video Editing" was one of Blender's functions because people would giggle. So basically "Video Sequence Editor" was chosen to avoid comparisons.

But times have changed and it has come a very long way. It is probably time to call it "Video Editor" now.

I vaguely remember people asking to call it "Video Editor" about a million years ago. At that time it was a definite "No" in that we didn't want to call it that because it fulfilled so little of what users would expect of a video editor. The state of it at the time was such that we just didn't want to say that "Video Editing" was one of Blender's functions because people would giggle. So basically "Video Sequence Editor" was chosen to avoid comparisons. But times have changed and it has come a very long way. It is probably time to call it "Video Editor" now.

Added subscriber: @HUSCH

Added subscriber: @HUSCH

This seems logical and in line with the other editors (image editor, shader editor, UV editor, movie clip editor). Let's use the term Video Editing for the workspace (also in line with some other e.g. UV editing, shading) and global workflow.

This seems logical and in line with the other editors (image editor, shader editor, UV editor, movie clip editor). Let's use the term Video Editing for the workspace (also in line with some other e.g. UV editing, shading) and global workflow.

Added subscribers: @ideasman42, @pablovazquez

Added subscribers: @ideasman42, @pablovazquez

One thing to keep in mind, is that renaming things in the UI typically also means renaming everything with that name in the code base.

So if the "sequencer" word is going to be removed from the VSE UI entirely, a search in the code base for the word "sequence" results in 5036 hits in 240 files, minus the use in the image sequence context, that's a lot of stuff to rename. And after the renaming, more than 160 add-ons needs to be updated or given up on: https://blenderartists.org/t/video-sequence-editor-news-add-ons/1188770
So is a big decision. I wonder what opinions @pablovazquez @ideasman42 have about this?

One thing to keep in mind, is that renaming things in the UI typically also means renaming everything with that name in the code base. So if the "sequencer" word is going to be removed from the VSE UI entirely, a search in the code base for the word "sequence" results in 5036 hits in 240 files, minus the use in the image sequence context, that's a lot of stuff to rename. And after the renaming, more than 160 add-ons needs to be updated or given up on: https://blenderartists.org/t/video-sequence-editor-news-add-ons/1188770 So is a big decision. I wonder what opinions @pablovazquez @ideasman42 have about this?

However, this is slightly problematic as it is confusing with the "Sequencer" view type.

Another approach is: could we call the Sequencer View Type something different? Personally, I do not have a problem with Sequencer, in the meaning a sequence of strips, but it is actually a timeline. Like all editors in Blender with a playhead also have a timeline, however the "timeline" word is owned by the Timeline editor, so unless the Timeline editor is called something which is along the lines of what it actually is, ex. Playback Controller, Player etc. the Sequencer view type can't be called what it actually is.

{F10187572,size=full}

> However, this is slightly problematic as it is confusing with the "Sequencer" view type. Another approach is: could we call the Sequencer View Type something different? Personally, I do not have a problem with Sequencer, in the meaning a sequence of strips, but it is actually a timeline. Like all editors in Blender with a playhead also have a timeline, however the "timeline" word is owned by the Timeline editor, so unless the Timeline editor is called something which is along the lines of what it actually is, ex. Playback Controller, Player etc. the Sequencer view type can't be called what it actually is. {[F10187572](https://archive.blender.org/developer/F10187572/image.png),size=full}

Added subscriber: @AndreaMonzini

Added subscriber: @AndreaMonzini

Hello, when i search info/tutorial/news about the "Video Sequencer" actually i search "VSE" as Video Sequence Editor.
Even the manual talk about the VSE that at this point is quite "iconic".
So if Video Sequencer is confusing i would revert to the old VSE but as a new "Video Scene Editor"... always VSE !

I also agree with Peter as the VSE is used also for realtime scene strips editing so it should not compared to traditional NLE.

Then i think that "Video Editor" would be confused with the "Movie Clip Editor", what is the difference between "Video" and "Movie"? ...
Ideally for the future we should think a convergence of VSE and Movie Clip Editor, adding tracking and masking modes to the VSE.

I would vote to keep the iconic name VSE but as "Video Scene Editor" because this editor can edit Videos but also realtime Scenes.
Just my personal opinion.

Hello, when i search info/tutorial/news about the "Video Sequencer" actually i search "VSE" as Video Sequence Editor. Even the manual talk about the VSE that at this point is quite "iconic". So if Video Sequencer is confusing i would revert to the old VSE but as a new "Video Scene Editor"... always VSE ! I also agree with Peter as the VSE is used also for realtime scene strips editing so it should not compared to traditional NLE. Then i think that "Video Editor" would be confused with the "Movie Clip Editor", what is the difference between "Video" and "Movie"? ... Ideally for the future we should think a convergence of VSE and Movie Clip Editor, adding tracking and masking modes to the VSE. I would vote to keep the iconic name VSE but as "Video Scene Editor" because this editor can edit Videos but also realtime Scenes. Just my personal opinion.
Author
Member

Even the manual talk about the VSE that at this point is quite "iconic".

There were a few references to VSE in the manual but these have since been renamed in rBM8196.

Then i think that "Video Editor" would be confused with the "Movie Clip Editor", what is the difference between "Video" and "Movie"? ...

There were already plans for 2.8x to remain the Movie Clip Editor to "Motion Tracking Editor" see #54744.

> Even the manual talk about the VSE that at this point is quite "iconic". There were a few references to VSE in the manual but these have since been renamed in rBM8196. > Then i think that "Video Editor" would be confused with the "Movie Clip Editor", what is the difference between "Video" and "Movie"? ... There were already plans for 2.8x to remain the Movie Clip Editor to "Motion Tracking Editor" see #54744.

Added subscriber: @iss

Added subscriber: @iss

I think that terms "Video Editor" and "Video Sequence Editor" are completely synonymous in eyes of most people, So I won't object to such change. It's true, that VSE is not only video editor, but most existing "video editors" are also not limited to editing videos, so I don't see problems here.

In #89266#1180488, @tintwotin wrote:

However, this is slightly problematic as it is confusing with the "Sequencer" view type.

Another approach is: could we call the Sequencer View Type something different?

I would agree in renaming "Sequencer" view to "Timeline" or equivalent name. Sequence editor implies editing of a sequence. Sequencer implies compositing sequences. VSE does or can do both things, but it's used mostly for sequencing. I still think that term "Sequencer" is not fully descriptive and "Timeline" would be good overarching term.

I think that terms "Video Editor" and "Video Sequence Editor" are completely synonymous in eyes of most people, So I won't object to such change. It's true, that VSE is not only video editor, but most existing "video editors" are also not limited to editing videos, so I don't see problems here. > In #89266#1180488, @tintwotin wrote: >> However, this is slightly problematic as it is confusing with the "Sequencer" view type. > > Another approach is: could we call the Sequencer View Type something different? I would agree in renaming "Sequencer" view to "Timeline" or equivalent name. Sequence editor implies editing of a sequence. Sequencer implies compositing sequences. VSE does or can do both things, but it's used mostly for sequencing. I still think that term "Sequencer" is not fully descriptive and "Timeline" would be good overarching term.

Wouldn't the term timeline be confusing given the timeline space type?

Wouldn't the term timeline be confusing given the timeline space type?

In #89266#1190152, @ideasman42 wrote:
Wouldn't the term timeline be confusing given the timeline space type?

If it would be confusing, then I would look for equivalent term that is not confusing. If none can be found, "Sequencer" View name is probably OK. Purpose of component name is to communicate it's purpose. I think that at least 90% of VSE users calls "Sequencer" view a "timeline" or "sequencer timeline" already. Or see function draw_timeline_seq() for example.

Not sure how to evaluate confusion level, but I think this would be very minor issue if at all. Which I would assume is same for "Sequencer" view vs Video Sequencer, so perhaps I don't see where this issue exhibits mostly.

> In #89266#1190152, @ideasman42 wrote: > Wouldn't the term timeline be confusing given the timeline space type? If it would be confusing, then I would look for equivalent term that is not confusing. If none can be found, "Sequencer" View name is probably OK. Purpose of component name is to communicate it's purpose. I think that at least 90% of VSE users calls "Sequencer" view a "timeline" or "sequencer timeline" already. Or see function `draw_timeline_seq()` for example. Not sure how to evaluate confusion level, but I think this would be very minor issue if at all. Which I would assume is same for "Sequencer" view vs Video Sequencer, so perhaps I don't see where this issue exhibits mostly.

@ideasman42
From above:

In #89266#1180488, @tintwotin wrote:

However, this is slightly problematic as it is confusing with the "Sequencer" view type.

Another approach is: could we call the Sequencer View Type something different? Personally, I do not have a problem with Sequencer, in the meaning a sequence of strips, but it is actually a timeline. Like all editors in Blender with a playhead also have a timeline, however the "timeline" word is owned by the Timeline editor, so unless the Timeline editor is called something which is along the lines of what it actually is, ex. Playback Controller, Player etc. the Sequencer view type can't be called what it actually is.

{F10187572,size=full}

@ideasman42 From above: > In #89266#1180488, @tintwotin wrote: >> However, this is slightly problematic as it is confusing with the "Sequencer" view type. > > Another approach is: could we call the Sequencer View Type something different? Personally, I do not have a problem with Sequencer, in the meaning a sequence of strips, but it is actually a timeline. Like all editors in Blender with a playhead also have a timeline, however the "timeline" word is owned by the Timeline editor, so unless the Timeline editor is called something which is along the lines of what it actually is, ex. Playback Controller, Player etc. the Sequencer view type can't be called what it actually is. > > {[F10187572](https://archive.blender.org/developer/F10187572/image.png),size=full}

Added subscriber: @AndyCuccaro

Added subscriber: @AndyCuccaro
Richard Antalik added this to the Video Sequencer project 2023-02-09 21:00:44 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
10 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#89266
No description provided.