sobotka / filmic-blender

Film Emulsion-Like Camera Rendering Transforms for Blender

Download the latest version of Filmic Blender

Who?

This is a simple OpenColorIO configuration for intermediate to advanced imagers using Blender's Cycles raytracing engine, or the Renderman system as included by default.

What?

This OpenColorIO configuration adds a closer-to-photorealistic view transform for your renders. For imagers working with non-photorealistic rendering, it also will bring significant dynamic range and lighting capabilities to your work, as well as potentially open up correct transforms for rendering to HDR displays and other such forward looking technology. It is as close to a Magic Button™ you can get for an experienced imager. The kit embodies a high dynamic range transfer function and an intensity gamut mapping.

Filmic does two things:

1. It compresses the scene referred linear radiometric energy values down to the display / output referred range. This aspect is known as a transfer function or tone mapping. The shape of the Filmic Base Log with a contrast aesthetic roughly emulates a photographic film curve.
2. It compresses the gamut for high intensity values. As colour ratios increase in intensity, highly saturated ratios tend to be resistant to transfer function compression, which results in peculiar feeling imagery with some regions feeling appropriately over-exposed and others "lingering" behind. Filmic considers all colour values fair game, and attempts to blend colours into a consistent output that matches our learned expectations from film emulsion-like media.

When?

This repository is ready to use right now, with no compilation or special Blender application binaries required.

Why?

Because the basic sRGB nonlinear transfer functions (OETF / EOTF) were designed to describe an aspect of device response and never for rendering. This configuration is a step towards providing imagers with a reliable camera rendering transform and a base of aesthetic looks useful for modern raytracing engine CGI, animation, and visual effects work with real-world cameras.

How?

1. Download the latest version of Filmic Blender. Replace your current OpenColorIO configuration in Blender with this version.

2. The Blender OpenColorIO configuration directory is located in:

   BLENDER/bin/VERSIONNUMBER/datafiles/colormanagement
   

   Move the existing colormanagement directory to a backup location, and place the contents of this repository into a new colormanagement directory.

3. Optionally, instead of replacing the actual directory, use the environment variable to specify where the OCIO configuration lives:

   export OCIO=/path/to/where/the/filmic-blender/config.ocio
   

4. From within the Color Management panel, change the View to your desired contrast level and render.

Once you have Blender utilising the configuration, you are free to render away. You may discover that some of your materials were broken due to exceptionally low lighting levels, and may require reworking. General PBR advice holds true when using wider and more photographic illumination levels.

Supported Display Colorimetry

The current configuration supports:

• Generic sRGB / REC.709 displays with 2.2 native power function
• Display P3 displays with 2.2 native power function. Examples include:
  • Apple MacBook Pros from 2016 on.
  • Apple iMac Pros.
  • Apple iMac from late 2015 on.

Due to an unfortunate side effect of the way Blender has thus far integrated colour management, folks pushing pixels on Apple Display P3 devices will need to be careful when encoding images. Loosely:

• When viewing renders, use the Apple Display P3 setting.
• When saving nonlinear display referred files such as JPEG, TIFF, etc. it is critical that the Display be set to the file encoding. For example, for sRGB imagery, the View must be set to sRGB for the file to be properly encoded. If this is not done, the file will not be encoded properly. The bug / todo can be found at the link provided.

Additional Information and Technical Details

The basic kit of weaponry includes:

View Transforms

A set of View transforms that include:

1. sRGB OETF. This is an accurate version of the sRGB transfer function. This is identical to what imagers would use as the "Default" View transform in Blender proper. Should be avoided at all costs for CGI work. Useful in some edge cases for albedo textures, for example.
2. Non-Colour Data. This is a view useful for evaluating a data format. Do not expect to see perceptual values however, as it is literally data dumped directly to the screen. Use this transform on your buffer, via the UV Image Viewer Properties panel, if your buffer represents data and not colour information. This will keep it out of the OpenColorIO transformation pipeline chain and leave it as data.
3. Linear Raw. This is a colour managed linearized version of your data. For all intents an purposes, will look identical to Non-Colour Data, but applied to colour based data such as an image.
4. Filmic Log Encoding Base. This is the workhorse View for all of your rendering work. Setting it in the View will result in a log encoded appearance, which will look exceptionally low contrast. Use this if you want to adjust the image for grading using another tool such as Resolve, with no additional modifications. Save to a high bit depth display referred format such as 16 bit TIFF. This basic view is designed to be coupled with one of the contrast looks.

