Color management is broken in the Sequencer #66682

New Issue

Vincent Girès · 2019-07-11T00:24:38+02:00

Vincent Girès commented

2019-07-11 00:24:38 +02:00

System Information
Operating system: Linux-5.0.21-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits
Graphics card: Mesa DRI Intel(R) Sandybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 19.1.1

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-10 15:05, hash: bb7b741d2f
Worked: earlier build of 2.80 (hash: d62a749fcf) and 2.79

Short description of error
Weird things happens when changing the color management settings in the VSE:

wrong color display
make sound

Exact steps for others to reproduce the error
With a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not.
Also, changing this setting does not apply the change directly, the VSE has to be refreshed.

Another issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.

**System Information** Operating system: Linux-5.0.21-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits Graphics card: Mesa DRI Intel(R) Sandybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 19.1.1 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-10 15:05, hash: `bb7b741d2f` Worked: earlier build of 2.80 (hash: d62a749fcf48) and 2.79 **Short description of error** Weird things happens when changing the color management settings in the VSE: - wrong color display - make sound **Exact steps for others to reproduce the error** With a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not. Also, changing this setting does not apply the change directly, the VSE has to be refreshed. Another issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.

Vincent Girès commented

2019-07-11 00:24:38 +02:00

Added subscriber: @VincentGires

Richard Antalik commented

2019-07-11 10:57:36 +02:00

Added subscriber: @iss

Richard Antalik commented

2019-07-11 10:57:36 +02:00

With a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not.

see #65271 (Using Filmic view transform causes VSE to be lower contrast than it should be)

Also, changing this setting does not apply the change directly, the VSE has to be refreshed.
Another issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.

This would be bug though.

>With a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not. see #65271 (Using Filmic view transform causes VSE to be lower contrast than it should be) >Also, changing this setting does not apply the change directly, the VSE has to be refreshed. >Another issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise. This would be bug though.

Brecht Van Lommel commented

2019-07-11 11:37:41 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-07-11 11:37:41 +02:00

We require a .blend file and exact steps to reproduce the problem.

Vincent Girès commented

2019-07-11 12:40:28 +02:00

In #66682#718002, @iss wrote:
see #65271 (Using Filmic view transform causes VSE to be lower contrast than it should be)

This is a different topic. I'm not talking about display result with Filmic that dipslay sRGB files less contrasted which is normal.

Let's say you uses the VSE with "Standard" view transform (old sRGB). If you put a movie in the VSE with Blender 2.79, set the "Sequencer" color management to anything without having any color modifier on the strip, the result looks the same. It makes the sequencer able to work in any working colorspace for grading. Do the same with the current 2.80 version and switch for instance the "Sequencer" color management between sRGB and Filmic Log and the result will look different. This is also problematic when using another ocio config file (like the one of ACES with ACEScc working space).

Here is two .blend files that have a different sequencer color management. Open it and compare the result in 2.80, it does not look identical. Open the same files with 2.79 and the result is the same.
I think the correct behavior was the one of 2.79.
bug_report.zip

> In #66682#718002, @iss wrote: > see #65271 (Using Filmic view transform causes VSE to be lower contrast than it should be) This is a different topic. I'm not talking about display result with Filmic that dipslay sRGB files less contrasted which is normal. Let's say you uses the VSE with "Standard" view transform (old sRGB). If you put a movie in the VSE with Blender 2.79, set the "Sequencer" color management to anything without having any color modifier on the strip, the result looks the same. It makes the sequencer able to work in any working colorspace for grading. Do the same with the current 2.80 version and switch for instance the "Sequencer" color management between sRGB and Filmic Log and the result will look different. This is also problematic when using another ocio config file (like the one of ACES with ACEScc working space). Here is two .blend files that have a different sequencer color management. Open it and compare the result in 2.80, it does not look identical. Open the same files with 2.79 and the result is the same. I think the correct behavior was the one of 2.79. [bug_report.zip](https://archive.blender.org/developer/F7591581/bug_report.zip)

Sebastian Parborg commented

2019-07-15 11:53:23 +02:00

Added subscriber: @ZedDB

Richard Antalik was assigned by Sebastian Parborg

2019-07-15 11:53:23 +02:00

Sebastian Parborg commented

2019-07-15 11:53:23 +02:00

@iss can you look into this?

Richard Antalik commented

2019-07-15 20:34:14 +02:00

d62a749fcf is not that old, though I am not aware of any changes here.

I will investigate

d62a749fcf48 is not that old, though I am not aware of any changes here. I will investigate

dark999 commented

2019-07-15 21:18:03 +02:00

Added subscriber: @dark999

dark999 commented

2019-07-15 21:18:03 +02:00

@VincentGires your GPU is not officially supported from Blender, it is too old to match minimum Blender requirement

https://www.blender.org/download/requirements/

