RX Audio Editor vs Plugins vs RX Connect: Which Workflow?

Use an RX insert plug-in when a repair should remain adjustable during the mix. Open the standalone RX Audio Editor for precise spectral selections, several ordered repairs or stem work. Use RX Connect when a supported host needs to send selected clips to the editor and receive the repaired audio back in place.

There are two useful exceptions: AudioSuite plug-ins process audio offline, and RX Spectral Editor can make selected spectral repairs inside compatible ARA hosts. Decide from the edit, then check the integration your edition and host actually provide.

RX Editor, plug-in and Connect at a glance

A narration track with steady noise can suit an insert. A chair squeak overlapping one word calls for a local selection. Several dialogue clips needing different editor modules may justify Connect. These are workflow choices, not a ranking of sound quality.

Stay in the DAW for adjustable processing

An insert keeps processing available while you mix: bypass it in context, change settings and automate controls that support automation. Splitting clips by noise condition can be more useful than forcing one setting across the recording. An offline AudioSuite render is a different commitment; do not expect it to behave like an adjustable track insert.

Check the RX 12 edition and module matrix before choosing a route. Editor modules do not all have separate plug-in versions. The standalone Audio Editor, Connect and Monitor belong to Standard and Advanced; Elements does not include that editor workflow.

Some algorithms introduce processing delay. The RX plug-in latency documentation describes delay reporting and host compensation. Compensation can align playback, but it does not make a delayed processor suitable for every live monitoring situation. Audition the chosen mode in your actual session.

If an expected processor is absent, start with the missing RX plug-in checklist. Establish that the processor exists in your edition and format before rebuilding a plug-in cache.

Open the Audio Editor for surgical or ordered repairs

The editor gives you waveform and spectrogram selections, Preview, Compare and Undo History alongside the modules in your edition. Choose it when the location of a repair matters as much as its settings, or when several operations need a deliberate order. Module Chain, batch processing and stem workflows also make the separate application useful beyond individual spot fixes.

Preview lets you hear a proposed repair; it does not commit the result. In modules with Compare, audition candidates and select the intended result before rendering. After each rendered operation, listen again and use History if the repair damages wanted sound. The editor's Preview, Compare and Render controls explain that sequence.

Save an RX document, .rxdoc, when you need to retain the original audio and Undo History for later revision. Export a separate deliverable when the host needs an audio file. The RX file-saving guide distinguishes those operations: an ordinary Save on an opened WAV or AIFF can overwrite that file. A WAV export does not preserve the editor's history.

For sync-critical work, keep a recoverable source and preserve duration, channel layout and sample rate unless the job explicitly requires a change. Identify each incoming clip before processing. A good repair returned to the wrong clip still fails the job.

Check the ARA option before leaving the host

RX Spectral Editor offers selection-based Attenuate, Replace, Gain, De-click and De-hum processing inside supported ARA workflows. It is not the entire standalone editor or a replacement for every Connect job.

The current RX release notes list Logic's AU ARA route with the Rosetta requirement on Apple silicon, and a VST3 ARA route for Studio One/Fender Studio Pro. In Studio One, use the VST3 version as an Event FX, rather than a normal channel insert. Check the current RX host and format requirements against your installed build.

Pro Tools also has an Avid-documented RX Spectral Editor integration. Its package and compatibility should be checked through the Pro Tools documentation; do not infer that every RX plug-in installation provides the same ARA integration in every DAW. Use Connect when the repair needs editor modules outside the available ARA tool set.

Understand what RX Connect actually does

Connect transports audio; the editor performs the repair. The RX 12 Connect manual documents sending one or multiple clips through AudioSuite in Pro Tools and the appropriate effects or offline-processing path in other supported hosts.

Send for Reference is one-way analysis. It does not provide a return through that transfer and does not automatically open the editor; open RX to see the imported audio. Send for Repair establishes a round trip. After committing the repair in RX, use Send Back and then the host's Apply or Render command.

The vendor's Connect host list includes Pro Tools, Media Composer, Audition, Cubase and Nuendo. It describes external-editor routes for Live, Premiere Pro, Final Cut Pro, Logic Pro and REAPER. Treat that list as integration families, not certification of every historical host version for RX 12. Plug-in compatibility alone does not establish a working Connect return.

A safe RX Connect round trip

1. Preserve the source. Use a non-destructive host output mode or a separate audio-file copy; duplicating a playlist alone cannot protect a file that is overwritten on disk.
2. Select the intended clip or range, with the handles needed for transitions. Confirm its destination and channel layout.
3. Open Connect through the host's documented path and choose Repair when the audio must return.
4. Execute the host's send command: Send in Pro Tools, or the initial Apply in the Audition and Cubase/Nuendo workflows below.
5. In RX, preview the repair, render the intended processing and listen to the result. Preserve timing unless changing it is part of the job.
6. Choose Send Back in RX, return to the host and commit with its second Apply or Render step.
7. Listen in the session. Check the returned clip's boundaries, fades, handles, channels, sync and level against the recoverable original.

Pro Tools: Send, then Send Back, then Render

Select the timeline audio and open RX Connect from AudioSuite > Noise Reduction, or the iZotope category when menus are organized by manufacturer. Choose Repair and click Send. In the editor, perform and render the repair, then choose Send Back. Return to the original destination in Pro Tools and click Render in Connect.

Before sending, inspect AudioSuite's input and output settings. Clip by Clip processes clips individually, including their fades; Entire Selection treats the selection as one clip. Multi-input keeps stereo channels together, while Mono can send them as separate mono files. Many discrete channels can run into RX's 32-file limit.

Create Individual Files is the documented non-destructive output option for retaining individual clips, fades and handles. Create Continuous File consolidates the selection into one new file. Overwrite Files changes the original files: a duplicate playlist referencing those same files is not a backup. Choose the output behavior before trusting the return.

Audition: Apply twice, with Connect reloaded

In Waveform view, select the audio and open Effects > VST3 > Restoration > iZotope > RX 12 Connect. Use Repair for a return workflow and click Apply to send. Render the repair in RX and choose Send Back.

Return to Audition and reload Connect from the Effects menu. When the returned audio is ready, click Apply to commit it. The first Apply sends the audio; the second applies the returned result. Keep a separate original before editing the Waveform file.

Cubase and Nuendo: turn Auto Apply off first

Select the event and open Audio > Direct Offline Processing. Disable Auto Apply, add RX Connect with the plug-in control and click Apply to send for repair. Render your work in RX, choose Send Back, return to the host and click Apply again.

If Apply is missing, disable Auto Apply and start a new Connect instance as the RX manual instructs. Do not repeatedly send from several instances while trying to identify one pending return.

The RX instructions also describe making Direct Offline Processing permanent. Treat that as a separate finalization decision: Steinberg warns that making processing permanent cannot be undone. Preserve a recoverable project and source before clearing that processing history.

Route editor playback through RX Monitor when needed

RX Monitor sends the standalone editor's playback through a host track. It is particularly useful when the host has exclusive use of the audio device. It neither transfers clips nor repairs them.

Follow the RX Monitor routing instructions: insert Monitor on an Aux or Instrument track in the host. For Cubase and Nuendo, use an FX Track, as the vendor's host-specific Monitor notes specify. In RX, open Preferences > Audio, select RX Monitor as the Driver Type and confirm with OK. The host plug-in should report Connected. Start playback in RX and check that the receiving track reaches the intended output and is not muted.

External-editor workflows need an explicit safety copy

First establish which file the host sends and what saving will change. A duplicated timeline region can still reference the same source file. For a workflow that opens the source directly, make a separate file copy or bounce first and confirm the host uses that copy.

In Logic's current external-editor setup, choose Logic Pro > Settings > Audio, then File Editor > Choose to select RX. From the Audio Track Editor, use Edit > Open in the selected external editor, or Shift-W. Saving externally updates the audio used by Logic's regions, which is why the separate source copy matters.

Resolve's built-in external process behaves differently. Blackmagic's External Processing description says to add the application in preferences under Audio Plugins, then choose it from the Fairlight clip's External Audio Process menu. Resolve creates a bounced version for processing; saving it in RX returns the result on a new layer above the original. Save the supplied file in place for that return, and retain the original layer for comparison or recovery.

If a host's integration is unclear or unreliable, export a separate audio copy, repair it and export a new named result for reimport. Preserve common start and end boundaries and sample rate, place it at the original timeline position, then verify sync at the head, tail and edit points before delivery.

Failure checks before sending again

• No Send Back: check whether the transfer used Reference instead of Repair.
• Returned audio sounds unchanged: confirm processing was rendered in RX; Preview alone does not commit it.
• Host still awaits the return: check Send Back, then the host's second Apply or Render stage. Audition requires Connect to be reloaded.
• RX is silent: check its output route; with Monitor, check Connected and the receiving host track.
• Timing or channels changed: compare selection boundaries, input mode, duration and channel layout with the original.
• The wrong file changed: stop, identify the affected source and restore from the actual file backup before trying again.

For a first session, work through the RX 12 beginner tutorial on a copy before returning a client clip. The RX Workflows hub covers broader session and delivery decisions; the audio repair hub helps choose a processor for the specific defect.

Frequently asked questions

Is RX Connect the same as an RX repair plug-in?

No. Connect transports selected audio between a supported host and the standalone RX Editor. The editor modules perform the repair.

What is the difference between Send for Reference and Send for Repair?

Reference is a one-way analysis transfer and cannot return through that send. Repair creates a round trip: render the repair in RX, choose Send Back, then complete the host's Apply or Render step.

Does every DAW support RX Connect?

No. Direct Connect workflows are host-specific. Other routes include an external editor, deliberate export and reimport, or RX Spectral Editor in a compatible ARA host.

When is an RX plug-in better than the standalone editor?

An insert suits an included processor that should remain adjustable during the mix. An AudioSuite processor instead renders an offline selection. Check edition, format and host support before choosing either route.

When is the RX Audio Editor better?

Use the editor for precise spectral selections, several ordered repairs, stem or batch work, or sessions needing its History and Compare tools. The standalone editor is included in RX 12 Standard and Advanced, not Elements.

What does RX Monitor do?

RX Monitor routes the standalone editor's playback through a host track, particularly when the host controls the audio device. It does not transfer or repair clips.

Is RX Connect non-destructive?

Reversibility depends on the host's output mode and recoverable source files. A duplicate playlist cannot protect an original file that is overwritten on disk. Check file-handling settings before sending.

Why did my repaired clip not return to the DAW?

Check Repair mode and the initial Send or Apply, render processing in RX, choose Send Back, then complete the host's final Apply or Render. Audition requires Connect to be reloaded; also confirm the intended destination selection.