Look Transforms

A set of Look transforms that include:

1. Greyscale. This Look is based off of the Filmic Log Encoding Base and will deliver a weighted greyscale version of the image. The weights used are for REC.709 RGB lights, which are the same lights specified in sRGB.

2. Five contrast base looks for use with the Filmic Log Encoding Base. All map middle grey 0.18 to 0.5 display referred. Each has a smooth roll off on the shoulder and toe. They include:

   1. Very High Contrast.
   2. High Contrast.
   3. Medium High Contrast.
   4. Base Contrast. Similar to the sRGB contrast range, with a smoother toe.
   5. Medium Low Contrast.
   6. Low Contrast.
   7. Very Low Contrast.

3. False Colour. This Look is an extremely useful tool for evaluating your image in terms of the dynamic range and latitude. It is a colour coded "heat map" of your image values, according to the following codes:

   Value	Colour	Scene Referred Value
   Low Clip	Black	Scene Referred Linear value below 0.0001762728758.
   -7.5 EV	Purple	Scene Referred Linear value 0.00099436891.
   -5.0 EV	Blue	Scene Referred Linear value 0.005625.
   -2.5 EV	Cyan	Scene Linear value 0.005625.
   -0.01 EV	Green-Cyan	Scene Referred Linear value ~0.178.
   0 EV	Grey	Scene Referred Linear value 0.18009142.
   +0.01 EV	Green-Yellow	Scene Referred Linear value ~0.181.
   +2.17 EV	Yellow	Scene Referred Linear value 0.80779930598.
   +4.33 EV	Red	Scene Referred Linear value 3.62857262286.
   High Clip	White	Scene Referred Linear value above 16.29174024.

Grading Your Work

Given that images generated under Cycles are scene referred, many nodes in Blender, being broken, will not work properly. This may have been hidden if one used a range that perfectly mapped to the display referred domain such as the sRGB transfer function, however using a proper camera rendering transform exacerbates this brokenness.

There are a good number of nodes that work absolutely fine. For grading, it is highly encouraged to use the ASC CDL node, as it operates on scene referred imagery perfectly well. It is in the Color -> Color Balance node. Do not use the Lift, Gamma, Gain default as it is strictly a display referred formula and will break on scene referred imagery. Instead, change the drop down to ASC CDL and use the Slope, Offset, and Power controls to perform grading.

Almost all of the Adobe PDF specification blend modes in the Mix node are also display referred and are broken for Cycles rendering. That includes but is not limited to Overlay, Screen, and other such modes.

Viewing in Other Applications

It is important to tag your imagery generated with Filmic with the canonized sRGB ICC for viewing outside of Blender and across applications and the web. Simply assign the profile to your generated image using the tool of your choice. Do not convert.

Colorimetric Information

RGB Primaries

Filmic was designed to be easily integrated into existing pipelines, and as such, uses the primaries and achromatic white colour outlined in ITU-R BT.709 specification. As a result, the reference space lights match the sRGB specification and are as follows:

Primary	x	y
Red	0.64	0.33
Green	0.30	0.60
Blue	0.15	0.06
Achromatic	0.3127	0.3290

RGB to XYZ transform

Following with the above, the transformation for primaries to the CIE 1931 2 degree standard observer XYZ model, is:

Primary	Red	Green	Blue
X	0.4123910	0.3575840	0.1804810
Y	0.2126390	0.7151690	0.0721923
Z	0.0193308	0.1191950	0.9505320

Transfer Function of Base Log Encoding

