Color Management - Film and RRT presets and ALL film looks missing #65538

Closed
opened 2019-06-05 19:57:44 +02:00 by Adam Janz · 24 comments

System Information
Operating system: Windows-8.1-6.3.9600 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.22

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-05 13:55, hash: 806d4fbc5e
Worked: 2.80 (sub 69), branch: blender2.7, commit date: 2019-05-17 23:36, hash: 03672e7783

Short description of error
Just realized the Film and RRT view transform presets are missing in this latest build, along with all film looks. Also the basic contrast presets for "Look" are only available when Filmic or Standard is selected. I'm using the Film preset for a current project, so I will need to roll back to the previous installed build until this can be fixed. Thanks!

**System Information** Operating system: Windows-8.1-6.3.9600 64 Bits Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.22 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-05 13:55, hash: `806d4fbc5e` Worked: 2.80 (sub 69), branch: blender2.7, commit date: 2019-05-17 23:36, hash: `03672e7783` **Short description of error** Just realized the Film and RRT view transform presets are missing in this latest build, along with all film looks. Also the basic contrast presets for "Look" are only available when Filmic or Standard is selected. I'm using the Film preset for a current project, so I will need to roll back to the previous installed build until this can be fixed. Thanks!
Author

Added subscriber: @AdamJanz

Added subscriber: @AdamJanz

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-06-05 20:11:53 +02:00

This was an intentional change in d2e139e.

This was an intentional change in d2e139e.
Author

Oh okay, thanks, Brecht, for letting me know. I'm able to match Filmic to the old Film preset using 1.2 exposure and 0.5 gamma, but of course it misses that extra warmth the Film preset had. On the plus side, Filmic has more accurate color than Film did. I guess if leaving legacy transforms in would break something, then I'll just need to move forward without them. Thanks.

Oh okay, thanks, Brecht, for letting me know. I'm able to match Filmic to the old Film preset using 1.2 exposure and 0.5 gamma, but of course it misses that extra warmth the Film preset had. On the plus side, Filmic has more accurate color than Film did. I guess if leaving legacy transforms in would break something, then I'll just need to move forward without them. Thanks.
Author

Well I'm going to chime in once more on this, Brecht, having worked with the two competing view transforms this past week. My client actually preferred the look of the Film preset (over Filmic), so that has me staying with a older 2.8 build for now. I really think the legacy presets should stay in right until the day that they can be replaced with updated versions that work with HDR. After all, why should HDR be a factor in taking away an artist's creativity? There is tons of content being made that has nothing to do with HDR. The more LUTs and grading options we have, the better. Let the artist decide if the presets will work for them or not. Otherwise, we're forced to use a stripped down version and try to recreate those classic legacy looks using color curves, exposure and gamma settings, and extra post processing when we shouldn't have to. The presets just worked before. Unless they explicitly break some new feature of Blender, I say let them remain. :-)

Thank you!

  • Adam Janz
Well I'm going to chime in once more on this, Brecht, having worked with the two competing view transforms this past week. My client actually preferred the look of the Film preset (over Filmic), so that has me staying with a older 2.8 build for now. I really think the legacy presets should stay in right until the day that they can be replaced with updated versions that work with HDR. After all, why should HDR be a factor in taking away an artist's creativity? There is tons of content being made that has nothing to do with HDR. The more LUTs and grading options we have, the better. Let the artist decide if the presets will work for them or not. Otherwise, we're forced to use a stripped down version and try to recreate those classic legacy looks using color curves, exposure and gamma settings, and extra post processing when we shouldn't have to. The presets **just worked** before. Unless they explicitly break some new feature of Blender, I say let them remain. :-) Thank you! - Adam Janz

Added subscriber: @KihakuGisui

Added subscriber: @KihakuGisui

Added subscriber: @James8569

Added subscriber: @James8569

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
James reopened this issue 2019-07-14 09:02:48 +02:00

What in the h3ll is the point in removing these? Is there something about them that's broken?

What in the h3ll is the point in removing these? Is there something about them that's broken?

I just wasted 11 hours of rendering BTW.

I just wasted 11 hours of rendering BTW.

Added subscriber: @moisessalvador

Added subscriber: @moisessalvador

Color management isn't applied until you save the image and it's not applied on EXR. You could've saved it as EXR, and applied the color management to that image later, to not have to re-render again