@VincentGires your GPU is not officially supported from Blender, it is too old to match minimum Blender requirement https://www.blender.org/download/requirements/

Vincent Girès commented

2019-07-16 13:24:48 +02:00

In #66682#723172, @dark999 wrote:
@VincentGires your GPU is not officially supported from Blender, it is too old to match minimum Blender requirement

https://www.blender.org/download/requirements/

Indeed, I was reporting the bug on my laptop. Here is my working machine where it does the same for both issues:
Operating system: Linux-3.10.0-327.el7.x86_64-x86_64-with-centos-7.2.1511-Core 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.77

In #66682#723163, @iss wrote:
d62a749fcf is not that old, though I am not aware of any changes here.

I will investigate

Sorry for the mess of my report, I sent more or less two different issues within the same task.

d62a749fcf do not have the issue of the exposure/gamma that makes some noise with a strip that have sound and changing those setting in this build is very fast to compute. Latest build is slower, this is significant on low-end machine.
About the working space that give different result even on strips without color correction, d62a749fcf behave the same than the latest build and I didn't succeed to build older commit (from the beginning of 2.80) to try to see if it was already there or not. But the 2.79 with the files I've uploaded is not displaying the same result than 2.80. Maybe the ocio.config file has changed? or maybe the result is correct now and was not before?

> In #66682#723172, @dark999 wrote: > @VincentGires your GPU is not officially supported from Blender, it is too old to match minimum Blender requirement > > https://www.blender.org/download/requirements/ Indeed, I was reporting the bug on my laptop. Here is my working machine where it does the same for both issues: Operating system: Linux-3.10.0-327.el7.x86_64-x86_64-with-centos-7.2.1511-Core 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.77 > In #66682#723163, @iss wrote: > d62a749fcf48 is not that old, though I am not aware of any changes here. > > I will investigate Sorry for the mess of my report, I sent more or less two different issues within the same task. - d62a749fcf48 do not have the issue of the exposure/gamma that makes some noise with a strip that have sound and changing those setting in this build is very fast to compute. Latest build is slower, this is significant on low-end machine. - About the working space that give different result even on strips without color correction, d62a749fcf48 behave the same than the latest build and I didn't succeed to build older commit (from the beginning of 2.80) to try to see if it was already there or not. But the 2.79 with the files I've uploaded is not displaying the same result than 2.80. Maybe the ocio.config file has changed? or maybe the result is correct now and was not before?

Vincent Girès commented

2019-07-16 13:27:31 +02:00

The exposure/gamma setting make noise only when audio scrubbing is checked.

Vincent Girès commented

2019-07-19 14:52:55 +02:00

By curiosity, I tried to use the config.ocio file from 2.80 in 2.79 and there is no issue while using the config file of 2.79 in 2.80 still have not identical render with the two files I've uploaded. It's then probably not related to the new ocio file and something has been broken in 2.80.
Hope it helps.

By curiosity, I tried to use the config.ocio file from 2.80 in 2.79 and there is no issue while using the config file of 2.79 in 2.80 still have not identical render with the two files I've uploaded. It's then probably not related to the new ocio file and something has been broken in 2.80. Hope it helps.

Richard Antalik commented

2019-07-19 15:02:26 +02:00

In #66682#727252, @VincentGires wrote:
By curiosity, I tried to use the config.ocio file from 2.80 in 2.79 and there is no issue while using the config file of 2.79 in 2.80 still have not identical render with the two files I've uploaded. It's then probably not related to the new ocio file and something has been broken in 2.80.
Hope it helps.

It does help.
Thanks.

> In #66682#727252, @VincentGires wrote: > By curiosity, I tried to use the config.ocio file from 2.80 in 2.79 and there is no issue while using the config file of 2.79 in 2.80 still have not identical render with the two files I've uploaded. It's then probably not related to the new ocio file and something has been broken in 2.80. > Hope it helps. It does help. Thanks.

Richard Antalik was unassigned by Dalai Felinto

2019-12-23 16:33:50 +01:00

tintwotin commented

2020-01-18 13:08:43 +01:00

Added subscriber: @tintwotin

tintwotin commented

2020-01-18 13:08:43 +01:00

Seems to be an quite important bug to fix in 2.82, no? And maybe this, somewhat related, export one: https://developer.blender.org/T57397

What do you think @iss?

Seems to be an quite important bug to fix in 2.82, no? And maybe this, somewhat related, export one: https://developer.blender.org/T57397 What do you think @iss?

tintwotin commented

2020-06-12 12:43:16 +02:00

Removed subscriber: @tintwotin

tintwotin commented

2020-06-12 12:43:19 +02:00

Added subscriber: @tintwotin

tintwotin commented

2020-06-12 12:43:22 +02:00

Removed subscriber: @tintwotin

Pauan commented

2021-09-29 16:12:14 +02:00

Added subscriber: @pauanyu_blender

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Color management is broken in the Sequencer #66682