> 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/project/arrangement-in-canvas/record.md).
# Record
Record audio and MIDI directly onto tracks in ACE Studio.
{% hint style="info" %}
Before recording, please set up the input hardware, sample rate, buffer size.
For more information, please refer to [Preferences](/account-and-settings/preferences.md).
{% endhint %}
To start recording, click the **Record** button on the transport or press the shortcut key R.
## Arm Record
In ACE Studio, you don't need to manually arm a track for recording. The track will automatically arm for recording when you select it or place the marker line on it.
## Record from An Empty Track
When selecting an empty track and starting recording, a dialog will appear asking you to choose whether to record Audio or MIDI.
## Record Audio
### Select a Target Track
The selected (focused) track is automatically armed for recording. A red dot will appear next to the channel name in the [mixer](/project/mixing/mixer.md) or on the track header to indicate it's ready.
### Set Input and Monitoring
Choose the correct input channel in [mixer](/project/mixing/mixer.md). By default, monitoring is turned off for audio tracks to prevent feedback. You can manually enable the **Monitor Switch** (headphone icon) in [mixer](/project/mixing/mixer.md) if you need to hear the live input signal.
### Start and Stop Recording
Place the playhead where you want to start and press the **Record** button R in the transport. Press R again or press the Space to stop both recording and playback.
## Record MIDI
### Select a Vocal or Instrument Track
Select a Vocal Track, AI Instrument Track, or Instrument Track. The selected track is automatically armed for recording, indicated by a red dot.
{% hint style="info" %}
Note: If you select multiple tracks, only the first selected track will be armed for recording.
{% endhint %}
### Set Input and Monitoring
Choose the correct MIDI input in [mixer](/project/mixing/mixer.md). For MIDI tracks, monitoring is enabled by default, allowing you to hear the sound as you play on your MIDI device. A headphone icon will be displayed to indicate that monitoring is active. You can turn off the Monitor Switch (headphone icon) in the [mixer](/project/mixing/mixer.md).
### Using the Virtual MIDI Keyboard
If you don't have a MIDI controller, you can use your computer keyboard as a virtual MIDI input device. Activate it from the menu Edit > Virtual MIDI Keyboard(Shortcut key /).
* Keys A to L correspond to white keys. Keys WETYU correspond to black keys.
* Press Z / X to switch octaves down / up.
* Press C / V to decrease / increase velocity.
* When the virtual keyboard is active, some application shortcuts will be temporarily disabled.
### Start and Stop Recording
Place the playhead where you want to start and press the **Record** button R in the transport. Press R again or press the Space to stop both recording and playback.
---
# 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/project/arrangement-in-canvas/record.md?ask=&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.
