> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/scopebox/palette-types/rgb-histogram.md). # RGB Histogram The RGB Histogram displays the intensity of the Red, Green and Blue signals. Similar to the Luma Histogram, the leftmost column is the lowest intensity and the rightmost is the highest intensity. The RGB histogram is particularly useful when working with chroma key shots. The key color should be as even as possible for clean keying. Doing so produces a very tight clump of long bars rather than a wider clump of short bars. ![](https://1060439511-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LStRji2w1AYja1bLBFv%2Fuploads%2FrH2n1ptJjjtUzIhlnea3%2FRGBHistogram.png?alt=media\&token=e289fe07-b621-4dce-bff5-bb7fbd4d406b) ### Controls #### Layout The layout control allows you to adjust whether you're viewing the individual R, G, and B components separately, or overlayed as a single composite. #### Scaling The RGB Histogram can be toggled between "log" and "linear" scaling. In log mode, each horizontal graticule represents an order of magnitude - 10, 100, 1000 and so on. This means that even levels with relatively low frequency within your signal will be easily visible within the palette. Linear scaling causes the vertical axis to be scaled to the height of the most populated intensity for a given channel. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hedge.video/scopebox/palette-types/rgb-histogram.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.