Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blender 2.79 #43

Open
clankill3r opened this issue Jan 22, 2018 · 10 comments
Open

blender 2.79 #43

clankill3r opened this issue Jan 22, 2018 · 10 comments

Comments

@clankill3r
Copy link

Is there any difference between this repository and the filmic blender in 2.79?

@sobotka
Copy link
Owner

sobotka commented Jan 22, 2018

Indeed.

The default "Filmic" view, which carries on Blender's confused description of what a display is, is actually the Filmic Log Encoding Base coupled with the Base Contrast.

There currently is no means to generate a purely Filmic Log encoded image. You can see this by comparing the "None" creative look against "Base Contrast" and note that the two are identical.

This will pose issues for anyone seeking to use alternative display referred tool chains. For example, the Agent team used the Filmic Log encoded imagery at 16 bit for grading within Resolve.

@Blendify
Copy link

Blendify commented Jan 22, 2018 via email

@finnbear
Copy link

finnbear commented Nov 3, 2018

@sobotka You're suggesting that something about Blender's implementation of "Filmic" is suboptimal. What implications does this have on my project if I would otherwise use your filmic addon with "Base Contrast"? Does compositing make any difference?

Basically, is there anything different between Addon using "Base Contrast" and Stock Blender using "Filmic?"

@sobotka
Copy link
Owner

sobotka commented Nov 3, 2018

It depends on context. There is no Base Log encoding exposed in Blender’a version, so if you are saving to a 16 bit TIFF, you are losing out on the densest data.

If you save as an EXR and process elsewhere, no issue. Some software is more complex to use EXRs properly with, such as Resolve, and as such not having the base log encoding exposed is extremely problematic.

@echuber2
Copy link

echuber2 commented Nov 4, 2018

Have you made a feature request to the Blender team about this?

@musm
Copy link

musm commented Nov 4, 2018

@sobotka can you explain the best way to export to resolve. I had issues in the past but wasn't aware this might have been the problem.

@sobotka
Copy link
Owner

sobotka commented Nov 4, 2018

@musm Depends on contextual needs.

The Looks can be converted to Resolve compatible cubes quite easily, even via a spreadsheet. This allows the transform to be applied via the OFX nodes to go from EXRs to the Base Log, and out to the Look.

Resolve isn’t terribly well designed for a full scene referred workflow, and as such, YMMV with regards to mental models and interactions. In the instance where scene referred does not work for a pipeline, it would be wisest to go to a dense Base Log at 16 bit, and apply the Look as above at the tail end in Resolve of the software of choice.

This is again how the Agent colourist achieved the final grade based off of the Base Contrast example LUT.

@sobotka
Copy link
Owner

sobotka commented May 22, 2019

Does what work?

@bimbachi
Copy link

does FilmicBlender color mangement work on Blender 2.8?

@sobotka
Copy link
Owner

sobotka commented Jun 14, 2019

That’s up to the audience to tell me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants