> For the complete documentation index, see [llms.txt](https://docs.avis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avis.net/vi/avis-creative-studio/feature-guide/object-tracker-vfx-node.md).

# Object Tracker (VFX Node)

Object Tracker bám theo một đối tượng qua các khung hình video và tạo đầu ra dạng Highlight, Transparent hoặc Mask. Chuỗi mask/cutout này hỗ trợ khâu chuẩn bị cảnh quay và các bước VFX tiếp theo.

Để thêm node, nhấn **+** (hoặc nhấp chuột phải vào Canvas), chọn **VFX**, rồi chọn **Object tracker**.

**Cách sử dụng:**

1. Chọn video đầu vào.
2. Chọn khung hình bắt đầu rồi vẽ khung bao quanh đối tượng cần theo dõi. Khung nên ôm sát toàn bộ chủ thể.
3. Chọn **Result** (Highlight, Transparent hoặc Mask), **Result type** (Fast hoặc Better) và **Quality** (Original, 6 FPS, 12 FPS hoặc 24 FPS).
4. Nhấn **Track subject** để chạy theo dõi.
5. Dùng video đầu ra cho bước chỉnh sửa hoặc VFX kế tiếp.

<figure><img src="https://1381001042-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBqtOszkBUadA4v68IeIc%2Fuploads%2Fgit-blob-218681d5be61048e02bbb999cd4a73f32d945c6c%2Fimage%20(82).png?alt=media" alt="" width="563"><figcaption><p>Object Tracker</p></figcaption></figure>

{% file src="/files/jqYRyrPFZ2Xk57303xVR" %}


---

# 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.avis.net/vi/avis-creative-studio/feature-guide/object-tracker-vfx-node.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.