UnaiM

The magic of Kronos

(AKA Why My Rolling Shutter Fix Didn’t Match with RollingShutter) – 20th December 2014
WARNING: doesn’t come to any solution.

My last post was about trying to recreate The Foundry’s RollingShutter plugin, using the new Kronos 2 technology instead of the old one, which the discontinued plugin was left with. And while the proposed solution benefitted from Regularized motion estimation, when switching back to Local it was clear that RollingShutter still won over it. So there’s something missing that I didn’t recreate, and have yet to figure out.

---

UnaiM

“Just convert everything to ACEScg”

An investigation on whether “respecting” plate colour in a VFX pipeline makes any real difference

Motivation

Until 2020, I always had worked either without any real colour management, or in an environment where everything was converted to (and encoded in) ACEScg on ingest, effectively before anyone used it. But I always had a hunch that this solution wasn’t “pure”— if the Academy had devised another linear colour space (ACES2065–1) for archival, it had to have a reason.

UnaiM

"""Requirements:
    Python 3.7.2+
    NumPy 1.14.5+
    OpenColorIO 2

The xxhash Python package v2+ is recommended, which uses the xxHash library v0.8+.
"""

import hashlib
import os

UnaiM

import functools
import typing

from PySide2 import QtCore, QtWidgets


class _TopLinkedTable(QtWidgets.QTableView):

    def __init__(self, other):
        super().__init__()

UnaiM

"""Time-dependent hash generation.

The original use-case called for the hashes to be short and easy for humans to
communicate, in a context where it doesn't matter if hashes repeat themselves after
some days, plus there's an implicit guarantee that seconds will pass between hash
requests, hence the `resolution` argument.
"""

from collections import abc
import datetime