Video Sequence Editor lost stereoscopic preview #77564

Closed
opened 3 years ago by GabrielMontagne · 12 comments

System Information
Operating system: Linux-4.19.0-9-amd64-x86_64-with-debian-10.4 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.3.6

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 12:23, hash: 82e3bd4bbb (also broken in 2.83.0 downlaoded from the main download page)
Worked: 2.83 alpha (I only have a custom build lying around, sorry, but it was before https://developer.blender.org/T71546 -- on which one can see the VSE trying to render the stereoscopic preview)
Short description of error
When loading a stereoscopic image sequence on the VSE the preview shows only a monoscopic version even though when I render the image, the stereoscopic image is rendered as expected.
On older builds it rendered the stereoscopic preview correctly (if the strip was the same size as the output, https://developer.blender.org/T71546)

Exact steps for others to reproduce the error

  • Create a new file.
  • In the output properties, turn on stereoscopy.

On the VSE editor, import the DSCF****_L.jpg files on the attached zip — on the options select "use multi view" and leave "individual".

I'm uploading a zip file with a couple of stereo images, for debugging comfort.

vse-stereoscopy-preview.zip

NOTE: while doing tests on the previous "working" (although admittedly dodgy) build, I could see the 3D previews but the renders were black on the image editor.
I'm not sure if that's related or not, but still I wanted to mention it.

On a recent build,
A-BROKEN-NOW_feh_023802_000002_2020-06-07-091813_1920x1080_scrot.png

On an old build,
B-WORKING-BEFORE_feh_023802_000001_2020-06-07-091627_1920x1080_scrot.png

**System Information** Operating system: Linux-4.19.0-9-amd64-x86_64-with-debian-10.4 64 Bits Graphics card: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.3.6 **Blender Version** Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 12:23, hash: `82e3bd4bbb` (also broken in 2.83.0 downlaoded from the main download page) Worked: 2.83 alpha (I only have a custom build lying around, sorry, but it was before https://developer.blender.org/T71546 -- on which one can see the VSE trying to render the stereoscopic preview) **Short description of error** When loading a stereoscopic image sequence on the VSE the preview shows only a monoscopic version even though when I render the image, the stereoscopic image is rendered as expected. On older builds it rendered the stereoscopic preview correctly (if the strip was the same size as the output, https://developer.blender.org/T71546) **Exact steps for others to reproduce the error** - Create a new file. - In the output properties, turn on stereoscopy. # On the VSE editor, import the DSCF****_L.jpg files on the attached zip — on the options select "use multi view" and leave "individual". I'm uploading a zip file with a couple of stereo images, for debugging comfort. [vse-stereoscopy-preview.zip](https://archive.blender.org/developer/F8588737/vse-stereoscopy-preview.zip) **NOTE:** while doing tests on the previous "working" (although admittedly dodgy) build, I could see the 3D previews but the renders were black on the image editor. I'm not sure if that's related or not, but still I wanted to mention it. On a recent build, ![A-BROKEN-NOW_feh_023802_000002_2020-06-07-091813_1920x1080_scrot.png](https://archive.blender.org/developer/F8588754/A-BROKEN-NOW_feh_023802_000002_2020-06-07-091813_1920x1080_scrot.png) On an old build, ![B-WORKING-BEFORE_feh_023802_000001_2020-06-07-091627_1920x1080_scrot.png](https://archive.blender.org/developer/F8588753/B-WORKING-BEFORE_feh_023802_000001_2020-06-07-091627_1920x1080_scrot.png)
Poster

Added subscriber: @GabrielMontagne

Added subscriber: @GabrielMontagne
Owner

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

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

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Collaborator

Could be that the new stereo rendering assumes that stereo rendering always happen in a GPUViewport. As VSE doesn't use a GPUViewport it does not render correctly anymore. Actually the stereo composite isn't executed anymore. This change was needed to solve color management issues in the viewport and make sure the image editor displays the correct results. I have missed this one.

My proposal is to make the scene sequencer preview a GPU viewport this is the most future proof way and use the global window stereo setting.
Current implementation seems to be a per strip setting. But that will change current workflow.

@iss: What do you think?

Could be that the new stereo rendering assumes that stereo rendering always happen in a GPUViewport. As VSE doesn't use a GPUViewport it does not render correctly anymore. Actually the stereo composite isn't executed anymore. This change was needed to solve color management issues in the viewport and make sure the image editor displays the correct results. I have missed this one. My proposal is to make the scene sequencer preview a GPU viewport this is the most future proof way and use the global window stereo setting. Current implementation seems to be a per strip setting. But that will change current workflow. @iss: What do you think?
Collaborator

Added subscriber: @iss

Added subscriber: @iss
iss commented 3 years ago
Collaborator

In #77564#953852, @Jeroen-Bakker wrote:
My proposal is to make the scene sequencer preview a GPU viewport this is the most future proof way and use the global window stereo setting.
Current implementation seems to be a per strip setting. But that will change current workflow.

@iss: What do you think?

Can you give me some reference or elaborate a bit more? (read what should I do?)

> In #77564#953852, @Jeroen-Bakker wrote: > My proposal is to make the scene sequencer preview a GPU viewport this is the most future proof way and use the global window stereo setting. > Current implementation seems to be a per strip setting. But that will change current workflow. > > @iss: What do you think? Can you give me some reference or elaborate a bit more? (read what should I do?)
Owner

Added subscriber: @dfelinto

Added subscriber: @dfelinto
Owner

Issue introduced on fe045b2b77.

Issue introduced on fe045b2b77.
dfelinto self-assigned this 3 years ago
Collaborator

This issue was referenced by 2e908156d0

This issue was referenced by 2e908156d0c744e526e165b386c61a0a4d0e8ed0
fclem commented 3 years ago
Collaborator

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
fclem closed this issue 3 years ago
Collaborator

This issue was referenced by 47c6f41b89

This issue was referenced by 47c6f41b8926befcf1ffe8b0dcccb90922c4b9be
Collaborator

This issue was referenced by 40edb84dcf

This issue was referenced by 40edb84dcf4f05fe2d6a73170617af0eab0cd5ff
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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 project
No Assignees
6 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#77564
Loading…
There is no content yet.