Copy link to clipboard
Copied
Gamut warning with colors. I assume there are 3 reasons when the warning is shown. 1. Whites to high, 2. Blacks to low. 3. Color not legal for color space. Over saturated or not legal in color space. When it comes to hue vs hue adjustment in curves the warning disappears just by clicking on the color.
I have generated this ai response. Which explanation is correct?.
GPT-4o mini
If the gamut warning disappears after selecting a color using the Hue to Hue adjustment without making any visible changes, it may not necessarily be a bug, but rather a feature of how Premiere Pro handles color adjustments.
Possible Explanations
Color Space Re-evaluation: When you select a color with the Hue to Hue tool, Premiere Pro may automatically re-evaluate the color's position within the color space, effectively recalibrating it to fit within the gamut. This could lead to the warning disappearing even if no visible adjustment was made.
Threshold Adjustment: The software might have a threshold for what it considers out of gamut. By selecting the color, it may be adjusting the internal parameters that determine whether a color is flagged as out of gamut.
Temporary Glitch: While less likely, it could be a temporary glitch in the software. If the warning consistently disappears without any adjustments, it might be worth restarting the application or checking for updates.
Copy link to clipboard
Copied
What do the scopes show? You do use the scopes, right?
Waveform (I prefer YC no chroma variant) would show tonal range, including excursions.
Vectorscope shows saturation ... including excursions.
Drag/drop a screen-grab of your scopes onto your text reply box, the answer will be pretty easy to give.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
SDR/Rec.709, internationally, is specified as sRGB primaries, white point of D65.
See the hexagonal shape on the Vectorscope, the lines that go from the individual color boxes? Stay within that bounding box, you are probably good, though there might be a momentary excursion. So back to a bit within them, and you'll be fine.
Hue v Hue does one thing, Hue v Sat another. Which is why they exist.
Hue v Hue changes the specific hue to another hue, so say you can pull the green and blue towards cyan, for the good old orange & teal look. It doesn't change saturation, just what hue maps to where.
Hue v Sat changes saturation for specific hues. So in your case, you could use the Hue v Sat to pull that cyan spike back within bounds.
Or of course, you could also dial down saturation in either the Basic or Creative tab Saturation controls.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now