> 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/account-and-settings/preferences.md).

# Preferences

Customize and manage ACE Studio's settings.

For Windows users, you can find preferences under \[File] from the main menu.

For Mac users, you can find preferences under \[ACE Studio] from main menu.

You can also click the <i class="fa-gear">:gear:</i> gear icon in the lower right corner to open preferences.

## General

### Language

* **Interface**: Sets the display language for the entire user interface, including menus, buttons, and tooltips. By default, the application attempts to match your operating system's language.
* **Default singing language**: Determines the default language assigned to any new vocal track you create. The "In Singer's Native Language" option will automatically set the track's language to match the native language of the singer you select.

### Auto Scroll

These settings configure the automatic scrolling behavior of the timeline during playback, ensuring the playhead remains visible.

* **Animation**: Customizes the style and speed of the auto-scroll animation when the view advances.
* **Scroll Trigger**: Defines the point at which auto-scroll is activated.
* **Scroll Dismiss**: Prevents auto-scrolling when you are zoomed in for detailed editing. For example, "<2.5s Scale" disables auto-scroll if the currently visible timeline represents less than 2.5 seconds, avoiding unwanted screen jumps.

### Debug

* **Debug Logs**: Manages the storage of application log files, which can help developers diagnose issues. You can set how long logs are kept.

### MIDI Import

* **Octave Offset**: Allows you to transpose all notes in an imported MIDI file up or down by one or more octaves.

### External Agent Access

Connect AI agents and assistants to ACE Studio through MCP or the command line. For setup guides, see [External Agent Access](/ai-agent/external-agent-access.md).

* **MCP Server (stdio)**: Click **Copy command** to copy the launch command for ACE Studio's MCP server, then add it to your MCP client's configuration.
* **acestudio-cli binary path**: Click **Copy** to copy the path of the command-line tool, for agents and power users who script or automate ACE Studio.

## Audio

{% hint style="warning" %}
For Windows users:

Due to the exclusivity of ASIO, it can only support one program at a time. If you want to use an ASIO device, please make sure there is no other program using ASIO at the same time. For more information, please refer to[ASIO Problem?](/trouble-shooting/audio-issues/readme.md)
{% endhint %}

### Device

This section controls which hardware and drivers the application uses for audio.

* **Device Type**: Selects the audio driver model for communication with your hardware.

> On **macOS**, this will typically be **CoreAudio**.
>
> On **Windows**, it is highly recommended to select **ASIO** if you have an audio interface with dedicated ASIO drivers, as it provides the lowest latency and best performance.

* **Input**: Choose the device you will use for recording audio.
* **Output**: Choose the device for audio playback.
* **Output Channels**: If your selected output device has multiple physical outputs, you can choose which pair to use here.
* **New device Notice**: When this box is checked, the application will notify you if it detects that an audio device has been connected or disconnected, prompting you to review your settings.

### Recording & Playback

These settings fine-tune audio performance, quality, and recording behavior.

* **Sample Rate**: Determines the digital audio quality. Higher values like 48000 Hz or 96000 Hz offer higher fidelity but result in larger file sizes. 44100 Hz is the standard for CDs, while 48000 Hz is common for video and professional audio.
* **Buffer Size**: Controls the amount of data processed at once, directly impacting latency.
  * **Low Buffer Size** (e.g., 128, 256): Results in very low latency (delay), which is ideal for real-time recording and monitoring. However, it requires more CPU power and may cause clicks or pops on less powerful systems.
  * **High Buffer Size** (e.g., 512, 1024): Increases latency but makes playback more stable and less demanding on the CPU. This is ideal for mixing and playback when you are not recording.
* **Latency Compensation**: Manually corrects any timing discrepancies between your live input and the project's playback. If you find your recordings are slightly out of sync with the beat, adjust this value in milliseconds (ms) until the recorded audio is perfectly aligned.
* **Pre-count**: Sets a metronome count-in before [recording](/project/arrangement-in-canvas/record.md) begins. Selecting "1 Bar," for example, will play one bar of metronome clicks, giving you time to prepare before the recording starts on the downbeat.

