> 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/hml-balance.md).

# HML Balance

The HML Balance palette can be thought of as three distinct vectorscopes, displaying information about the "high," "mid," and "low" components of your signal. This can be helpful for identifying color casts in specific luminance regions of your image, like shadows or highlights.

Because the crosspoints between the three vectorscopes are configurable, this palette can be filtered in a variety of ways to allow you to focus on just one component of your signal.

Many of the controls are similar to those found on the vectorscope, but there are some HML-specific controls as well.

![](https://1060439511-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LStRji2w1AYja1bLBFv%2Fuploads%2Fl5Ms6R7MBlugku45ARas%2FHMLBalance.png?alt=media\&token=0a1003b7-4059-403b-9e60-9d0aebfbeb88)

### Controls

#### Zoom

The Zoom control is a variable zoom, allowing you scale up the scopes to see even the most minute detail. Keep in mind that with an 8-bit signal, the amount of resolution available in the display is inherently very limited.

#### Luma Threshold

The "low" and "high" values act as low- and high-pass filters, respectively. Everything below the value entered in the "low" field will be displayed on the low scope, everything above the value entered in the "high" field will be displayed in the high scope, and everything in between will be drawn in the mid scope.


---

# 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/hml-balance.md?ask=<question>&goal=<user_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.
