Skip to main content
Participating Frequently
May 17, 2024

OCIO config file rules are not respected for image sequences

  • May 17, 2024
  • 4 replies
  • 682 views

When using an OCIO config with file rules in place, it seems as though image sequences do not respect the file rules. For example, I've set EXR file types to come in as ACEScg. This works for single EXR files but not for EXR sequences. 

 

This is what I have in the config for the file rules. As you can see, anything with EXR extension should be flagged for ACEScg while everything else will default to Raw. 

 

file_rules:
  - !<Rule> {name: OpenEXR, extension: "exr", pattern: "*", colorspace: ACEScg}
  - !<Rule> {name: Default, colorspace: Raw}

 

However, with this set, all EXR image sequences get missed and come in as Raw. 

Also, it's not just EXR sequences. I just did a test with PNG sequences and making a rule to interpret PNGs as "sRGB - Texture". Again, the single PNG comes in correctly while the PNG sequence gets missed and comes in as Raw.

 

Since I can't attach the OCIO config or EXRs, you can recreate this by creating a custom version of the 1.3 Studio config. Simply add the file rules mentioned above. Then import some test EXRs twice, once as a single image and another time as an image sequence. Notice how they're intepreted differently.

4 replies

Participating Frequently
September 13, 2024

Hello, I hope this is fixed in AE 2025. Please let me know if you've seen this or even care to support OCIO properly for pipelines. Thanks.

Participating Frequently
June 4, 2024

Hello Adobe,

 

Any updates or information on this? It's pretty frustrating that we have some nice features like OCIO built in, but there are still things in place that break in a studio pipeline. This is one of them.

Participating Frequently
May 25, 2024

I am able to make a rule that catches all image sequences by checking that there are no periods in the path. So it seems AE is only reporting the parent path rather than the full path to the file. Therefore, the OCIO File Rules won't be able to detect the file types for sequences. The rule uses a regex to catch any path without a period in it which means there's no file or extension in the path to read.

  - !<Rule> {name: Sequence, regex: "^[^.]*$", colorspace: ACEScg}

So while this works to catch EXR sequences, it also catches any other sequences - PNG, JPG, etc. and will apply the wrong color space. So it's unusable. This needs to be fixed.

 

Thanks.

Participating Frequently
May 21, 2024

If you need assistance creating file rules, here's the documentation.

https://opencolorio.readthedocs.io/en/main/guides/authoring/rules.html

 

I hope this is an easy fix and can be released in an update soon. Or if I'm doing something wrong to access the image sequence file rules, let me know. Having the file rules in place really make the pipeline much smoother and reliable.