# Settings

<figure><img src="/files/yiTkRRJXNRdwA3SnBgQO" alt=""><figcaption></figcaption></figure>

## 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.

#### 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;

#### 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. This file can be imported directly into Avid Media Composer to recreate bin metadata and organize clips alongside the transcoded media.

#### 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;

## Advanced

The Advanced Settings pane contains some options that should only be adjusted in response to very specific issues. Generally, you shouldn't make changes here unless our support staff have specifically instructed you. This panel's default is for all options to be unchecked.

#### Prefer Legacy Color Science for Premiere Pro

When transcoding xvYCC (extended-gamut YCbCr) footage to ProRes, Adobe Premiere Pro can experience color management glitches. While these issues are reduced in newer versions of Premiere Pro, enabling this option may correct color rendering issues if you're using a version from 2023 or earlier.

#### Ignore H.264/HEVC data levels

Video files can store their brightness information within a couple of different ranges. Historically, all video files were in what was called "video range". To allow for more dynamic range, some cameras allow you to instead record brightness information in "data" or "full" range. By default, EditReady will preserve data range video levels during the transcoding process. However, this can make video content look very high contrast if the playback application isn't taking that range into account. Checking this box will change how EditReady converts those files in those cases.&#x20;

#### Disable A/V Synchronization

Cameras often write metadata to files that perform basic synchronization adjustments to account for differences between the frame and audio sample lengths. EditReady preserves these edits (called an edit list or ELST). In some cases, though, cameras incorrectly write ELST data, so it's better to ignore that metadata.&#x20;

#### Maintain Source Audio Track Count

Audio is stored in tracks and channels within media files. An audio track stores at least one audio channel but may contain many more. Cameras often record audio with multiple single-channel (mono) tracks. However, converting files to a single track with multiple channels is often better for performance reasons. That's the default behavior for EditReady. Check this box to maintain the original track structure of your source format.


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.
