> 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/next-level/txt-file-format/tags/medleyendbeat.md).

# MEDLEYENDBEAT

## What is it?

Medleyendbeat defines the moment (in beats) in which the singable part of the medley should end.

## What is it used for?

It is used to indicate the first beat that should not be included in medley.

## How to determine the value?

First determine the part of the song that you want to include in medleys (has to be continuous). It can be the chorus or something more custom - e.g. several lines of the verse and several lines of the chorus - any fun and recognizable part of the song will do as long as it is not too long.

The *medleyendbeat* should be the beat after the end of the last note from this part.\
So if the last note starts in beat 4000 and lasts 5 beats, you should use 4005.

## Technical requirements

Valid MEDLEYSTARTBEAT:

* must be >= 0,
* is expressed in beats so it is an integer,
* is after #MEDLEYSTARTBEAT,
* is before the song's last beat.

## Example in TXT file

```
#MEDLEYENDBEAT:4005
```

## See also

{% content-ref url="/pages/VnYD1QDJiupSkCpshGGn" %}
[MEDLEYSTARTBEAT](/karedi/next-level/txt-file-format/tags/medleystartbeat.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZCM4ytfayzHklRZWTXqT" %}
[Setting medley boundaries](/karedi/next-level/editing-tags/setting-medley-boundaries.md)
{% endcontent-ref %}


---

# 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/next-level/txt-file-format/tags/medleyendbeat.md?ask=<question>&goal=<endgoal>
```

`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.