2.5. Known limitations
The DAW-specific advice below reflects the versions tested. Other DAWs and versions may behave differently.
- Time-stretching or pitch-shifting a clip in the host is not supported.
- REAPER shares ARA edits between copies of the same source by default. A setting you change on one copy applies to all of them. To optimize a copy separately, select it and run Item: Remove active takes from ARA edit pool (unpool).
- Audio, analysis data, and frozen renders are held in memory. Long sources or processing at several levels can use several GB of RAM.
- Some DAWs play files at the wrong speed when you import them at a different sample rate without conversion. A started ARA level plays the file at its original speed, which can leave silence at the end of the clip. Convert files to the project’s sample rate when importing them.
- If a frozen level’s audio can’t be read when the project opens, for example because a media file is missing, the level is no longer frozen and the project saves it that way. Its settings are kept: once the audio is available again, press Start analysis, Optimize, and Freeze again.
- REAPER leaves clips whose media file is missing out of ARA processing. Saving the project while a file is missing can discard the ARA settings of its clips, so locate the file first, or close the project without saving.
- ARA processes the clips on a track, not audio routed into it. If your DAW uses ARA on a track without clips, such as a bus that receives other tracks, the plug-in has nothing to optimize and outputs silence. To process a mix, render it to a new clip first.
See Saving and exporting for loading and export precautions, including saving after ARA changes.