<div dir="auto"><div dir="auto">Slightly more from my n-th research into colorspaes.<div dir="auto"><br></div><div dir="auto"><a href="https://www.slashcam.com/news/single/Adobe-After-Effects-gets-ACES-workflow-via-OpenCol-17721.html" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://www.slashcam.com/news/single/Adobe-After-Effects-gets-ACES-workflow-via-OpenCol-17721.html</a><br></div><div dir="auto"><br></div><div dir="auto">Apparently AE (After Effects) got ACES via OCIO just recently:</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">==== quote ==</div><div dir="auto">The
traditional Adobe colour management engine (which uses ICC profiles)
has to be switched to OpenColorIO in a project menu for this.<p></p> <br> <br>Afterwards, working, composition, display and export colour spaces can be assigned. <br> <br>A
plug-in effect "OCIO Color Space Transform" has also been thought of.
This is a colour space conversion effect implemented with the
OpenColorIO engine that can be used anywhere in the composition. This
can work with CDL or LUT files. Complex 3D LUT interpolations are
optionally performed tetrahedral, but this requires a supported(end)
GPU. <br></div><div dir="auto"><br></div><div dir="auto">====</div><div dir="auto"><br></div><div dir="auto">not sure how "working" vs "composition" differs ....</div><div dir="auto"><br></div><div dir="auto">Long 13 part series on color management in AE again</div><div dir="auto"><br></div><div dir="auto"><a href="https://www.provideocoalition.com/color-management-part-13-opencolorio-and-after-effects/" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://www.provideocoalition.com/color-management-part-13-opencolorio-and-after-effects/</a><br></div><div dir="auto"><br></div><div dir="auto">=== quote ===</div><div dir="auto"><br></div><div dir="auto">As I said above, using OpenColorIO is a conscious decision to do color
management manually, instead of using the built-in color management
system. And this means you need to have a solid understanding of what
you’re trying to do, and why. OpenColorIO was created for use on large
scale Hollywood productions, and the ACES workflows that it’s used with
are designed to future-proof commercial content.<br></div><div dir="auto"><br></div><div dir="auto">==== </div><div dir="auto"><a href="https://www.provideocoalition.com/color-management-part-9-workflow-theory/" target="_blank" rel="noreferrer">https://www.provideocoalition.com/color-management-part-9-workflow-theory/</a><br></div><div dir="auto"><br></div><div dir="auto">== quote ===</div><div dir="auto"><br></div><div dir="auto">As explained in the video above, the point of a color managed workflow
is that we assign our project a colorspace, and any assets which have a
different colorspace are converted to match the project. But if every
component in our workflow (assets, project, monitor and output) are the
same, then no conversion will be needed. <br></div><div dir="auto">===</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">c++ example looks simple, but I have no idea if it works transparently enough to try ...</div><div dir="auto"><br></div><div dir="auto"><a href="https://opencolorio.readthedocs.io/en/latest/guides/developing/developing.html" rel="noreferrer noreferrer noreferrer" target="_blank">https://opencolorio.readthedocs.io/en/latest/guides/developing/developing.html</a><br></div><div dir="auto"><br></div><div dir="auto">===</div><div dir="auto"><strong>Convert your image, using the Processor.</strong> Once you have a CPU or GPU processor, you can apply the color transformation using the “apply” function. In <a href="https://opencolorio.readthedocs.io/en/latest/guides/developing/usage_examples.html#usage-applybasic-cpp" rel="noreferrer noreferrer" target="_blank">C++</a>, you may apply the processing in-place, by first wrapping your image in an <code>ImageDesc</code>
class. This approach is intended to be used in high performance
applications, and can be used on multiple threads (per scanline, per
tile, etc).<br></div><div dir="auto"><br></div><div dir="auto">===</div><div dir="auto"><br></div><div dir="auto">so, ICC vs OCIO actually a thing ... o.o</div><div dir="auto"><br></div><div dir="auto">Currently in cingg you have colorspaces plugin and ffmpeg's LUT plugin, but no support for color-managed display or embedding icc profile in media ....</div><div dir="auto"><br></div><div dir="auto">so, *may be* you can add colorspace plugins for equating different media files manually, and then use external tools (olive-editor?) for viewing/embedding profiles ....</div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пт, 26 мая 2023 г., 20:56 Phyllis Smith via Cin <<a href="mailto:cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">cin@lists.cinelerra-gg.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">Updated GIT manual with Andrea's additional screen shot. This manual section as previously written by Andrea is a very helpful explanation. It is too bad that CinGG does not have better color management and most likely never will. ...Phyllis<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 26, 2023 at 10:31 AM Andrea paz via Cin <<a href="mailto:cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">cin@lists.cinelerra-gg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I added an image as you requested. thanks for the hint.<br>
> I guess my 'work' would benefit from RGB-Float, and only at the output<br>
> clamp to 8bit.<br>
In theory, yes. But in practice many of CinGG's internal processes<br>
(e.g., effects) do their own conversions. The result may be<br>
unpredictable. Everyone has to look for a satisfactory worflow....<br>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div></div>