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
ocioview currently has inspectors for curves (#1845 ) and color volumes ( #1875 ).
This task would involved building a QGraphicsScene or OpenGL viewport which displays an interactive CIE chromaticity diagram, and plots the primaries of the currently viewed transform (if known) as a triangle, with the option to scatter plot all or some of the current image's transformed pixels into their xy coordinates over the diagram.
The text was updated successfully, but these errors were encountered:
I was actually rewriting colour-analysis using WebGPU via pygfx:
which brings me to the following question and point:
Is there an interest consolidating forces and having me contributing some of my code and continuing in ocioview? This would probably add some more dependencies, e.g. Colour, Pygfx, wgpu-py, etc...
OpenGL is on the way out, and I'm thinking that it would be future proof to embrace Vulkan and Metal via WebGPU.
That awesome @KelSolaar ! I think it would be great to consolidate these projects. I have no objections to introducing new Python package dependencies for ocioview. I used Qt3D for #1875 , but could see that being moved to another GPU implementation too.
ocioview currently has inspectors for curves (#1845 ) and color volumes ( #1875 ).
This task would involved building a QGraphicsScene or OpenGL viewport which displays an interactive CIE chromaticity diagram, and plots the primaries of the currently viewed transform (if known) as a triangle, with the option to scatter plot all or some of the current image's transformed pixels into their xy coordinates over the diagram.
The text was updated successfully, but these errors were encountered: