AMPAS IDT calculator Standstill - BlackboxCamera

Hi everyone, ACES 2.0 is a celebration. Thank you to everyone that works hard on this amazing workflow to exist. The new DRTs are amazing. But it is not so much to render an image that is the problem today, but much more difficult to get inside the workflow. Making an IDT by hand is very hard. Just understanding the per channel 1D Linearization, normalisation (illuminant and 18%grey linear scene match), Chroma Adpat D60 and Colour Matrix 3x3 is incredible. The IDT calculator is going to make life so easy. But here is the thing, I can only dream about ACES. The IDT calculator refuses to input my files, Implicit or Explicit structure folder, it is the same outcome, it claims to have no files to be found even after checking the explicit JSON. I used both local and web Idt calculators. Someone needs to build a PDF manual soon because left in the dark if anything goes wrong. I have used Tiff 16bit Integer out of davinci resolve. I’ve tested Log and gamma cameras, even a debayered DNG linear sensor data (not linear scene yet). and this do not work and claims these errors:

[2025-08-23 13:56:47 +0000] [14] [DEBUG] POST /_dash-update-component
ERROR:app:Exception on /_dash-update-component [POST]
Traceback (most recent call last):
File “/usr/local/lib/python3.12/site-packages/flask/app.py”, line 1473, in wsgi_app
response = self.full_dispatch_request()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.12/site-packages/flask/app.py”, line 882, in full_dispatch_request
rv = self.handle_user_exception(e)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.12/site-packages/flask/app.py”, line 880, in full_dispatch_request
rv = self.dispatch_request()
^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.12/site-packages/flask/app.py”, line 865, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) # type: ignore[no-any-return]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.12/site-packages/dash/dash.py”, line 1405, in dispatch
ctx.run(
File “/usr/local/lib/python3.12/site-packages/dash/_callback.py”, line 529, in add_context
raise err
File “/usr/local/lib/python3.12/site-packages/dash/_callback.py”, line 518, in add_context
output_value = _invoke_callback(func, *func_args, **func_kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.12/site-packages/dash/_callback.py”, line 47, in _invoke_callback
return func(*args, **kwargs) # %% callback invoked %%
^^^^^^^^^^^^^^^^^^^^^
File “/home/ampas/idt-calculator/apps/idt_calculator_camera.py”, line 1372, in compute_idt_camera
_IDT_GENERATOR_APPLICATION.extract(_PATH_UPLOADED_IDT_ARCHIVE)
File “/home/ampas/idt-calculator/aces/idt/application.py”, line 299, in extract
self._update_project_settings_from_implicit_directory_structure(
File “/home/ampas/idt-calculator/aces/idt/application.py”, line 156, in _update_project_settings_from_implicit_directory_structure
attest(colour_checker_directory.exists())
File “/usr/local/lib/python3.12/site-packages/colour/utilities/common.py”, line 464, in attest
raise AssertionError(message)
AssertionError

I’m not a programmer, and I sure not don’t want to do the IDT by hand. Is there anyone outthere that has made an IDT with the AMPAS idt calculator and it worked? I would love to know how to make it work. I’ve used the EVfloat folder values and even tried the regular EV scale. But it always fails. In anycase, when will an official documentation be produced to avoid issues like that and this tool more accessible for normal filmmakers? Thank you to all of you and this amazing community, special thanks to Thomas for the design of this IDT, I probably don’t know how to use it and it’s not the designer’s fault. There is too much to learn in life…

Thomas replied to me and he took the time to find what was wrong with the asset and why it didn’t work. It’s very important to create a data directory with a data subfolder. For negative EVs you must use ascii negative sign, the sign is longer. If you don’t do that the IDT calculator won’t work.

So I tried to make them for my consumer cameras, training myself and archive work. Mini DV Cameras, GoPros, DSLRs, anything I could grab… So, I measured the nits value of my Grey Cards, and my Sekonic told me the shutter speed value with a 50 ISO @ F4 lens system.
So I applied to it, and then when aquirering the footage in Davinci, YRGB None Color Managed, Working Space REC709/REC709 and Output space REC709/REC709, Applyed no nodes anyway… but guess what… The camera placement of middle grey was:
Full-data for GoPro Hero7=0.660
studio-swing for Panasonic DV=0.660
What?

The middle grey is much much higher than the official REC601/REC709 OETF limited-range=0.413

What was going on?
Surely my sekonic was dead right?
I took my camera, put it in front of my middle grey and made it do an auto shutter to force it to show its own placement and there it was…
The freaking same result…
And these cameras have very small amount of stops above middle grey…

And of course it prooved to be a huge problem later during the IDT calculation with the Ampas IDT Calculator Black Box Camera. I had no stop above middle grey to offer because the brightest patche was starting to clip at nominal exposure. The IDT calculator prevents me from doing the IDT because there is no above 0EV exposures.
I find that really estonishing.
And again I might be crazy! I missed something fundamental!

I thought a recording colour space and transfer function had to be respected by a camera maker… They already have secret sauce to polute the 3x3 matrices… Looks like it’s not enough. But on most of my consumer cameras? And all the exact same middle grey placement?!