Please describe the issue you have encountered?

New implementation of explicitly defined direction of collected colorspace datas had introduced bug in CG render AOV collected colorspaces. The representation's colorspaceData meant to be from beginning reflecting only current state but historically it was missunderstood and in CG was used as future colorspace data. This is no confusing the new implementation of https://github.com/ynput/ayon-core/blob/ec2a18ab4ac82cb24ca81e4173e6e7897abf6a37/client/ayon_core/lib/transcoding.py#L1066. 

.

Here is quite detailed analyses of the problem: https://github.com/ynput/ayon-core/pull/1268/files#r2156555474

.

This needst to be fixed in following way:

• display and view data from viewport in Maya or Houdiny should be collected and set to instance.data, rather then to representation's colorspaceData
• EXR AOV should have colorspace key value set to some default value inherited from render settings. This needs to reflect current state of the pixel values only
• What ever instance.data keys related to potential target (future) transformation should be used in case ExtractOIIOTranscode[](https://github.com/ynput/ayon-core/pull/1268/files#r2156555474%60) plugin here 

  ayon-core/client/ayon_core/plugins/publish/extract_color_transcode.py

  Line 20 in ec2a18a

  class ExtractOIIOTranscode(publish.Extractor):

  is not having any targets defined in active preset.

How to replicate the issue?

No response

Additional context:

link to discussion on Discord
(might be a private channel)

This issue was automatically created from AYON ticket YN-0135