> For the complete documentation index, see [llms.txt](https://docs.acestudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acestudio.ai/docs/product-wiki-ko/instruments.md).

# 악기

- [악기 라이브러리](https://docs.acestudio.ai/docs/product-wiki-ko/instruments/instrument-library.md): ACE Studio의 악기 라이브러리에서 AI 악기, 유니슨 프리셋 및 타사 악기 플러그인을 탐색하세요.
- [타사 악기](https://docs.acestudio.ai/docs/product-wiki-ko/instruments/third-party-instruments.md): ACE Studio의 악기 트랙에서 타사 VST3 및 AU 악기 플러그인을 로드합니다.
- [악기 사운드 만들기](https://docs.acestudio.ai/docs/product-wiki-ko/instruments/create-instrument-sounds.md): ACE Studio에서 AI 악기를 사용하는 방법을 알아보세요.
- [노트 편집](https://docs.acestudio.ai/docs/product-wiki-ko/instruments/create-instrument-sounds/editing-notes.md): ACE Studio에서 AI 악기의 MIDI 노트를 편집하세요.
- [아티큘레이션](https://docs.acestudio.ai/docs/product-wiki-ko/instruments/create-instrument-sounds/articulations.md): ACE Studio AI 악기의 아티큘레이션을 살펴보세요.
- [표현 컨트롤](https://docs.acestudio.ai/docs/product-wiki-ko/instruments/create-instrument-sounds/expression-controls.md): ACE Studio AI 악기의 표현 컨트롤을 살펴보세요.
- [악기용 유니슨 모드](https://docs.acestudio.ai/docs/product-wiki-ko/instruments/create-instrument-sounds/unison-mode-for-instruments.md): ACE Studio에서 여러 AI 악기를 하나의 유니슨 트랙으로 결합하세요.


---

# 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.acestudio.ai/docs/product-wiki-ko/instruments.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.