> For the complete documentation index, see [llms.txt](https://karedi.gitbook.io/karedi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://karedi.gitbook.io/karedi/user-interface/middle-components/main-editor/beats-and-pitches-grid.md).
# Beats & pitches grid
Let's take a look at the main editor without any notes:
It's a two dimentional grid. There are two X axes (time) and one Y axis (pitch).
## Grid axes
1. The Y axis corresponds to pitches (pitch is represented by a number from -60 to 67)
2. The lower X axis represents time in beats (beat is the smallest unit of time in Ultrastar format, see [bpm ](/karedi/next-level/txt-file-format/tags/bpm.md)article to learn more about beats)
3. The upper X axis represents time in ms. This axis is purely informational for you as humans understand time in milliseconds better than beats.
## Grid lines style
The lines creating the grid are dashed. The vertical lines corresponding to every 4th beat are solid. The thick vertical line that you can see in beat 3 is the [time marker](/karedi/user-interface/middle-components/main-editor/time-marker.md).
## Visible range
The range of values visible on any of the axes depends on several factors - mostly the current display mode and the notes. You can read about that in [visible area](/karedi/user-interface/middle-components/main-editor/visible-area.md) section.
## Blue grid
The light blue color of the grid's background marks the time range of the [medley](/karedi/creating-songs-for-beginners/finishing-touches/medley.md).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://karedi.gitbook.io/karedi/user-interface/middle-components/main-editor/beats-and-pitches-grid.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.