> 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/advanced.md). # 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 has specifically instructed you. This panel's default is for all options to be unchecked. ### Always write video range ProRes clips Remaps full range (data range) source content to video range when writing ProRes outputs. There's inconsistent handling of ProRes range mapping across applications, which can cause issues when between different applications, which can cause issues mixing ProRes proxies with camera originals. Premiere Pro and DaVinci Resolve tend to treat ProRes as video range exclusively, whereas Final Cut Pro X will treat files differently depending on the project settings. ### 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. ### 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. ### 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 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/advanced.md?ask=&goal= ``` `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.