Currently Vuo does not understand the difference between RGB that is in linear - or has an OETF (gamma) applied.

Attached is an example composition that shows the difference between the two- when using a blur.

I suggest that there be a linear data cable type, which can be converted easily. No image processing (compositing, blur, etc) should happen to the data when their is an OETF on the data.

This would mean that Vuo would need to read the ICC profile of the image, and remove the EOTF based on the tags. (And also allow the user to convert from known colour spaces - sRGB, P3, rec.2020 etc)

This is clearly shown in a blur effect, with an image with saturated colours.

Simply because x^2 + x^2 != (x+x)^2

Here are two screenshots from the attached Vuo composition, note that in both the blur effect is identical, the only difference is the top one has: OETF removed -> Blur -> OETF applied.

NOTE: for the attached example composition- I am using the approximation of pow(src, 2.2) for sRGB OETF


Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro


●●○○ — A few weeks of work


●○○ — Appeals to current community

Currently, Vuo's colors and textures use the sRGB colorspace. Our overall goal for Vuo is to make it easy for people to get professional results, without having to master underlying technical details. So, we'd like to approach this a bit differently.

Our plan would be to audit Vuo's image filter nodes and figure out which ones handle colorspace properly as-is, and which ones don't (presumably blur is one that doesn't), and fix the ones that don't (i.e., make them convert input textures from sRGB to linear (when necessary), perform the filter, then convert linear back to sRGB (when necessary)). We think ideally this should all happen automatically so composition authors don't need to worry about it. Part of the fix would be to add an "Apply ICC Profile" node, to facilitate advanced color management.


Feature status

  • Submitted to
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for.

If anyone would like to help this happen sooner, we're also accepting open source contributions and commissioned work.

Read more about how Vuo feature requests work.