> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/editready/settings/general.md).

# General

The General Settings pane exposes a few common settings that can be used to customize how EditReady processes files. For most users, the default settings will be correct and should not be adjusted.

### Parallel Job Count

This setting controls how many files are converted in parallel. By default, EditReady automatically configures itself based on your computer's capabilities and will attempt to fully utilize your Mac's processing power.

Reducing the job count may be helpful in reducing memory consumption on machines with very limited RAM, especially when working with very high-resolution (8K / 12K) footage.

### Write ALE Files

When enabled, EditReady generates an Avid Log Exchange (ALE) file for each transcoding batch. The ALE file contains metadata about all media files included in the batch.

### Audio Bit Depth

EditReady produces 24-bit audio by default. This is the industry-wide default for video editing and post-production. However, some workflows or hardware playback devices may require reduced-bit-depth audio.&#x20;

### Hardware Acceleration

All modern Macs have powerful video encoding and decoding hardware, which can speed up video conversion by multiple orders of magnitude. However, this hardware can have trouble decoding the latest video formats. Disabling hardware acceleration and using a purely software-based approach can help process those files in those cases.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hedge.video/editready/settings/general.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
