• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

OCIO config file rules are not respected for image sequences

Explorer ,
May 17, 2024 May 17, 2024

Copy link to clipboard

Copied

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.

Bug Unresolved
TOPICS
Workflow

Views

47

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
3 Comments
Explorer ,
May 21, 2024 May 21, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Explorer ,
May 24, 2024 May 24, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Explorer ,
Jun 04, 2024 Jun 04, 2024

Copy link to clipboard

Copied

LATEST

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.

Votes

Translate

Translate

Report

Report