The canonized ground-truth encoding for Filmic is the Filmic Base Log Encoding. The Base Log Encoding is a pure normalized log 2 encoding in two parts, to accomodate the gamut mapping for wide primary ratio intensity gamut mapping. The first portion that is routed through the 3D LUT for the gamut compression at value range -12.473931188, 12.526068812. The final Base Log Encoding covers the log 2 range of -12.473931188, 4.026068812.

Transfer Function of Aesthetic Outputs

The contrasts are designed for an idealized sRGB display, with the aforementionned primaries, and an Electro-Optical Transfer Function consisting of a pure 2.2 power function.

Issues

Please post any and all issues to the issue tracker at GitHub.

filmic-blender's Issues

Headless render error

Hello

thanks for your awesome tools man . . .

its helps me a lot

but recenly we have some issue when we render our scene in headless mode (command promp)
its suddenly error here the output from cmd :

c:\Program Files\Blender Foundation\Blender>blender -E CYCLES -b F:\RENDER\SH25\ANM_SQ005_SH0025.blend -o F:\RENDER
Color management: display "sRGB" used by scene not found, setting to default ("sRGB / BT.709").
Color management: scene view "Default" not found, setting default "sRGB EOTF".
Color management: sequencer colorspace "sRGB" not found, will use default instead.
Read new prefs: C:\Users***\AppData\Roaming\Blender Foundation\Blender\2.78\config\userpref.blend
found bundled python: c:\Program Files\Blender Foundation\Blender\2.78\python
read blend: F:\RENDER\SH25\ANM_SQ005_SH0025.blend
Info: Read library: 'Z:\Char_1.blend', parent ''
Info: Read library: 'Z:\Char_2.blend', 'Z:\Char_3.blend', parent ''
Info: Read library: 'Z:\Char_4.blend', 'Z:\Char_4.blend', parent ''
Info: Read library: Z:\Char_5.blend', parent ''
Info: Read library: 'Z:\Char_6.blend', 'Z:\Char_7.blend', parent ''
Dependency cycle detected:
Plane.008 depends on Char_rig through Armature Modifier.
Char_rig depends on Plane.008 through Action.

Color management: display "sRGB" used by scene not found, setting to default ("sRGB / BT.709").
Color management: scene view "Default" not found, setting default "sRGB EOTF".
Color management: sequencer colorspace "sRGB" not found, will use default instead.
Color management: image colorspace "sRGB" not found, will use default instead.
Color management: image colorspace "sRGB" not found, will use default instead.
Color management: image colorspace "sRGB" not found, will use default instead.
Color management: image colorspace "sRGB" not found, will use default instead.

Blender quit

Blender 2.8

In the 20 May 2019 meeting notes it was stated:

The OpenColorIO color management configuration was updated to remove legacy transforms. This provides a clean base for future improvements. (Brecht Van Lommel)

• Replace Log view transform with Filmic Log.
• Remove Rec.709, DCI-P3 displays that were incomplete and outdated.
• Remove outdated RRT and Film transforms, replaced by Filmic.
• Remove camera responsive curves that don’t work with HDR colors.
• Rename Default view transform to Standard.

So following this commit to Blender, what are the differences in color management between 2.8 and this repository?

[Q] Why are a lot of images clipped on the whites

Im using Filmic together with Thea Render, thats a different renderer then cycles for Blender. Im wondering why most of the images i use with Filmic have the whites "clipped". The range of white doesnt extend to the end of the histogram?

Blender and Photoshop show the same result. It can be fixed easily ofcourse. But im wondering why all images show it

Loading file created with default OCIO config crashes VSE

I am having the same problem described in an old closed issue by Italic.
When I load a blend file created with the blender shipped color config and switch to the VSE or if the VSE is open on load it crashes blender. (seg fault)
It seems there must be saved tracks in the VSE for this to ocour. A blend file loaded with noting in the VSE has no problems when you switch to it.
I am using Blender 278b

Uncommenting views on lines 39 to 47 in config.ocio leaves them missing one space

When I uncomment these lines I get errors on importing the file to NUKE because the lines then lack a space each.

Filmic in Blender 2.79 only renders B&W

