> For the complete documentation index, see [llms.txt](https://bennykok.gitbook.io/rhythm-game-starter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bennykok.gitbook.io/rhythm-game-starter/hierarchy-overview/track-manager.md).

# Track Manager

### Overview

![](https://32629026-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76iL7-CNlRUwW2lAqS%2F-M7CrWRzTQgOdZm36wiJ%2F-M7CuNMjyV6bafet5YGK%2Fimage.png?alt=media\&token=20ac6359-7e69-4f0c-92e7-43cdffc56334)

#### 1. Midi Track Mapping: Map the note in midi to the track in-game

{% content-ref url="/pages/-MHxTVoOuzUtoeIKifzB" %}
[Track Mapping](/rhythm-game-starter/note-sequences/midi-import/track-mapping.md)
{% endcontent-ref %}

#### 2. Note Prefab Mapping: Map the note to different types of note object

{% content-ref url="/pages/-M78XMycr5B7V616geeR" %}
[Note Type Mapping](/rhythm-game-starter/note-sequences/midi-import/midi-prefab-mapping.md)
{% endcontent-ref %}

### Beat Size

The distance between each note placed on the tracks, which can be perceived as the falling speed of the notes. Which higher the 

### Sync Mode

|                       | Track                                               | Individual note                                                                      |
| --------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Method                | Moving whole track parent's position.               | Moving Individual notes' position with account for the track's rotation and position |
| Movement              | Precalculated note's position with note's time data | Use lerp to move between startpoint and endpoint, which calculated each update time  |
| Realtime Speed Change | :x: Can't change beatSize(speed) in runtime         | :white\_check\_mark: Can change beatSize(speed) in runtime                           |


---

# 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://bennykok.gitbook.io/rhythm-game-starter/hierarchy-overview/track-manager.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.