VSE: In Multicam all strips gets white outline #92105

New Issue

tintwotin · 2021-10-11T09:22:03+02:00

tintwotin commented

2021-10-11 09:22:03 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59

Blender Version
Broken: version: 3.0.0 Alpha, branch: master (modified), commit date: 2021-10-11 04:33, hash: bdd2a7f466

Short description of error
All channels/strips get a white active strip outline when a multicam strip is selected.

Open this .blend file:
VSE_MultiCam.blend

Notice that all previews have a white active strip outline, though it's only the multicam strip selected:
{F10961426,size=full}

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master (modified), commit date: 2021-10-11 04:33, hash: `bdd2a7f466` **Short description of error** All channels/strips get a white active strip outline when a multicam strip is selected. Open this .blend file: [VSE_MultiCam.blend](https://archive.blender.org/developer/F10961456/VSE_MultiCam.blend) Notice that all previews have a white active strip outline, though it's only the multicam strip selected: {[F10961426](https://archive.blender.org/developer/F10961426/image.png),size=full}

tintwotin commented

2021-10-11 09:22:03 +02:00

Added subscriber: @tintwotin

Pratik Borhade commented

2021-10-11 11:30:42 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-10-11 11:32:19 +02:00

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

tintwotin commented

2021-10-26 08:44:49 +02:00

Changed status from 'Confirmed' to: 'Archived'

tintwotin closed this issue

2021-10-26 08:44:49 +02:00

tintwotin commented

2021-10-26 08:44:49 +02:00

As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this report for now.

Philipp Oeser commented

2021-10-26 09:30:43 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-10-26 09:30:43 +02:00

Changed status from 'Archived' to: 'Confirmed'

Philipp Oeser reopened this issue

2021-10-26 09:30:43 +02:00

Philipp Oeser commented

2021-10-26 09:30:43 +02:00

Sorry to hear (thx again reporting). In my opinion we should not sweep this under the carpet (esp. since this already been confirmed), there is still a chance to get this fixed in the future and others might be affected by this issue as well.
Feel free to unsubscribe though.

Sorry to hear (thx again reporting). In my opinion we should not sweep this under the carpet (esp. since this already been confirmed), there is still a chance to get this fixed in the future and others might be affected by this issue as well. Feel free to unsubscribe though.

tintwotin commented

2021-10-26 11:23:59 +02:00

Removed subscriber: @tintwotin

Richard Antalik commented

2021-11-02 01:41:03 +01:00

Added subscriber: @iss

Richard Antalik commented

2021-11-02 01:41:03 +01:00

I have intentionally hard-coded displayed channels to highest available, because sometimes you want to manipulate with invisible objects.

This type of workspace setup uses channel property of editor to set which channel is used as output. Outline drawing can have access to this property and strips can be filtered, but this wouldn't be complete solution.

Say channel 5 is used as output, if there are strips in channel 4 and 3, and both are blended with alpha over, this will display strips in channel 4 and 3. If there was colormix effect and one of it's input would be in channel 6, this strip would affect final result too.

So best way to resolve this issue would be to have option for SEQ_query_rendered_strips to go through strips and their relations to truly reflect which images are used for rendering. Still not completely bulletproof though. I would have to investigate if this would be useful for rendering or if it would be just source of error, which is quite likely. It's probably best to implement function to traverse these relationships and apply early-outs where possible.

Marking as known issue so far, because this works as intended. Not sure how to provide option to not display outline for hidden images or if this is even something that should be done.

I have intentionally hard-coded displayed channels to highest available, because sometimes you want to manipulate with invisible objects. This type of workspace setup uses channel property of editor to set which channel is used as output. Outline drawing can have access to this property and strips can be filtered, but this wouldn't be complete solution. Say channel 5 is used as output, if there are strips in channel 4 and 3, and both are blended with alpha over, this will display strips in channel 4 and 3. If there was colormix effect and one of it's input would be in channel 6, this strip would affect final result too. So best way to resolve this issue would be to have option for SEQ_query_rendered_strips to go through strips and their relations to truly reflect which images are used for rendering. Still not completely bulletproof though. I would have to investigate if this would be useful for rendering or if it would be just source of error, which is quite likely. It's probably best to implement function to traverse these relationships and apply early-outs where possible. Marking as known issue so far, because this works as intended. Not sure how to provide option to not display outline for hidden images or if this is even something that should be done.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE: In Multicam all strips gets white outline #92105