You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature you have in mind and explain what the current shortcomings are?
It's hard to know whether a representation has stored any colorspace information with its publish in the database - that data is visualized nowhere.
How would you imagine the implementation of the feature?
Add it as visible metadata for each representation in the Loader UI.
Similar to the implementation here: ynput/OpenPype#5459 (but most listed per representation).
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
Ask anyone who needs to 'check' the stored colorspace to check the representation entity data manually. But even getting to that information in raw format is hard for an artist in production because there's no easy way to get that data.
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
It's hard to know whether a representation has stored any colorspace information with its publish in the database - that data is visualized nowhere.
How would you imagine the implementation of the feature?
Add it as visible metadata for each representation in the Loader UI.
Similar to the implementation here: ynput/OpenPype#5459 (but most listed per representation).
Are there any labels you wish to add?
Describe alternatives you've considered:
Ask anyone who needs to 'check' the stored colorspace to check the
representation
entity data manually. But even getting to that information in raw format is hard for an artist in production because there's no easy way to get that data.Additional context:
No response
The text was updated successfully, but these errors were encountered: