USD import: investigate texture color space conversion issue #93904

New Issue

Michael Kowalski · 2021-12-09T15:42:00+01:00

Michael Kowalski commented

2021-12-09 15:42:00 +01:00

@brurpo Reported the following issue:

When exporting USD from maya to blender none of the textures comes with the correct color space, they are all srgb.
Importing on maya again, on a clean scene, does not have this issue, all textures are loaded with the correct color space.
Is there a workaround for this, or is this planned?

I'll be looking into this.

@brurpo Reported the following issue: > When exporting USD from maya to blender none of the textures comes with the correct color space, they are all srgb. > Importing on maya again, on a clean scene, does not have this issue, all textures are loaded with the correct color space. > Is there a workaround for this, or is this planned? I'll be looking into this.

Michael Kowalski self-assigned this 2021-12-09 15:42:00 +01:00

Michael Kowalski commented

2021-12-09 15:42:00 +01:00

Added subscribers: @brurpo, @makowalski

blender-admin commented

2021-12-09 15:42:00 +01:00

#97136 was marked as duplicate of this issue

Michael Kowalski commented

2021-12-09 15:42:57 +01:00

@brurpo thank you for the test assets to reproduce this. I'll look into this and will let you know what I find.

BRUNO RANTIN PO commented

2021-12-09 18:47:36 +01:00

@makowalski You are awesome! Let me know if you need anything, even if you want a call for me to show you the process or if you want a simpler usd.

BRUNO RANTIN PO commented

2021-12-09 21:53:12 +01:00

Hi @makowalski ! Recently, maya released an update that fixed this, so it was not a problem on blenders side afterall. What was weird is that maya was importing the colorspace correctly, maybe it used something that only maya could read and now it uses something that is more generic?
If you want, I can send you the new exported USD.
Cheers.

Hi @makowalski ! Recently, maya released an update that fixed this, so it was not a problem on blenders side afterall. What was weird is that maya was importing the colorspace correctly, maybe it used something that only maya could read and now it uses something that is more generic? If you want, I can send you the new exported USD. Cheers.

Michael Kowalski commented

2021-12-10 02:18:43 +01:00

@brurpo I'm glad there's a fix in Maya!

I tracked the issue down to the following: the colorSpace metadata in that USD is given as "Raw" (note the capitalization). Lowercase "raw" is the actual standard, I believe. In my code I was checking for "raw" as well as "RAW" (all caps) which is another variant I've seen. If I change my code to do a case-insensitive string comparison against "raw", the color space comes is correctly for this USD.

I'm guessing that Maya updated their code to use the standard "raw" token now, so we'll have to consider whether doing this fix is worth the effort. I'll give it some thought.

@brurpo I'm glad there's a fix in Maya! I tracked the issue down to the following: the `colorSpace` metadata in that USD is given as "Raw" (note the capitalization). Lowercase "raw" is the actual standard, I believe. In my code I was checking for "raw" as well as "RAW" (all caps) which is another variant I've seen. If I change my code to do a case-insensitive string comparison against "raw", the color space comes is correctly for this USD. I'm guessing that Maya updated their code to use the standard "raw" token now, so we'll have to consider whether doing this fix is worth the effort. I'll give it some thought.

Philipp Oeser commented

2022-03-10 11:34:02 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-03-10 11:34:02 +01:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Philipp Oeser commented

2022-03-10 11:34:02 +01:00

In #93904#1269872, @makowalski wrote:
@brurpo I'm glad there's a fix in Maya!

I tracked the issue down to the following: the colorSpace metadata in that USD is given as "Raw" (note the capitalization). Lowercase "raw" is the actual standard, I believe. In my code I was checking for "raw" as well as "RAW" (all caps) which is another variant I've seen. If I change my code to do a case-insensitive string comparison against "raw", the color space comes is correctly for this USD.

I'm guessing that Maya updated their code to use the standard "raw" token now, so we'll have to consider whether doing this fix is worth the effort. I'll give it some thought.

@makowalski: I assume this can be confirmed then?
It would still be good to have an example .USD here (maybe alongside screenshots expected vs. actual behavior) just in case someone else will end up looking at this

> In #93904#1269872, @makowalski wrote: > @brurpo I'm glad there's a fix in Maya! > > I tracked the issue down to the following: the `colorSpace` metadata in that USD is given as "Raw" (note the capitalization). Lowercase "raw" is the actual standard, I believe. In my code I was checking for "raw" as well as "RAW" (all caps) which is another variant I've seen. If I change my code to do a case-insensitive string comparison against "raw", the color space comes is correctly for this USD. > > I'm guessing that Maya updated their code to use the standard "raw" token now, so we'll have to consider whether doing this fix is worth the effort. I'll give it some thought. @makowalski: I assume this can be confirmed then? It would still be good to have an example .USD here (maybe alongside screenshots expected vs. actual behavior) just in case someone else will end up looking at this

Michael Kowalski commented

2022-03-14 18:28:55 +01:00

Hi @lichtwerk. Thanks for following up on this. Yes, this bug can be confirmed, and I'll provide a USD example, as you suggested. This is a relatively simple change, and I will most likely make the fix after the latest USD Preview Surface import patch (https://developer.blender.org/D13297) has been approved and merged into master.

Michael Kowalski commented

2022-03-14 18:29:09 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Michael Kowalski commented

2022-03-14 23:21:42 +01:00

I'm uploading the notebook.7z archive originally provided by @brurpo that contains the USDs and textures that exhibit the behavior. Note that this example is for Windows only, as it references textures in the c: drive. To test on Windows, extract the contents under the c: root for the texture paths to resolve correctly.

notebook.7z

An example of the issue is that the roughness textures in the USD

asset inputs:file = @C:/notebook/TEXTURES/ESTRUTURA_TOP/NOTEBOOK_ESTRUTURA_TOP_SG_Roughness.png@ (
                    colorSpace = "Raw"
                )

is imported with color space sRGB:

I'm uploading the notebook.7z archive originally provided by @brurpo that contains the USDs and textures that exhibit the behavior. Note that this example is for Windows only, as it references textures in the `c:` drive. To test on Windows, extract the contents under the `c:` root for the texture paths to resolve correctly. [notebook.7z](https://archive.blender.org/developer/F12927937/notebook.7z) An example of the issue is that the roughness textures in the USD ``` asset inputs:file = @C:/notebook/TEXTURES/ESTRUTURA_TOP/NOTEBOOK_ESTRUTURA_TOP_SG_Roughness.png@ ( colorSpace = "Raw" ) ``` is imported with color space `sRGB`: ![image.png](https://archive.blender.org/developer/F12928042/image.png)

Germano Cavalcante commented

2022-04-07 19:24:39 +02:00

Added subscribers: @weirdmonkey2807, @mano-wii

Kevin Collins commented

2022-05-20 01:08:59 +02:00

Added subscriber: @codeloadgame

Bastien Montagne added this to the Pipeline, Assets & IO project 2023-02-09 15:40:38 +01:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

USD import: investigate texture color space conversion issue #93904