Hello, it would be very useful to add a text field in the native color picker to edit the color as HEX string.
I’ve been thinking about this feature for a bit. The issue is that it’ll be less and less useful in the future. As far as I can tell most of the time HEX values for colors are used is for describing 8-bit sRGB colors. As more and more monitors standardize on DCI-P3 or higher color spaces, and 10-bit color, the usefulness of these old color values goes down.
As a dev that works with Ad Agencies to build out from their designs. This is a much needed native feature. Most of the time I am working off figma, PSD, or AI files. Having to convert colors is a big pain in the ass. Luckily @dylanroscover created a hexler which is a component you can copy any hex value into and it converts it to an RBG field you can copy and paste from. But I would still love to see the option natively in the color palette in TD.
Direct Download link: https://github.com/dylanroscover/TDComponents/raw/main/release/hexler-v0.1.5.tox
Figma prioritizes hex, and for good reason (it’s simple and easy!):
@malcolm I totally get where you’re coming from, however I don’t see hex going away anytime soon, as for UI it’s accurate “enough”.
From a UX perspective, it’s quicker to copy/paste a hex code than it is to set a vec3 for rgb. Accuracy is one thing, however I think in this thread we’re speaking to improving the UX in TouchDesigner… hex is among the lowest hanging fruit for that.
It would great to have a conversation about the needs of folks doing UI/UX with TD and see if there isn’t a roadmap of features that could be added for that subgroup of TD users. We may be fewer but likely purchases more licenses on a regular bases for permanent installs. Kiosk, Interactive LED Walls, Trade Show Games, etc.
Hex can be assumed to come from sRGB, however, it seems Oklch is gaining traction very quickly.
Just dropping my +1 here.
Still would be very welcome as at least at the moment I do still get hex codes 90% of the time.
Ok thanks for the feedback. I’ll take a closer look at it.
I’ve added oklab in one spot, for the Ramp TOP interpolation. I do see those color spaces being added more in other places.
I can’t find examples of Oklch using HEX though. The CSS pages use floats for their examples of using Oklch, unless I missed it.
Ah, what I meant is that Oklch could eventually replace the HSL controls in the dialog so we can have wider gamuts available in there. As for HEX conversion, there is a color explorer here: OKLCH Color Picker & Converter , however, I can’t vouch for its correctness. The W3C standards put the HEX notation firmly in sRGB land (CSS Color Module Level 4), just like rgb(), so it looks like it should be: HEX → sRGB components → Working Color Space

