On this page
To use iZotope RX Connect in Pro Tools, duplicate the working playlist, select the problem clip or range, and open RX 12 Connect from the AudioSuite menu. For a routine clip repair, start with Playlist, Use In Playlist enabled, Create individual files and Clip-by-clip. Choose Repair, then Send. Apply the repair in RX Audio Editor, click Send Back, and click Render in the still-open RX Connect window. Send Back transfers the result; AudioSuite Render applies it according to the selected file and playlist modes.
That sequence is simple, but the result still depends on what you selected and how AudioSuite is configured. A clean repair with the wrong input, channel or output mode can lose fades, split stereo audio into mono files, replace more clips than intended or appear to do nothing. Check the selection and AudioSuite modes before sending valuable audio.
What RX Connect does in a Pro Tools session
RX Connect is a bridge between Pro Tools and the standalone RX 12 Audio Editor. It is not an ordinary real-time insert. The current RX 12 Connect manual says it can send one or multiple clips to the Editor, where you get the offline tools and spectral display, then return repaired audio to the host.
Use it when a repair needs the full Editor: a spectral selection, several modules in sequence, detailed before/after inspection or an RX document you may revisit. If one suitable AudioSuite module already solves the problem, processing directly in Pro Tools can be faster. The RX Editor, plug-ins and Connect comparison helps choose that route before starting a transfer.
RX Connect is available in RX 12 Standard and Advanced, not Elements. iZotope's RX 12.0.0 release notes, dated April 28, 2026, list support for 64-bit AAX AudioSuite and name Pro Tools 2025 as a supported host. Avid now publishes a 2026.4 reference guide, but that document is not iZotope certification of every newer host combination. Check the exact RX build, Pro Tools build, operating system and processor architecture before changing a working system.
Repair mode and Reference mode are not interchangeable
| RX Connect mode | What happens | Can it return audio? | Use it for |
|---|---|---|---|
| Send For Repair | Sends the selection and opens it in RX Audio Editor | Yes, through Send Back then AudioSuite Render | Actual clip restoration |
| Send For Reference | Sends audio one way for analysis | No | Learning a profile or inspecting material without a return |
If RX does not open automatically and no return button appears, check the mode before reinstalling anything. The manual states that Reference is analysis-only and does not automatically launch RX Audio Editor; the referenced file appears when you open the Editor yourself. For a complete Pro Tools loop, choose Repair before Send.
Prepare a reversible edit before sending audio
Duplicate the playlist before a repair pass and save the session. With nondestructive AudioSuite file modes, Undo can reverse the processed edit; it cannot restore source audio overwritten in destructive mode. A duplicate playlist is an edit safety copy, not a separate backup of the underlying audio files. Preserve source media separately before any destructive operation.
Work on one representative problem first. For dialogue, select the mouth click, rustle or noise event plus enough clean speech and room tone to judge the transition. For a clipped transient or musical noise, include the attack and decay. Avoid selecting an hour simply because RX Connect accepts multiple clips; short, deliberate transfers are easier to audit and recover.
Keep the same RX Connect AudioSuite instance open through the round trip, and leave the target selection and playlist unchanged while repairing. This avoids losing track of which return belongs to which edit. Before closing a transferred RX tab or restarting either application, preserve valuable RX work in an .rxdoc; use a separate WAV or AIFF export if you also need a playable recovery file. An archived file is not a promise that reopening it restores the original Connect return connection.
Selection and handles decide whether the repair blends
The visible problem is rarely the whole edit boundary. A denoised word still needs room tone on both sides; a repaired click may sit inside a crossfade; a de-rustled phrase may need consonants before and after the selected noise. Give RX enough context to process naturally and give Pro Tools enough media to rebuild fades.
Avid's Pro Tools 2026.4 Reference Guide describes AudioSuite handles as additional available source audio beyond the visible edit selection. The Handle Length field accepts 0.00–60.00 seconds; Whole File can make the referenced source available for trimming when the chosen modes support it. This does not manufacture audio beyond the original recording. The amount needed depends on the fade, ambience and repair boundary.
Extra timeline context and AudioSuite handles are different. Selecting a longer range changes what you send as the visible edit; setting handles can retain media outside that edit. For separate repair clips with editable fades, start with Create individual files plus Clip-by-clip and an appropriate handle length. Do not select Whole File on a long recording without checking the transfer size. After Render, briefly extend an edge on the working playlist to verify the expected media, then restore the intended boundary.
Choose Clip-by-clip or Entire selection deliberately
Clip-by-clip analyses clips separately. Combined with Create individual files, it is the documented starting point for keeping separate clips, editable fades and available handles. Entire selection analyses the range together. It can be useful for continuous ambience work, but it does not by itself determine whether the return becomes one file: that also depends on File Mode.
Consider a line assembled from several takes. Separate clip processing keeps the local edits easier to revise, but may open several RX tabs. Treating the whole range together can make a broad repair easier; choosing Create continuous file deliberately consolidates it. Choose both modes before Send and keep them consistent through the return. Do not assume switching modes halfway through will recover missing fades or handles.
Review the channel input mode as well. The RX 12 manual says Mono mode treats stereo and multichannel material as discrete mono clips. A stereo clip therefore becomes two separate mono files. Multi-input mode keeps dual-mono and stereo audio together. Choose the mode for the clip you intend to repair, then confirm channel order and phase after the return.
Mono mode can also multiply file count quickly. iZotope warns that a large group can exceed RX Connect's 32-file maximum. If a batch mysteriously stops, reduce the selection and check whether a stereo or multichannel transfer was exploded into many mono files.
Pick a safe AudioSuite output mode
| File mode | What it creates | Check before use |
|---|---|---|
| Create individual files | New processed files; source media stays intact | Pair with Clip-by-clip for editable fades and handles |
| Create continuous file | New consolidated clip | Expect rendered fades and gain; inspect boundaries |
| Overwrite files | Destructive source-media replacement | Undo and a duplicate playlist cannot restore overwritten audio |
For routine restoration, use Create individual files plus Clip-by-clip. The RX manual summarizes individual-file processing as preserving clips and fades/handles; Avid's more detailed AudioSuite conditions table on pages 1247–1248 supplies the combinations. With Individual Files plus Entire Selection, it lists no handles or Whole File option, and fades and clip gain are rendered into the result. With Continuous File, the table lists handles only at the beginning and end of the new continuous file; fades and clip gain are rendered, metadata is not preserved, and Whole File is unavailable.
The same Avid section cautions that plugins dependent on an analysis selection may not work as expected with handles. Its general description of Entire Selection is broader than the continuous-file rows in the table, so check the actual controls and returned media on a short test. If handles are disabled even in the intended combination, do not change to a destructive mode to force them.
For a change limited to the selected track clips, set Selection Reference to Playlist and enable Use In Playlist. With Use In Playlist off, the new result goes to the Clip List and does not replace timeline clips. With Clip List reference and Use In Playlist enabled, all copies of the selected clip can be replaced throughout the session, including other playlists. That combination defeats the purpose of a safety playlist. These targeting rules are separate from File Mode: leave Overwrite Files off.
Nine steps for a clean RX Connect round trip
- Duplicate the playlist. Save the session and duplicate the working playlist. Keep source media intact by using a nondestructive file mode.
- Select the intended audio. Select the problem and enough context for judging transitions. The handle controls are configured after opening Connect.
- Open RX 12 Connect. Choose RX 12 Connect from AudioSuite, under Noise Reduction or the manufacturer grouping used by your installation.
- Set the target and modes. For a routine separate-clip repair, choose Playlist, enable Use In Playlist, and select Create individual files plus Clip-by-clip. Choose the channel mode deliberately and verify available handles.
- Choose Repair and Send. Use Repair for a return trip, then click Send. Keep the same Connect instance, selection and playlist in place while RX opens the transferred audio.
- Apply and audition the repair. Turn Instant Process off before drawing selections unless immediate processing is intended. Apply the repair in RX and compare the result across both edges. Preserve duration, sample rate and channel layout for this workflow.
- Send Back from RX. Click Send Back from the transferred audio in RX. Preserve valuable work separately before closing a transferred tab.
- Render in Pro Tools. Return to the same Connect instance, confirm the intended target and modes, then click Render to apply the returned audio.
- Verify the returned edit. Compare against the safety playlist. Check sync, handles, fades, clip gain, channels and both transitions; confirm the safety playlist remains unchanged.
In RX, turn Instant Process off before drawing a selection unless immediate processing is intentional. Apply the chosen repair to the transferred audio before Send Back; auditioning a module alone is not the same as applying it. Keep the clip duration, sample rate and channel layout unchanged for this repair workflow. If deliberate timing or format changes are needed, handle them as a separate edit with a sync check. The RX spectrogram guide helps locate a defect; the De-click workflow covers click processing.
Monitor RX through Pro Tools when the audio driver is busy
On applicable HDX setups, Pro Tools can control the audio hardware so RX Editor cannot play through the same driver. That is a monitoring conflict, not proof that the sent audio is missing. The current RX Monitor manual provides the supported bridge.
Insert RX Monitor on an Aux or Instrument track in Pro Tools. In RX Audio Editor, open Preferences, choose the Audio tab, and set Driver Type to RX Monitor. Return to Pro Tools and confirm the RX Monitor plug-in reports Connected. Playback from RX should then arrive through that host track and the Pro Tools output path.
Route the monitor track to the intended listening output and check its mute, solo and level state if RX plays silently. Keep that track out of prints and stems unless deliberately included. If the plug-in remains Disconnected, check the RX driver selection first; the manual also notes that firewall or antivirus permission may be required. Allow the specific component where needed rather than disabling protection globally. Changing the session sample rate is not a general repair for a monitoring problem.
Send Back is not the same as Render
There are two places where processing must actually be applied. Inside RX, complete the selected repair rather than only auditioning it. Then Send Back transfers that edited audio to Connect. Render in Pro Tools applies the returned data using the AudioSuite output and playlist settings. A successful RX audition, Send Back and AudioSuite Render are distinct steps.
If RX reports a return but the timeline sounds original, confirm that the same Connect instance is ready to render and still targets the intended selection. If that selection changed, stop and restore the known target before committing; do not render into an unrelated clip. Check Use In Playlist as well: with it off, the new audio can be in the Clip List while the original stays on the track.
After Render, compare the repaired playlist against the safety copy at matched gain. Listen one edit before and one edit after the target. A successful button sequence is not the acceptance test; transparent boundaries, correct sync and preserved channel behavior are.
Why RX Connect will not send or return audio
Repair was not selected. Reference is one-way. Choose Repair and start a new Send.
The AudioSuite target is wrong. Verify the selected track clips, Playlist reference and Use In Playlist before a new transfer. A result in the Clip List can mean the transfer worked without replacing the timeline. Do not enable Clip List plus Use In Playlist casually; that can change other occurrences too.
The return was never rendered. Keep RX Connect open, click Send Back in RX, then click Render in Pro Tools. Repeating the RX repair does not substitute for this commit.
The transfer is too large. Reduce the selection, especially when Mono mode has split stereo or multichannel content into many files. The documented maximum is 32 files, not 32 timeline clips in every channel configuration.
Handles are greyed out. First check the file/process combination and available source audio. If the intended settings still fail, test one short clip in a blank session and record the exact builds. A Windows 11 / Pro Tools 2026.4.0 report describes disabled handles, but does not identify an RX build or prove every RX 12 installation is affected. Treat it as a reason to test your combination, not as a universal diagnosis or an instruction to downgrade.
A shortcut fails but the buttons work. Test Send Back and Render manually before changing the audio installation. A May 2026 SoundFlow discussion reports an RX 12 recognition problem in an automated command. That concerns the macro layer; it does not by itself establish a failed manual Connect transfer. Update or troubleshoot the automation separately, without copying an unverified script into the production session.
The bridge is stuck or says Waiting for Connect. That message alone does not identify the cause. Check the original host instance and complete the documented Send Back → Render sequence. If restarting the transfer is necessary, save the session and preserve the RX edit as an .rxdoc or separate audio file before closing its tab. Reopen Connect and resend a short source selection. If that also fails, consult current support guidance for the recorded versions. The RX crash and launch guide covers application failures; the missing RX plug-ins guide covers discovery. If Connect is absent, first look in AudioSuite and check that its AAX component is installed.
How to verify a returned repair before moving on
- The repaired clip begins at the same sample or timecode position as the source.
- The intended playlist changed and the safety playlist did not.
- Original fades or rebuilt fades play without clicks or ambience dips.
- Handles extend far enough for the next edit revision.
- Mono, stereo or multichannel layout matches the source intent.
- Stereo width and polarity have not changed unexpectedly.
- No loudness jump is masquerading as a better repair.
- The problem is reduced without damaged consonants, attacks or room tone.
- Recheck clip mute and lock state: Avid documents that AudioSuite processing unmutes muted clips and unlocks locked clips.
Name the new playlist or processed clip so another editor can identify the pass. For extensive work, save the RX document and note the module chain or decisive settings. This is more useful than relying on memory after dozens of dialogue fixes.
When direct AudioSuite processing is the better route
RX Connect adds value when the standalone spectrogram and cross-module editing matter. It adds unnecessary steps when a single RX module already solves a clearly selected problem inside Pro Tools. A quick De-click or Voice De-noise AudioSuite pass may be easier to preview, render and revise directly.
Use Connect for surgical spectral work, compound repairs and cases that benefit from RX history or an .rxdoc. Use direct AudioSuite for repeatable one-module jobs. Use a real-time insert when the process must remain adjustable during playback and its latency and automation behavior fit the session.
Use the RX Workflows guides for other DAW transfers and ways to keep repairs revisable. In Pro Tools, start with the right selection and nondestructive modes, apply the repair in RX, Send Back, then Render and listen across the boundary.
Frequently asked questions
Where is RX Connect in Pro Tools?
Open it from the AudioSuite menu. The current RX 12 manual places RX Connect under Noise Reduction, while some installations may group vendor plug-ins under iZotope. It is an AudioSuite process, not a normal track insert for this round trip.
Should I choose Repair or Reference?
Choose Repair when the edited audio must return to Pro Tools. Reference is a one-way analysis mode and cannot send repaired audio back to the host.
Why did Send Back not change my Pro Tools clip?
Send Back only transfers the repaired result. Return to the open RX Connect AudioSuite window and click Render. Also check Use In Playlist; if it is off, the processed file may be in the Clips List without replacing the timeline clip.
Which AudioSuite output mode is safest?
For separate repaired clips with editable fades and handles, start with Create individual files plus Clip-by-clip. File Mode alone does not guarantee those properties: Individual Files plus Entire Selection has different fade and handle behavior. Avoid Overwrite Files; a duplicate playlist does not protect overwritten source media.
Should I use Clip-by-clip or Entire selection?
Use Clip-by-clip with Create individual files when separate clip edits, fades and available handles should remain revisable. Entire selection analyses the range together; its return structure and handles still depend on File Mode. Test the chosen pair before processing a large selection.
Why did a stereo clip arrive as two mono files?
RX Connect was likely in Mono input mode, which treats stereo and multichannel sources as discrete mono clips. Choose Multi-input when the stereo pair should remain one entity, then resend a short test.
How do I hear RX Editor with a Pro Tools HDX system?
Insert RX Monitor on an Aux or Instrument track, then set RX Audio Editor's Driver Type to RX Monitor. Confirm the plug-in reports Connected before playing from RX.
What should I test when RX Connect suddenly stops working?
Try one short clip in a blank session and record the exact RX, Pro Tools, operating-system and processor details. Verify Repair, Playlist targeting, file/process modes and the final Render step. Test manual buttons if a macro fails. Preserve unsaved RX work before restarting a transfer; do not begin with cache deletion or a downgrade.
