Video Sequence Editor lost stereoscopic preview #77564

New Issue

gabriel montagné · 2020-06-07T10:27:48+02:00

gabriel montagné commented

2020-06-07 10:27:48 +02:00

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,

On an old build,

**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)

gabriel montagné commented

2020-06-07 10:27:48 +02:00

Added subscriber: @GabrielMontagne

Dalai Felinto commented

2020-06-08 09:59:12 +02:00

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

Jeroen Bakker commented

2020-06-15 10:26:04 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2020-06-15 10:26:04 +02:00

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?

Jeroen Bakker commented

2020-06-15 11:38:18 +02:00

Added subscriber: @iss

Richard Antalik commented

2020-06-26 15:22:35 +02:00

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?)

Dalai Felinto commented

2020-08-03 18:39:15 +02:00

Added subscriber: @dfelinto