On Wed, May 6, 2026 at 11:08 PM Andrea paz via Cin <cin@lists.cinelerra-gg.org> wrote:
I'm starting a new post because the one about Lcms2 is already too long.
Now ./configure works for me with --with-opencolorio. However, when I start CinGG for the first time, I get these lines:
[OpenColorIO Info]: Color management disabled. (Specify the $OCIO environment variable to enable.) [ocio_616 @ 0x562a521bd680] Error: Config or arguments invalid. [ocio_616 @ 0x562a521bd680] Input color space is null [ocio_616 @ 0x562a521bd680] Display is null [ocio_616 @ 0x562a521bd680] View is null [ocio_616 @ 0x562a521bd680] Failed to create OCIO processor. PluginFFilter::new_ffilter(ocio)
And the opencolorio filter doesn't show up. I'm not sure which environment variable to use. Trying to use $OCIO prevents CinGG from starting, saying that this variable doesn't exist.
There are some examples for ffmpeg CLI: https://academysoftwarefoundation.github.io/EncodingGuidelines/FfmpegOcio.ht... -vf "ocio=input=ACEScct:display=sRGB - Display:view=ACES 1.0 - SDR Video:format=rgb48,scale=in_color_matrix=bt709:out_color_matrix=bt709,format=yuv444p10" part starting with ",scale .." probably optional for us, because we use different encoding end configuration. Next in parameters description guide says: ===== Option Description config By default the filter will use the OCIO config defined by the OCIO environment variable, but this parameter allows you to explicitly specify its location. If you are getting started, you can use config=ocio://studio-config-v1.0.0_aces-v1.3_ocio-v2.1 which specifies one of the built in defaults. ==== But it also says that this filter also CPU-only for now? "It is worth noting that OCIO using the CPU is not super fast (although clearly faster than the alternative), we will explore using vulkan to accelerate this in the future."
_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org