I have followed the instructions to include this Filmic Blender into my Linux version of Blender 2.79. However, whenever I render an image, I only get a black and white image as a preview. (note: the preview is nearly the exact same when using sRGB in Filmic as with Log) Is this an issue with my setup, or is it an issue with Filmic, and can I fix it?

Working Space

When I used to import my exr files into AE, I'd set the project settings to 32 bpc (sRGB IEC61966-2.1) linearize working space. Because then the colors would match my render out of cycles. But what "working space" (At least I think that's what's it called) should I set it to?
Anyone who could tell me, please?

exr format

It seems that all of the 32bit or 16bit data is not getting exported to exr format correctly.

This is take from another user as I don't have Nuke.

"Screenshot in Natron... Both images are converted to CINEON Log Space then i crankt up the fstops... Filmic Blender has serious issues with deep blacks... in a 16 or 32 bit working enviroment is filmic blender not a good sollution it kills dynamic range..."

Gamma 2.2 Displays

I wanted to reach out regarding potential gamma 2.2 display support.

I was digging through the OCIO config and, as I understand it, everything seems to revolve around using a typical sRGB display device for viewing; i.e. all of the looks move us from the "Filmic Log Encoding" colorspace into a final space for sRGB monitor display.

linear image data -> filmic log colorspace -> magic transform + sRGB gamma correction.

I'm working with an HP DreamColor display which uses a 2.2 gamma curve instead of sRGB.

Have you considered separating the "contrast" looks from the sRGB gamma correction and daisy-chaining them together, or would that somehow defeat the purpose? (It's quite possible I'm missing the entire point of this exercise.)

In an attempt to match the look between Gamma-2.2 and sRGB devices, I'm planning to create a sRGB->Gamma2.2 LUT which I can apply on top of the results to shimmy the values into the DreamColor's working space. The config would wind up looking something like this:

displays:
  sRGB / BT.709:
    - !<View> {name: Standard, colorspace: sRGB EOTF}
    - !<View> {name: Filmic Base Contrast, colorspace: Filmic Log Encoding, look: +Base Contrast}
    ...
  Gamma 2.2:
    - !<View> {name: Standard, colorspace: Gamma 2.2}
    - !<View> {name: Filmic Base Contrast, colorspace: Filmic Log Encoding, look: +Base Contrast,+srgb_to_gamma22}
    ...

In my mind, barring any rounding errors, this would account for the slight difference in the transfer function which mostly affects the final dark values. But I wanted to reach out and get your thoughts in case I'm missing something.

Regards.

license clarification request

I don't see a license reference in the repository.

Are you considering this derivative of Blender -> GPL ?

Are you licensing this in some more permissive license, such as LGPL or BSD 3-Clause which will still allow it to be pulled upstream?

Not Working Under Cycles On Linux Debian 8.7.1 64bit

Using a fresh install of Blender 2.78b with Filmic Blender installed, and I seemingly can't get Filmic Blender to affect how my scenes when using Cycles. Works fine under the internal renderer, but there is absolutely no change to the colours in my scene when switching to Cycles, the scene doesn't even refresh when changing the options around.
Here's a short clip of this in action:
Any user preferences or plugins that are potentially interfering? Is there more setup needed than just replacing the colormanagment directory?

default look

When using this version of Filmic with Blender 2.8, it defaults to none for the look in viewport, making it very flat. Changing look in color management panel doesn't influence viewport, only render. What should I modify (in Blender or config.ocio) to make the default look to be base contrast for example? It seems to be very helpful for final render to use log, but if it breaks viewport, it's hard to work with.

filmic Blender 2.8

Is there a way to use filmic blender on blender 2.8?

Eastman Double X Neg 4min, Agfa Agfacolor Vista 800, ect

What would it take to plug those film looks into this?

Filmic LUT for Resolve

I am having some trouble replicating the transform for use in Resolve - i've converted the filmic configuration using ociobakelut and imported it into Resolve; however when applying the LUT the image (32bit EXR) it appears clipped loosing all of the detail in the highlights.

ociobakelut --iconfig config.ocio --inputspace Linear --outputspace "Filmic Log Encoding" --format iridas_itx  --looks "High Contrast"  filmic-high.cube

Resolve Colour Space is set to Rec.709 Gamma 2.2 - any ideas?

Animations "Flicker" (includes demo video)

Filmic-Blender brings the stops we need for more accurate color reproduction in Blender. Single images look great, but animations seem to "flicker". Has anyone else seen this?

I rendered out an animation with a single sun lamp cranked up to 80 with a Size of 0.100 and the default number of Max Bounces (1024).

WATCH ANIMATION ON GOOGLE DRIVE HERE
This is a demo for a planetarium club I attend in Fort Collins, CO. Skip to 1:30 to see the filmic blender animation.

My Color Management settings are as follows:

.blend file on Google Drive
FilmicBlender_test02_filmic.blend

Repository does not include license information

Please select an appropriate license for your work and add it to the repository.

I suggest using the GPLv2 license in this case since that would make it simple to distribute Filmic Blender together with Blender in situations where that is desired since Blender itself is using the GPLv2 license.

updating instructions

I notice that blender is recently starting to include Filmic in Blender. I just got the 2.79 RC1. I am not sure if it contains everything in your repo though

The Blender RC includes the looks, but puts it in a "filmic" folder . I cannot tell if the luts are all in there. Maybe they renamed some of the stuff.

At the least, it is a heads up that the instructions might need to change. If blender is keeping the up to date versions, the instructions can just say that "filmic is included in blender by default starting with version 2.xx". I haven't tried 2.78, so maybe it is in that as well.

Glad to see this is being so well received. You deserve the attention and praise!

Adobe RGB

Please support conversion to Adobe RGB.

Loading file created with default OCIO config crashes

I've had a repeatable crash when working with this OCIO config and the VSE. Specifically, I have an older file created with another config (I've used both bassam-test and those shipped with blender), and loading the file or starting playback in the VSE will segfault. I've gotten errors on both Windows and Linux. Windows gives me the error EXCEPTION_ACCESS_VIOLATION, and Linux gives me a segfault. I am also unable to create a file in filmic config and open in default.

Oddly, I only get problems with this config, not bassam-test. With bassam-test I can go back and forth without issue.
filmic_test.blend.zip

Typo in config.ocio

Missing 2 spaces before keyword "none" line 43. Can be verified in the console when blender is launching. It prevents user from selecting display "none".

Filmic Blender clipping color picker values.

This one is easy to reproduce.
When picking a color of a shader, values above 1.0 are not registered.
The RGB sliders can go above 1.0 but it doesn't affect the render.
The Value (HSV) slider bugs out when trying to go over 1.0 and resets to 1.0.
I use this quite a lot to boost refractions and reflections, would be nice if this was fixed.

And yes, I know it's not PBR, but I don't care. ;)

minor typo fix in readme

in the readme, "Cycles" is spelled wrong at the beginning of the Grading your work section at the bottom. It is currently spelled "Cycels. Readme is super informative though. Can't wait to play with this library

problem with XNALARA

Traceback (most recent call last):
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/xps_tools.py", line 164, in execute
status = import_xnalara_model.getInputFilename(xpsSettings)
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/import_xnalara_model.py", line 78, in getInputFilename
status = xpsImport()
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/import_xnalara_model.py", line 156, in xpsImport
meshes_obs = importMeshesList(armature_ob)
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/import_xnalara_model.py", line 475, in importMeshesList
for meshInfo in newMeshes]
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/import_xnalara_model.py", line 475, in
for meshInfo in newMeshes]
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/import_xnalara_model.py", line 612, in importMesh
material_creator.makeMaterial(xpsSettings, rootDir, mesh_da, meshInfo, flags)
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/material_creator.py", line 170, in makeMaterial
makeNodesMaterial(xpsSettings, materialData, rootDir, mesh_da, meshInfo, flags)
File "/home/danilop/.programas/blender-2.80/2.80/scripts/addons/XNALaraMesh/material_creator.py", line 259, in makeNodesMaterial
imageNode.image.colorspace_settings.name = COLOR_SPACE_NONE
TypeError: bpy_struct: item.attr = val: enum "Non-Color" not found in ('AppleP3 Filmic Log Encoding', 'AppleP3 sRGB OETF', 'BT.1886 EOTF', 'BT.1886 Filmic Log Encoding', 'Filmic Log Encoding', 'Linear', 'Non-Colour Data', 'sRGB OETF')

