> ## Content Index > Fetch the complete content index at: https://izotoperx.net/llms.txt > Use this file to discover other available public pages before exploring further. # iZotope and VirtualDJ: What Works, What Does Not, and the RX Workflow - URL: https://izotoperx.net/izotope-rx-virtualdj-workflow/ - Published: 2026-09-22T20:01:33.000Z - Updated: 2026-09-30T20:24:24.000Z - Description: RX can prepare repaired tracks and stems for VirtualDJ. Learn what can load as VST3, why RX Editor stays separate, and the reliable WAV workflow. - Author: Brandon Hayes - Tags: Workflow, Music Repair, RX 12 **iZotope RX can be useful in a VirtualDJ workflow, but the dependable route is to process the audio in RX first, export a WAV file or stems, and then load the result into VirtualDJ.** VirtualDJ has VST3 support, so an individual RX plug-in may load as an effect. That does not turn the standalone RX Audio Editor into a VirtualDJ effect, and it does not make VirtualDJ a documented RX Connect host. If the job is live stem control, start with VirtualDJ’s own tools. If the job is careful vocal reduction, stem preparation, hum removal, clipping repair or spectral cleanup, prepare the file in RX and bring the rendered result back to the DJ library. The distinction saves time because it separates a possible plug-in route from the workflow that is easiest to repeat and archive. ## What works between iZotope RX and VirtualDJ? | Route | Does it work? | Best use | | -------------------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------ | | Open the RX Audio Editor inside VirtualDJ | No | Use RX as a separate application | | Load an individual RX VST3 component | Sometimes | Simple real-time cleanup when the specific plug-in loads and behaves correctly | | Send a deck to RX through RX Connect | Not a documented VirtualDJ workflow | Use file export and re-import instead | | Prepare a repaired track in RX | Yes | Controlled offline repair before a set | | Export vocals, bass, percussion and other material | Yes, with the relevant RX tools | Pre-built edits, mashups and alternate mixes | The key product distinction comes from iZotope’s [RX plug-in documentation](https://docs.izotope.com/rx12/en/rx-overview.html?ref=izotoperx.net#rx-plug-in-comparison): RX Audio Editor isn’t a plug-in, while selected RX modules ship as plug-in components. VirtualDJ’s own forum records that initial VST3 support arrived in [VirtualDJ build 7131](https://virtualdj.com/forums/245135/VirtualDJ%5FTechnical%5FSupport/VST3%5Fsupport.html?ref=izotoperx.net). The same thread also shows why “VST3 supported” doesn’t mean every VST3 plug-in is guaranteed to work. Host behavior, plug-in version, channel layout and real-time load still matter. ## RX Editor, RX plug-ins and exported audio are three different things The RX Audio Editor is the full repair environment with a waveform, spectrogram, module chain and file-based rendering, and it’s where the most detailed work happens. You open an audio file in RX, select a problem, preview a module, render the change and export a new file. RX plug-ins are individual processors exposed to compatible hosts. If a component is installed in the VST3 location VirtualDJ scans, it may appear among external effects. That route can suit a narrow task such as controlling clicks or background noise during playback, but it has two limits: not every RX feature exists as a plug-in, and a processor that is excellent offline may be too heavy or too risky for a live deck. Exported audio is the most predictable bridge. RX does the repair or separation once, then VirtualDJ plays the result like any other prepared track. The render does not depend on a plug-in being found at show time, and the file can be auditioned, tagged and backed up before it enters a set. ## The RX-first workflow I recommend ### 1\. Decide whether you need repair, separation or live control RX earns its place when the source itself needs work: steady hum, clipped peaks, clicks, intrusive noise, a vocal that needs attenuation, or a section that needs spectral editing. All of that is preparation. Keep the original file untouched and make the RX render a separate version with a clear suffix. VirtualDJ’s own stem controls cover live isolation, quick transitions and effects that change during performance. A prepared RX stem can still be useful, but only add an offline step when it improves a specific weak source or supports an edit you want to keep. ### 2\. Use Music Rebalance when you need four broad source groups [RX Music Rebalance](https://docs.izotope.com/rx12/en/music-rebalance.html?ref=izotoperx.net) separates a mixed recording into four broad groups: Voice, Bass, Drums and Other. It can change the gain of those groups inside the mix, which helps when you want a reduced-vocal version, a stronger rhythm bed or a cleaner reference before building an edit. Start with the smallest gain move that solves the musical problem. Pulling Voice all the way down can reveal artifacts or remove instruments that share the same frequency and spatial cues. A moderate reduction often sits more naturally under another vocal. Preview the busiest section and a sparse section before committing, because separation quality can change within the same track. ![iZotope RX 12 Music Rebalance with Voice lowered to -6 dB while Bass, Drums and Other stay at 0 dB, beside a selected passage in the spectrogram](https://storage.ghost.io/c/2e/c1/2ec1682b-08cc-4997-b0d0-7361fc45beb8/content/images/2026/09/music-rebalance-rx12.webp "RX Music Rebalance four-part control") Music Rebalance gives separate level controls for each of its four groups; preview both dense and sparse passages before rendering. ### 3\. Use Stems View when separate files are the goal The [RX Stems View](https://docs.izotope.com/rx12/en/stem-split-pane.html?ref=izotoperx.net) is designed for listening to, editing and exporting separated material. It suits you better than a single reduced-vocal mix when you need individual files for a custom arrangement or want to inspect one source group without the others. Do not treat the separated files as perfect studio multitracks. They are estimates derived from a finished mix. Listen for vocal remnants in Other, cymbal texture in Voice and low-frequency leakage between Bass and Drums. If an artifact only appears in solo but disappears in the combined edit, it may not need more processing. ### 4\. Export a clean, easy-to-identify WAV The RX [Export controls](https://docs.izotope.com/rx12/en/working-with-files.html?ref=izotoperx.net#export-format-options) support common delivery formats including WAV, AIFF, FLAC, OGG and MP3\. For a working file headed into VirtualDJ, WAV is the safest default because it skips another lossy encode before playback or further editing. Keep the project sample rate when possible. Name the output so you can see what changed without opening it: `TrackName_RX-clean.wav`, `TrackName_RX-vocal-down.wav` or `TrackName_RX-stem-vocals.wav`. Preserve the untouched master beside the processed versions. ![iZotope RX 12 Stems view with Voice, Bass, Drums and Other lanes and the Export dialog set to 24-bit WAV](https://storage.ghost.io/c/2e/c1/2ec1682b-08cc-4997-b0d0-7361fc45beb8/content/images/2026/09/export-stems-rx12.webp "RX stem export to WAV files") Export the four stem groups as clearly named WAV files so each version can be identified before it reaches the VirtualDJ library. ### 5\. Add the render to the VirtualDJ library and compare it with the original Keep the original and the RX version together while you check the result. Load them on separate decks, match the same section and compare level, timing and artifacts. A repair that sounds impressive on its own can turn out too dull, too quiet or too processed once it sits beside the original master. For stems, decide how the exported files will be used before the set. You may build a fixed edit in another editor, keep an instrumental and vocal as separate performance assets, or combine only the groups you need. VirtualDJ’s [effects interface](https://virtualdj.com/manuals/virtualdj/interface/decks/decksadvanced/effects.html?ref=izotoperx.net) controls deck effects; it is not a substitute for organizing several exported source files into a repeatable arrangement. ![VirtualDJ two-deck view comparing an original track with an RX-cleaned WAV in the browser](https://storage.ghost.io/c/2e/c1/2ec1682b-08cc-4997-b0d0-7361fc45beb8/content/images/2026/09/virtualdj-import.webp "Compare the RX render in VirtualDJ") Keep the original and RX render visible in the browser, then compare matched passages on separate decks before adding the processed file to a set. ## When the direct VST3 route makes sense A direct RX component can be reasonable when the effect is light, the control needs to stay live and you have time to verify the exact combination before performance. Scan the normal VST3 location, load one component, confirm that its interface opens, and listen through a full representative passage. Save and reopen the VirtualDJ configuration before relying on recall. Watch for latency, dropouts, channel changes and controls that fail to recall. Avoid building a chain of CPU-heavy repair modules on a live deck merely because they appear in the effect list. RX modules are designed to solve damaged audio; many are more useful when you can preview, undo and render away from the performance system. iZotope’s current [product compatibility page](https://support.izotope.com/hc/en-us/articles/47669633839757-Compatibility-of-iZotope-Products?ref=izotoperx.net) is the place to check operating system and host support. VirtualDJ is not listed in the documented RX Connect or external-editor workflows in the RX 12 guide, so file exchange remains the conservative choice when recall matters. ## Choose the route by the actual job | Goal | Recommended route | Reason | | --------------------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------- | | Remove a click, hum or damaged moment | RX Editor, export WAV, load in VirtualDJ | Precise selection and reversible file preparation | | Reduce vocals for a prepared edit | Music Rebalance, export a new mix | Controlled offline balance with time to inspect artifacts | | Create source groups for an arrangement | Stems View, export separate WAV files | Individual assets can be edited and organized before performance | | Isolate stems during a set | VirtualDJ stems | Fast, interactive control without pre-rendering | | Apply one simple RX processor live | Try the VST3 component and verify the exact setup | Possible when the component loads reliably and latency is acceptable | | Send a deck into the full RX Editor | Export or locate the source file, edit in RX, re-import | No documented RX Connect round trip for VirtualDJ | ## Troubleshooting common problems ### The RX plug-in does not appear in VirtualDJ Confirm that the installed component actually has a VST3 version and that VirtualDJ scans the folder where it was installed. The full RX Audio Editor won’t appear as an effect. Rescan after installation, then see whether another simple VST3 shows up; that tells a general scan problem apart from an RX-specific compatibility problem. ### The plug-in opens but playback stutters Strip out other effects and run one processor on its own. Increase the audio buffer only if the resulting latency stays usable. If the module still disrupts playback, render the repair in RX instead of forcing a live chain. ### The vocal reduction sounds watery or leaves a ghost vocal Ease off the Vocal reduction and judge the result inside the intended transition or overlay. If you need a separate file, compare Music Rebalance with Stems View and keep the version with fewer audible artifacts in context. No separation method can recover information that was never isolated in the finished mix. ### The exported track is quieter or clips in VirtualDJ Compare matched sections and check the render level before blaming the host. Separation and repair can change peak level and perceived loudness. Keep headroom in RX, avoid normalization as a reflex, and set gain in the same way you handle other library files. ### The RX version replaced the original in the library Give it a distinct filename and keep the original in a protected folder. The processed file is a new asset. That makes rollback simple and stops an imperfect repair from becoming the only surviving copy. ## Related RX guides For deeper control of the separation stage, use the [RX Music Rebalance guide](https://izotoperx.net/izotope-rx-music-rebalance/) and the [RX Stems View guide](https://izotoperx.net/izotope-rx-stems-view/). The [RX import and export guide](https://izotoperx.net/izotope-rx-import-export-save/) covers file choices, while the [RX plug-in formats guide](https://izotoperx.net/izotope-rx-plugin-formats/) explains the difference between VST3, AU and AAX installations. ## Frequently asked questions ### Can I use iZotope RX directly in VirtualDJ? You may be able to load an individual RX VST3 component as an effect. The full RX Audio Editor is a separate application and is not loaded as a VirtualDJ effect. ### Does RX Connect work with VirtualDJ? VirtualDJ is not part of the documented RX Connect or external-editor workflows in the RX 12 guide. Use a file workflow: process or separate the source in RX, export a new file, then load it in VirtualDJ. ### Should I separate stems in RX or VirtualDJ? Reach for VirtualDJ when you need immediate live control. RX is for preparing and inspecting files before a set, repairing a weak source, or exporting separate assets for an edit. ### Which RX format should I export for VirtualDJ? WAV is the practical working default because it avoids another lossy encoding stage. Keep the original sample rate when possible and use a filename that clearly identifies the processing. ### Can Music Rebalance remove a vocal completely? It can reduce or isolate the Vocal group, but a finished mix rarely separates without remnants or lost musical detail. Judge the result in the intended arrangement and use moderate changes when a full removal sounds artificial.