VSE 2.0: Media management #78990

New Issue

Sergey Sharybin · 2020-07-16T14:37:23+02:00

Sergey Sharybin commented

2020-07-16 14:37:23 +02:00

When working on a big project which consists of 10s of hours of video it is crucial to know what is used in the project.

A quick concept from the art team:

The final design and possible implementation still needs to be worked on, but the plan is to leverage the following ideas:

File browser is to become aware of any source of asset, not only about files on disk. This is a requirement for the asset management project, and can be used here as well to represent categorized media used or usable by the VSE.
VSE is already aware of scenes and movie clips, which are an ID in Blender terminology. This means that the media management is a minimal wrapper on top of the ID, and the sequencer uses those IDs in strip. Hopefully, this comes with minimal redesign of the VSE core.

When working on a big project which consists of 10s of hours of video it is crucial to know what is used in the project. A quick concept from the art team: ![vse_improvements_04.jpg](https://archive.blender.org/developer/F8699097/vse_improvements_04.jpg) The final design and possible implementation still needs to be worked on, but the plan is to leverage the following ideas: * File browser is to become aware of any source of asset, not only about files on disk. This is a requirement for the asset management project, and can be used here as well to represent categorized media used or usable by the VSE. * VSE is already aware of scenes and movie clips, which are an ID in Blender terminology. This means that the media management is a minimal wrapper on top of the ID, and the sequencer uses those IDs in strip. Hopefully, this comes with minimal redesign of the VSE core.

🚀 1

Sergey Sharybin commented

2020-07-16 14:37:23 +02:00

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

Sergey Sharybin commented

2020-07-16 14:37:23 +02:00

Added subscribers: @Sergey, @fsiddi, @iss, @dfelinto

tintwotin commented

2020-08-12 11:39:42 +02:00

Added subscriber: @tintwotin

tintwotin commented

2020-08-12 11:39:42 +02:00

A few notes on the mock up:

If the Clip Editor is to be used for preview of source material then give the playback performance a check-up, please. It seems to be much slower than the VSE).
How do you preview Scenes and Cameras(they should be in the media manager too?) in a 3D Viewer without switching the contents of the Sequencer?
Extraction and display(+sorting) of fps, resolution, aspect, embedded reelname and timecode stamps should be read already in the File Browser and carried over to the media manager etc. (in other words move away from the current lazy loading - where some of these elements only is read when the playhead is over the clip).
Proper media management would include (color+word)tagging, folder/bin organisation, drag and drop multiple files from File Browser and to Sequencer/Clip Editor.

A subpar workaround(which doesn't include a source preview monitor): As some of the media management functions are mirrored in the outliner, a workaround-ish media management through the Outliner could be done by allowing d'n d to from the outline and the file browser and the sequencer: So you could drag from File Browser into the Outliner scenes, drag from outliner into sequencer(movie, image, sound, cameras), by using a scenes+medias-view in the Outliner). And scenes would work as folders/bins(where batch creation of proxies could be done without having the material in the main edit sequence): https://www.youtube.com/watch?v=g1W7LHOhBx4

A few notes on the mock up: - If the Clip Editor is to be used for preview of source material then give the playback performance a check-up, please. It seems to be much slower than the VSE). - How do you preview Scenes and Cameras(they should be in the media manager too?) in a 3D Viewer without switching the contents of the Sequencer? - Extraction and display(+sorting) of fps, resolution, aspect, embedded reelname and timecode stamps should be read already in the File Browser and carried over to the media manager etc. (in other words move away from the current lazy loading - where some of these elements only is read when the playhead is over the clip). - Proper media management would include (color+word)tagging, folder/bin organisation, drag and drop multiple files from File Browser and to Sequencer/Clip Editor. A subpar workaround(which doesn't include a source preview monitor): As some of the media management functions are mirrored in the outliner, a workaround-ish media management through the Outliner could be done by allowing d'n d to from the outline and the file browser and the sequencer: So you could drag from File Browser into the Outliner scenes, drag from outliner into sequencer(movie, image, sound, cameras), by using a scenes+medias-view in the Outliner). And scenes would work as folders/bins(where batch creation of proxies could be done without having the material in the main edit sequence): https://www.youtube.com/watch?v=g1W7LHOhBx4

Nils-Erik commented

2020-08-19 03:00:00 +02:00

Added subscriber: @clayhands

Andy Cuccaro commented

2021-06-03 03:07:22 +02:00

Added subscriber: @AndyCuccaro

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE 2.0: Media management #78990