## Rendering

The **Rendering** tab allows you to configure how the application generates the synthesized vocal audio. The application supports two primary rendering modes: the default **Cloud Rendering** and the performance-enhancing **Turbo Mode**.

These settings currently apply to [V2 models](/ai-vocal-synth/voice-library/vocal-synth-models.md#model-generations) only.

* **Test Turbo Mode:** Click this button to start a 1-minute performance benchmark.
* **Turbo Mode**: Once unlocked by a successful performance test, you can use this checkbox to enable or disable Turbo Mode.
* **Pre-rendering:** When checked, the application will proactively start rendering vocals in the background immediately after you finish editing a note or parameter. This means the audio is often ready to play before you even press the spacebar, resulting in a more responsive and seamless editing experience.

For more information about rendering, please refer to [Local Rendering](/ai-rendering/local-rendering.md).

## Video

The **Video** tab controls how ACE Studio previews the video on the [Video Track](/project/arrangement-in-canvas/video-track.md).

### Video Preview Proxy

* **Proxy Preview**: When checked, ACE Studio transcodes videos above the proxy resolution in the background and previews the lightweight proxy instead of the original. Export always uses the original file.
* **Proxy Resolution**: The resolution of the proxy. 720p is recommended.
* **Proxy Keyframes**: How often a keyframe is stored in the proxy. **Every second** (recommended) halves the disk usage; **Every frame** gives the smoothest scrubbing.

### Proxy Cache

* **Proxy Location**: The folder where proxy files are stored. Click **Change…** to pick another folder, or **Show in Finder** (macOS) / **Show in Explorer** (Windows) to open the current one.
* **Disk Usage**: The current size of the proxy cache. Click **Clear Cache** to delete all proxy files. They are regenerated the next time they are needed.

## Plugins

Use this tab to manage ACE Bridge and third-party plug-ins.

### ACE Bridge

Install or uninstall [ACE Bridge 2](/daw-integration/ace-bridge-2.md) here. If the plug-in stops working, reinstall it here. ACE Studio also notifies you when an update is available.

> This setting applies only to **macOS**. On **Windows**, ACE Bridge 2 is installed with ACE Studio and can be restored by reinstalling ACE Studio.

### Rescan plug-ins

ACE Studio scans the standard system plug-in folders — VST3 and AU, both effects and instruments:

| Format             | Location                                                                       |
| ------------------ | ------------------------------------------------------------------------------ |
| **VST3 (Windows)** | `%LOCALAPPDATA%\Programs\Common\VST3` and `%ProgramFiles%\Common Files\VST3`   |
| **VST3 (macOS)**   | `~/Library/Audio/Plug-Ins/VST3` and `/Library/Audio/Plug-Ins/VST3`             |
| **AU (macOS)**     | `~/Library/Audio/Plug-Ins/Components` and `/Library/Audio/Plug-Ins/Components` |

Effect plug-ins appear in the FX Library (see [Third-Party Effects](/project/mixing/effects/third-party-effects.md)); instrument plug-ins appear in the **Plugins** tab of the [Instrument Library](/instruments/instrument-library.md).

ACE Studio fully scans your plug-in folders on its first launch, and on later launches only picks up plug-in files that have changed. If a newly installed or updated plug-in does not show up, refresh the list here:

* **Rescan**: Scans for newly installed or updated plug-ins and adds them to the effect browser and the Instrument Library.
* To rebuild the list from scratch, hold <kbd>Alt</kbd> / <kbd>Option</kbd> while clicking **Rescan** to force a full re-scan of all plug-ins. This is slower but resolves a plug-in list that has gotten out of sync.

{% hint style="info" %}
If a plug-in hangs or fails during the scan, you can **Disable** it — it won't be scanned again — or **Skip** it and continue.
{% endhint %}

## Update

You can update to the latest version of ACE Studio manually here.


---

# 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/account-and-settings/preferences.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.
