Brylka – TooDee – PanicPost

Category: Nerd stuff

  • Understand Resolve color management

    with some help from Nuke.

    A look at Resolve and what the basic controls do to your image: without color management, when using a 3D-LUT and what changes when Resolve is switched to ACES.

    Lift / Gamma / Gain

    2.5.3. Understanding Resolve Color Management with Nuke

  • HDR content – first tests and my HDR experience

    B-Log: My HDR experience

    Read the full article about my first HDR experience.

    Looking for feedback!

    I found out that I can link a HDR-Vimeo video here on the website and watch this HDR content on a iPhone (X or 11Pro) directly on the page when viewed with Safari. I don’t even have to be in the Vimeo App for that. I did not know that this is possible.

    Sadly it doesn’t work on a iPad or MBP that support HDR as well. If the device doesn’t support HDR you will be presented with a down converted SDR version. Please note also that this page needs to be opened directly in Safari on iOS and not from within LinkedIn or Instagram.

    ACES Blackbody converted
    ACES blackbody converted
    If the HDR works for you, then you will see a big difference to these two images.

    The HDR clip is a part of the new article
    “1.6.5. Comp before/after view transform (HDR)“.

    I am able to see the HDR content:

    • on a iPhone 11ProMax (looks best)
    • on a iPadPro, but only as a direct file playback from an iCloud folder share
    • on a MBP (2018) in the finder with the Quicktime Player X, FCPX/Compressor or Resolve Studio.
    • on a MBP with inside the Vimeo APP – but only in the small preview window, as soon I click full screen, the resolution is awful.
    • on a Samsung S10, but only when it’s played back directly as a file from a google drive account.

    I am not able to see the HDR content:

    • in Safari on an iPad Pro.
    • in Safari on a MBP thats supports HDR. 
    • without the latest MacOS Catalina or iOS version.

    If you are able to see the HDR video and can give me some feedback, this would be great.

  • ACES & the sRGB-Texture IDT

    Taking a texture from the “screen” and bringing it inside the “scene”.

    In this article I focus on the sRGB-Texture IDT and the right usage in Nuke or 3D packages.

    From “scene” to “screen”
    and back into the “scene”.

    Please find the article in the menu Understanding ACES:

    “2.7. The sRGB-Texture IDT“

  • Blender Filmic to ACES

    Converting a simple scene with some textures and a HDRI

    Here comes another project that I wanted to check out and test. Can I take a very simple scene that I created in Blender out of the box and convert it to render it in ACES? For me it worked out smoothly in this case.

    • Filmic (Look None)
    • ACES sRGB
    Same scene, different view transform.

    I learned a lot on the way and I am happy to share the results. It can be also found in the menu Learning ACES:
    “1.9. FILMIC to ACES“

  • Moving into a bigger gamut

    From sRGB over display P3 to ACEScg – a look at gamut sizes and their relations.

    This a another new entry in the menu Learning ACES:
    “1.8. Moving into a bigger gamut“

  • Linearizing images to use as a texture

    with Affinity Photo, Nuke and Blender.

    A look at what happens when you linearize a texture, render it in a scene and use a different view transform than the initial image/texture had.

    • Drawing from Procreate
    • Blender Filmic Rendering with shading

    This a a new entry in the menu Learning ACES:
    “1.7. From images to textures“

  • A look at view transforms

    and what it means to work under or on top of them.

    In the process of writing a new article for the website about textures I digged up some older notes and finally added them here.

    • scene referred
    • display referred
    • three spotlights hitting a wall

    Find it in the menu Learning ACES or here:
    “1.6. Adding “colors” before/after a view transform“

  • Blender & ACES

    Limitations with version 2.83 and up to 2.90.3 alpha

    Today (12th of May 2020) I filed a bug or limitation when working with 8-Bit textures in Blender that need a colorspace transform. So I added some notes of other limitations I ran into in the last weeks and months while exploring Blender & ACES:

    • All color images should be EXR files in the colorspace ACEScg – in this way they don’t need any colorspace transform inside Blender.
    • Colorspace transforms in Textures (Input – Generic – sRGB Texture) will result in imprecise or sometimes wrong results when the image texture is a 8-Bit file! (the transforms should happen in floating point precision)
    • Non-Color image texture files e.g. bump or normal maps need to have the color space set to “raw” (no gamut or gamma mapping) – then there is not problem when using JPG/PNG files
    • Blender misses an option to select the OCIO file in the preferences – at the moment you must set the OCIO environment variable before starting Blender.
    • The list of colorspaces are not sorted in categories like it is in Nuke for example. The list is so large and long you need a giant screen to see them all and be able to select one with is at the end of the list – as a workaround you can temporally scale down the Resolution Scale smaller than 1.0 in the Interface/Display Preferences.
    • Be aware that you are working in a far bigger gamut of ACEScg – I wrote an article called Understanding Gamut with ACES and Blender about this topic.
    • The Blackbody shader which doesn’t really works in ACEScg.
    Blender & ACES: The blackbody shader on a LED bulb of 2700K shows a wrong result – the light is too red.
    Blender & ACES: Using a linear sRGB to ACEScg converted color value for the LED bulb – now the result looks right.

    Go to the page for some more detailed information.

  • Flame & ACES

    TAG ONLY – AUTO CONVERT – VIEW TRANSFORM
    One of many possibilities to work with ACES in flame.

    It’s time to note down some flame related ACES stuff. Here is the first article.

    How to work with ACES material and do some basic online work before exporting a ProRes Master for a client.

    Click here to read it or find it in the menu “Panicpost – Understanding ACES”.

  • Resolve & ACES

    Deliver ProRes4444 with different ODTs

    Metadata Madness

    Resolve writes different color space related metadata when working in ACES into a ProRes file depending on the ODT you have selected.

    I wanted to know how this metadata is used when reviewing the ProRes files on a Mac with the Quicktime Player and VLC or when using the Apple Compressor to generate smaller files for client send-outs.

    This is another article in the “Learning ACES” menu.

    2.5.2. TD_ColorBars ACES Export from Resolve