location: :-1

Filmic Blender on Maya 2017 error.

Hello,

I tried uncommenting all the line to use in Maya but still get this message:

"config.ocio failed. yaml-cpp: error at line 47, columm 5: illegal block entry".

I use Maya 2017 update 2 by the way. At work with the same config on update 3, it works fine.
Great work by the way. Thank you.

J.

Not working on Linux Manjaro installed Blender (community repository)

I can't get filmic to work on my installed Blender on Linux Manjaro.
It works on a Blender 2.78b tar.bz version downloaded from blender.org but not on a 2.78b version installed from the Arch community repository.
Although all the filmic options are here, the colors don't change at all no matter what I choose. I don't get proper desaturation or anything else.

Specs :
Linux Manjaro 16.10.3 64-bit

pasted

I deleted original files and copy and pasted files no change, I uninstalled manually and installed manually then copy, pasted no change. I used Blender Uninstaller and installer etc. no change. I deleted original files and ran with empty colormanagement folder same no change. I downloaded new Blender (same as I was using 2.78a) no change. I have only seen one other person on YouTube mention this problem(same one that posted here) so it must be something on my end, but no clue what it could be. Download unzip was 15.1 MB all five or six of them, no luck. Really look forward to trying this though,

Blender V2.79 "Default" view for filmic blender

To sum it up and save time? I followed all of the appropriate steps up until testing the feature out. When I went to render>view it only displayed default. Nothing else. Apparently it is an issue with Blender itself and there is nothing I can do about that. However, if there is please update me. I'm a new and enthusiastic Blender fan and was dying to try this out. Thank you, have an amazing day/night.

Typo in config.ocio description

Minor issue.

On line 34,
- !<View> {name: BT.1886 ETOF, colorspace: BT.1886 EOTF}
I think this should read,
- !<View> {name: BT.1886 EOTF, colorspace: BT.1886 EOTF}

Inconsistent output between mac and other OSs

Background:
I rendered a project on the sheep-it renderfarm, which spread the load over machines with all three major OSs: Linux, Windows, and Mac.

• Blender: v2.79b
• Filmic: Whatever version sheep-it uses in conjunction with that blender version
• Compositing: Yes

Issue:
The frames rendered with MacOS were slightly darker than the frames rendered with the other OSs, Linux and Windows.

Images:
Not rendered/composited on Mac:

Rendered/composited on Mac:

Other notes:

• The machines were mostly Xeon W or Xeon E
• I can't be 100% sure that filmic is causing the issue

Add more color variance to the false colour option?

Hi, I'm from a video background so I'm quite used to using false colour to help expose my images. I've noticed that the current false colour layout within filmic blender is kind of confusing due to the use of cyan (a light colour, in the lower exposures) and similar green either side of the grey exposure.

Because of this, I thought that perhaps adjusting the colours of each EV to better match the false colour found in professional cameras such as the Arri Alexa would work better? The colours of each EV are more logical for users to grasp.

Example:
Black (clip)
Purple
Blue
Green
Dark Grey
Pink
Light Grey
Yellow
Red
White (clip)

No Apple DCI-P3 View Transforms

All iMacs from late 2015 and all MacBooks and MacBook Pros from 2016 onwards use wider gamut displays. Filmic doesn't currently support them.

blender 2.79

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

Filmic Blender as GLSL

I want to implement something like "Filmic Blender" in GLSL. Thus I have some question about the details on how the transformation works. I have found that there are two sets of LUT:s. RGB to RGB mapping, and a 1d mapping for controlling contrast:

• How are input values (those that comes from the lighting algorithm) mapped to the range [0, 64]
• When is the contrast control applied
• How does the exposure control work

Notice that reusing the same LUT may not be necessary, so some references with formulas would also be interesting.

No color mangment options on Mac (2.78)

I have installed filmic blender into my color management by replacing the default colormanagment folder with the new install and renamed it to 'colourmanagment', but when I open blender there are no extra color options in the panel. I am installing into blender 2.78 on an iMac running Sierra.

Can not install in 2.79

I followed the instructions exactly, even deleted the original 'colormanagement' folder, but after opening Blender only sRGB shows up on the list.

Ubuntu 16.04 Installation

Good morning! I have just installed Filmic Blender on my Windows 10 installation and been playing around with it. (LOVE IT by the way) But now I'm trying to install it on one of my Ubuntu installations and coming up with a blank. I tried searching for the "colormanagement" folder to no avail. I searched for the ".icio" file and found nothing. The Blender folder on Ubuntu seems not to have what I need (or what I think I need).

Does anyone have any advice or assistance on how to install Filmic Blender on Ubuntu 16? Thanks.

Broke with version 2.78c

After downloading version 2.78c, the filmic log encoding base is no longer found.

Steps taken:

• Download and install Blender 2.78c (on windows)
• Open new Blender file

Results:

• The Filmic log encoding base is no longer available under Scene Color Management.

Tried deleting current copies and copying files fresh from download, but it did not solve the problem.

please i just recently started using linux and havent a clue how i add flimic-blender to my OS. can someone take time to help me through this.

Maya 2016 error when loading

I managed to download some OCIO
But now, i have this error everytime I tried to load the OCIO:
http://imgur.com/xZv8KUp

Thank you.

Create an initial release / tag for stable versions in order to use in pipelines

First of all, thanks for the great work. It's really amazing what this can do for artists!

We want to use filmic-blender in our automated command-line application that is rendering things with blender.
To set up the process, we currently load the addon directly from the source from the master branch.
For versioning and stability of our process, it would be fantastic to have github releases or tags for each stable version.

Thank you

Getting this error in Maya 2017-2018

Installed new colormanagement folder, no results

Followed install instructions but only get default color options. Did a clean reinstall of 2.78a, replaced colormanagement folder with Filmic - same result. Noticed Blender startup console window did not report expected "could not find sRGB" etc.

Not Doing anything

Installing on a Mac

I am looking forward to using this great tool. However I am on a Mac.

The instructions indicate "Replace your current OpenColorIO configuration in Blender", does that mean within the application's package contents?

When I open the package for the Blender app it doesn't list the required folder.

Blender / Contents contains the following files:
_CodeSignature
Info.plist
MacOS
PkgInfo
Resources

What I am looking for is "BLENDER/bin/VERSIONNUMBER/datafiles/colormanagement"

Thank you for your help.

Dumb Newbie Question.

The default color management in 2.8 is now filmic, so I'm assuming that blender 2.8 comes with filmic-blender right ? I Just want to be sure, and also install the right filmic-blender. So is blender 2.8 filmc, the same as sobotka filmic-blender ?

baking gets darker

If I bake an object's "Diffuse Color", the result gets darker than the original texture, which doesn't happen with Blender's original color management. I tried different settings but all of them gave darker results. Did I miss the correct setting ?

Video Sequence Editor - crashes Blender

This may be covered in another issue, but in case I missed it, the video sequence editor currently doesn't work with the filmic-blender colorspace. Even when I set the colorspace to sRGB EOTF the video sequence editor won't load (Blender crashes). This really isn't a production blocker, as it's easy to have a second instance of Blender without filmic-blender.

I'm running MacOS Sierra 10.12.3 and Blender 2.78b

PS, thanks for this project. Filmic-blender is amazing.

Submit as a patch for Blender?

Not really an issue per-se, but I don't see why these changes shouldn't be considered for inclusion into blender as a patch. Has this been looked at?

Lighting not working

I went to test it with a regular cube on base contrast, but when I rendered it all but few of its faces were completely black. Is thee any way to fix this?