RX workflows: DAW and NLE round-trips, batch and delivery

Choose the RX route before you repair the clip: an adjustable plug-in in the session, an offline round-trip, or a separate audio file to import back into the edit. Preserve a recoverable source first. A cleaner recording is no help if the replacement has lost sync or overwritten the only original.

Choose a route for your host

• RX Connect: use it where the host supports the documented round-trip. In Pro Tools, the sequence is Send for Repair, edit in RX, Send Back, then Render in the host. Reference mode cannot send repairs back. Follow the Pro Tools Connect workflow for clip boundaries and output choices; iZotope’s current Connect manual also covers Audition and Cubase/Nuendo.
• Real-time plug-ins: use an available RX plug-in when processing needs to remain adjustable in the host. Check the particular module, format, edition and host version. A supported host does not make every Editor module a real-time insert; the RX plug-in format guide explains those distinctions.
• External editor or exported copy: follow the host-specific Logic, Premiere or Resolve guide. Some external-editor routes save directly into a file the session already uses. For manual export/import, give the repaired copy a new name, preserve the required duration, channel layout and sample rate, and check its placement after import. Matching the filename alone does not preserve sync.
• Spectral Editor ARA: selected hosts can load audio into RX’s spectral plug-in without a Connect transfer. Activation and limitations differ by host; use the ARA host guide before assuming it behaves like an ordinary insert.

RX 12 Standard and Advanced include the standalone Editor, Connect and Batch Processor; Elements does not. Check iZotope’s edition comparison before building a workflow around a missing tool.

Batch similar recordings, then check the outputs

The RX Batch Processor combines input files, a module chain and output settings. Group comparable recordings and test a small batch containing both clean and damaged passages. Do not assume that a chain tuned for one microphone or room will suit unrelated sessions. Choose a separate output folder and explicit filenames, then reopen the results and listen. The batch processing guide covers pilot runs, naming and recovery.

Check the delivered file

Confirm duration, channels, sync, audible transitions and the destination’s actual loudness and format requirements. Use the podcast cleanup or audiobook delivery guide for that job. Keep the source and an RX Document if you need editable history; export a normal audio file for the receiving application, as the RX file manual explains.

If a finished soundtrack needs a balance change, Scene Rebalance in RX 12 Advanced can separate and adjust voice, music and effects. Audition for separation artifacts before delivery; it is not a required final stage for every recording.

Frequently asked questions

Should I keep the original filename when exporting from RX?

For a manual export/import workflow, use a new filename and preserve a recoverable original. Check duration, channel layout, sample rate and placement after import. Reserve overwriting for a deliberate, backed-up external-editor workflow that you understand.

Is RX Connect the same as a real-time RX plug-in?

No. Connect transfers audio to the standalone Editor for offline repair and returns it through a supported host workflow. Real-time RX plug-ins process audio inside the host; availability depends on the module, edition and format.

Can I use one batch chain on every recording?

Do not assume so. Group similar sources, test clean and damaged passages in a small batch, and listen to the outputs before extending the run. Keep separate output files and the original recordings.