colormanager: Remove hard coded color space

The hard coded color space was causing custom configs to crash if they
didn't contain that specific color space.

Also sets the default role in the config to sRGB EOTF to keep
consistency with previous behaviour
This commit is contained in:
Thomas Wilshaw
2022-03-09 12:50:34 +00:00
parent f75e91cf4d
commit 6ccebcd988
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -50,7 +50,7 @@ ColorManager::ColorManager() :
// Set config to our built-in default
SetConfig(GetDefaultConfig());
SetDefaultInputColorSpace(QStringLiteral("sRGB OETF"));
SetDefaultInputColorSpace(config_->getCanonicalName(OCIO::ROLE_DEFAULT));
}
OCIO::ConstConfigRcPtr ColorManager::GetConfig() const
+1 -1
View File
@@ -16,7 +16,7 @@ luma: [0.2126, 0.7152, 0.0722]
description: A filmlike dynamic range encoding set for Blender
roles:
default: Linear
default: sRGB OETF
reference: Linear
scene_linear: Linear
data: Non-Colour Data