MaterialX and OCIO?

Forums Solaris and Karma MaterialX and OCIO?

5633 13 5


BrianHanke: Member; 448 posts; Joined: April 2018; Offline

Nov. 29, 2021 10:58 p.m.

Howdy, what's the status of being able to set OCIO colorspaces for MaterialX images? The Houdini docs say Hydra doesn't pick up the File Color Space metadata from the MatX image node. So, when rendering with Karma using a variety of MatX images (sRGB, linear, data), how is each one being interpreted? Just curious what's going on under the hood. Thanks!

Subscribe to my Patreon for the best CG tips, tricks and tutorials! https://patreon.com/bhgc [patreon.com]

Twitter: https://twitter.com/brianhanke [twitter.com]
Behance: https://www.behance.net/brianhanke/projects [www.behance.net]


BrianHanke: Member; 448 posts; Joined: April 2018; Offline

Nov. 30, 2021 11:29 a.m.

Update: I emailed SideFX support about this. Karma handles MaterialX texture colorspace as follows:

- float, vector2-4 images are treated as data (Linear, no conversions).
- color3-4 images are treated as "auto", which selects either Linear or sRGB based on the file format (sRGB: png, jpg, tiff, tga; Linear: exr, rat, hdr, pic)

So essentially it takes care of everything automatically! In my tests that's what it looked like, just wanted to confirm.


jsmack: Member; 8045 posts; Joined: Sept. 2011; Offline

Nov. 30, 2021 12:13 p.m.

BrianHanke
Update: I emailed SideFX support about this. Karma handles MaterialX texture colorspace as follows:

- float, vector2-4 images are treated as data (Linear, no conversions).
- color3-4 images are treated as "auto", which selects either Linear or sRGB based on the file format (sRGB: png, jpg, tiff, tga; Linear: exr, rat, hdr, pic)

So essentially it takes care of everything automatically! In my tests that's what it looked like, just wanted to confirm.

Yeah, it doesn't use OCIO spaces at all with that type of conversion. It's a simple gamma curve or not.


BrianHanke: Member; 448 posts; Joined: April 2018; Offline

Nov. 30, 2021 12:22 p.m.

Not ideal, but end result is close enough. I was mostly concerned about data textures getting gamma'd somehow. Seems like that's not an issue.


Yuri Serizawa: Member; 12 posts; Joined: Aug. 2013; Offline

Dec. 1, 2021 11:03 a.m.

I wish they had ACES profiles built in.


BrianHanke: Member; 448 posts; Joined: April 2018; Offline

Dec. 1, 2021 11:18 a.m.

Yuri Serizawa
I wish they had ACES profiles built in.

Would be nice. MaterialX apparently supports OCIO 100%, so hopefully the Houdini implementation will too eventually.


jsmack: Member; 8045 posts; Joined: Sept. 2011; Offline

Dec. 1, 2021 11:55 a.m.

Yuri Serizawa
I wish they had ACES profiles built in.

That would be a nightmare in a VFX pipeline setting. Instead of being obviously wrong when an environment hasn't been configured correctly, it would merely be subtly wrong--leading to delays in discovery and confusion when elements don't match. Shipping with the standard ACES configs would increase installer size considerably. It's undesirable for each app to manage its own color. OCIO is meant to be globally configured so all compatible apps share the same color configuration.

BrianHanke
Would be nice. MaterialX apparently supports OCIO 100%, so hopefully the Houdini implementation will too eventually.

Houdini already does support OCIO, the issue is materialx nodes expressing color settings in a way that doesn't translate via hydra.


Ashen: Member; 78 posts; Joined: May 2018; Offline

March 24, 2022 12:42 p.m.

So is this an issue with MaterialX or just SideFx's node implementation of it?


jsmack: Member; 8045 posts; Joined: Sept. 2011; Offline

March 24, 2022 1:47 p.m.

Ashen
So is this an issue with MaterialX or just SideFx's node implementation of it?

The issue is with Pixar's Hydra/USD


Ashen: Member; 78 posts; Joined: May 2018; Offline

March 24, 2022 1:51 p.m.

Good to know. Are there any rumblings about it being fixed in an upcoming release?

Edited by Ashen - March 24, 2022 13:52:23


TangheStudent: Member; 88 posts; Joined: Feb. 2021; Offline

July 26, 2022 2:23 p.m.

here's a simple script to convert all in one directory on Windows with default install location.

Param(
	[
		parameter(Mandatory=$true,HelpMessage="Enter directory")
	 ]
   $Dir
	)

	$files = Get-ChildItem -Path $Dir 	-Filter *ACEScg*

	foreach ($file in $files)
	{
		$newname = $file-Replace("ACEScg","rgb")
		Write-Host $newname
	 	& 'C:\Program Files\Side Effects Software\Houdini 19.5.303\bin\hoiiotool.exe' -i $Dir/$file --iscolorspace "acescg" --ociodisplay "ACES" "sRGB" -o  $Dir/$newname
	}

Edited by TangheStudent - July 26, 2022 20:01:52


BrianHanke: Member; 448 posts; Joined: April 2018; Offline

April 23, 2023 10:32 p.m.

I'm working on some MaterialX HDAs here and revisiting this topic a bit.

It seems that the MtlX Image node controls color space solely via file name. For example, image.raw.exr, image.ACEScc.exr, etc. all provide the expected color transforms.

You can use the Karma OCIO node to set color space via drop-down menu, but unfortunately it adds it on to the transform that takes place based on the file name. So, the only way to use the Karma node to go from texture_paint to scene_linear, for example, is to use a "raw" input file: raw -> texture_paint -> scene_linear. Otherwise you'll get "automatic transform based on file extension" -> texture_paint -> scene_linear.

Well, that ended up being a bit hard to explain! Hopefully it makes sense. Ideally I think it would be great to have the color space dropdown built into the MtlX Image node. I was trying to make an HDA for that, but with the color transform behavior seemingly hardcoded I guess there's no way around having to just name the files appropriately. Which probably is a good idea anyway, just not totally flexible.


jsmack: Member; 8045 posts; Joined: Sept. 2011; Offline

April 23, 2023 10:38 p.m.

BrianHanke
I'm working on some MaterialX HDAs here and revisiting this topic a bit.

It seems that the MtlX Image node controls color space solely via file name. For example, image.raw.exr, image.ACEScc.exr, etc. all provide the expected color transforms.

You can use the Karma OCIO node to set color space via drop-down menu, but unfortunately it adds it on to the transform that takes place based on the file name. So, the only way to use the Karma node to go from texture_paint to scene_linear, for example, is to use a "raw" input file: raw -> texture_paint -> scene_linear. Otherwise you'll get "automatic transform based on file extension" -> texture_paint -> scene_linear.

Well, that ended up being a bit hard to explain! Hopefully it makes sense. Ideally I think it would be great to have the color space dropdown built into the MtlX Image node. I was trying to make an HDA for that, but with the color transform behavior seemingly hardcoded I guess there's no way around having to just name the files appropriately. Which probably is a good idea anyway, just not totally flexible.

File name control of colorspace is an OCIO feature, it's not part of MaterialX. You can control the behavior with an OCIO 2.X config. The example 2.0 configs contain a filename token file name rule, but it can be disabled or defined by extension or other rules.


BrianHanke: Member; 448 posts; Joined: April 2018; Offline

April 23, 2023 10:42 p.m.

Understood, I was reviving this mostly to see if my concept of the workflow was correct. Sounds like I'm doing it right, so I'll go ahead and make an RFE with SideFX.

Quick Links

                    
                        Search links
                        Show recent posts
                        Show unanswered posts