Color management isn't applied until you save the image and it's not applied on EXR. You could've saved it as EXR, and applied the color management to that image later, to not have to re-render again

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Author

Yes, it's very unfortunate these presets were removed. I'm still using 2.80 (sub 69), branch: blender2.7, commit date: 2019-05-17 23:36, hash: 03672e7783 which includes a few bugs that were fixed in later versions, but at least this earlier build allows the artist full creative freedom. Hopefully we will see the decision to remove the presets reversed soon. It certainly would be greatly appreciated by many in the Blender community and aid in backwards compatibility with older Blender training out there.

Yes, it's very unfortunate these presets were removed. I'm still using 2.80 (sub 69), branch: blender2.7, commit date: 2019-05-17 23:36, hash: `03672e7783` which includes a few bugs that were fixed in later versions, but at least this earlier build allows the artist full creative freedom. Hopefully we will see the decision to remove the presets reversed soon. It certainly would be greatly appreciated by many in the Blender community and aid in backwards compatibility with older Blender training out there.

Added subscriber: @rjg

Added subscriber: @rjg

@AdamJanz While it may be more work, you still have full control over the result by color grading in the compositor.

@AdamJanz While it may be more work, you still have full control over the result by color grading in the compositor.
Author

That is true, Robert, but trying to manually match the gamma response of certain presets is not something artists should have to do when we had something that worked perfectly fine. Again I say the presets should be retained until they can be replaced with HDR capable ones (although HDR is not something that is important to me).

That is true, Robert, but trying to manually match the gamma response of certain presets is not something artists should have to do when we had something that worked perfectly fine. Again I say the presets should be retained until they can be replaced with HDR capable ones (although HDR is not something that is important to me).

I think i've managed to cheat the system by copying the 2.79 colormanagement folder and replaced the 2.80 RC1 giving back the film color settings. It seems to work too. Nice dynamic programming!

I think i've managed to cheat the system by copying the 2.79 colormanagement folder and replaced the 2.80 RC1 giving back the film color settings. It seems to work too. Nice dynamic programming!

Yes it has definitely done the job! :)

Yes it has definitely done the job! :)
Author

Nice find, James! So you just swapped one folder with another? Would you mind sharing what these two folders were named? Thanks (Now we're a bit like the MagicLantern team bringing advanced functionality to their Canon DSLRs that Canon omitted...) Hey I'm not against the Blender devs making changes, (they've made some pretty incredible ones which is hugely appreciated by me!) but as the old adage goes... if something's not broken, don't fix it... :-)

Nice find, James! So you just swapped one folder with another? Would you mind sharing what these two folders were named? Thanks (Now we're a bit like the MagicLantern team bringing advanced functionality to their Canon DSLRs that Canon omitted...) Hey I'm not against the Blender devs making changes, (they've made some pretty incredible ones which is hugely appreciated by me!) but as the old adage goes... if something's not broken, don't fix it... :-)

I renamed the current 2.80 rc1 colormanagement folder to Xcolormanagement.
See my unzipped folder in image below...
colormanagement_folder.png
Copied the 2.79 folder from C:\Program Files\Blender Foundation\Blender\2.79\datafiles\colormanagement -> see folder mentioned above.

I renamed the current 2.80 rc1 colormanagement folder to Xcolormanagement. See my unzipped folder in image below... ![colormanagement_folder.png](https://archive.blender.org/developer/F7620881/colormanagement_folder.png) Copied the 2.79 folder from C:\Program Files\Blender Foundation\Blender\2.79\datafiles\colormanagement -> see folder mentioned above.
Author

Great; thank you, James! I will have to give this a try... :-)

Great; thank you, James! I will have to give this a try... :-)
Author

So I tested the folder swap in RC2... you only get access to the film looks, but you do NOT get access to the "Very Low Contrast" to "Very High Contrast" settings, which is what I need if I'm using the Film preset. So I will just stick with Filmic until this is changed back. If I do need to render Film, I'd have to use an EXR and then open it in an older version of 2.8 in the compositor to apply the Film preset.

So I tested the folder swap in RC2... you only get access to the film looks, but you do NOT get access to the "Very Low Contrast" to "Very High Contrast" settings, which is what I need if I'm using the Film preset. So I will just stick with Filmic until this is changed back. If I do need to render Film, I'd have to use an EXR and then open it in an older version of 2.8 in the compositor to apply the Film preset.
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
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
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 Info 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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#65538
No description provided.