Filmic profile can use another looks #56986
Labels
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#56986
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
W10 64b
Blender Version
2.79b
Short description of error
You can use custom Look with filmic even it is not possible normal way.
Exact steps for others to reproduce the error
But it looks like working :)
Added subscriber: @Cenda
Added subscriber: @AdamPreisler
Can confirm this and it also happens in 2.8.
However never was a big problem.. Can confuse occasionaly though.
It might be a good idea to remember the Looks for each View Transform. And also Exposure and Gamma when it comes to this tbh.
Should filmic contrast be a "Look" or maybe a value field similar to Exposure and Gamma? Personally the contrast looks that are premade (Very Low Contrast, Base Contrast, High Contrast etc) work great for me.
Not sure here, but Gamma can be used in place of contrast when it comes to Filmic but maybe it only affects the midtones, @troy_s could shed some light when it comes to this I am sure
Added subscriber: @troy_s
Generic power functions operate such that they nonlinearly head towards 0.0 and 1.0.
If you think about contrast as being a widening of the spaces between values nonuniformly, this of course would increase contrast on both scene referred linear and nonlinear encodings. However, there are a couple of caveats:
That about sums up the complexity around ideas of contrast. If you want to experiment with the above concepts, you can perform a fulcrum based contrast adjustment on scene referred data rather easily. In the compositor:
You can of course perform the same fulcrum based contrast around any value, including higher values of 5.0 to 16.0 for example.
Thanks Troy! I always enjoy reading a good explanation of such topics. The 7 premade Contrasts for filmic work great it's just that I realized that Corona Renderer has a value input for Contrast so wondered if maybe it's not exposable. Some discussion about it is here: https://corona-renderer.com/forum/index.php?topic=12552.0
Anyway, would it be useful to remember Looks for each View transform? Possibly, but not very necessary to sort out right now.
Added subscriber: @brecht
I think the Looks implementation is a bit in need of an update for sure. @brecht wisely implemented some rudimentary filtering, which would be likely more ideal via OCIO's families perhaps.
The problem with the Corona stuffs is that a curve doesn't tell the whole story. Specifically, it doesn't tell us:
With Filmic, these answers are pretty clear:
Corona's approach is some sort of homebrew parametric. Judging from the shapes, they aren't telling you what the dynamic range is of the shaper transform that woudl come before that S shaped curve. We can estimate that the range of stop values up and down from middle grey is roughly equal though, as the centre point along X is roughly the centre point along Y. Without knowing those details though, it's silly to speculate as folks are in that thread. You could also end up with wonky results if a parametric approach doesn't have some form of constraints.
Thanks for further clarification. I see that there is a lot of underlying complexity and personally I don't need a parametric slider because the 7 presets work just great and at least no need to have random "on a whim" values like 1.5123 in the slider...
I dug around to show you how it works from a pixel pusher's perspective because maybe with your knowledge you can guess it but it's more for your curiosity. One setting that I miss in Blender which comes to mind is the "Highlight Compress" shown at 12 seconds into the video.
https://www.youtube.com/watch?time_continue=1&v=FLkltjN6Ld4
Highlight compression is the distance between the peak of the linear section of the curve and the terminating value. It's probably something that loosely controls the shape of the curve or the range of values.
It's not really an issue with Filmic as the values are fixed . The range Filmic uses is something roughly akin to traditional photographic emulsion. The rate of change between the linear-ish portion of the Filmic curve and the terminating point is essentially a byproduct of the slope. Adjusting it would probably lead to some wonky looking results.
You can see from the Corona demo you linked that they are missing some critical aspects as the sky starts fully saturated cyan, which is a telltale sign that the camera rendering transform is broken.
Good to read:)
Tbh the problem here is so minor that I don't think it's necessary to fix but could be good to remember Looks depending on View Transform.
I always use Filmic for all my renders with only adjusting exposure and Contrast but when it comes to rendering out normal maps through Viewport OpenGL grabbing (using the normalmap matcap) I tend to use Default and None but it's not exactly right of course but haven't used it enough to care as my current methods are fine for my uses.. Would be immensly helpful to show true normal matcap colors escpecially though..