Izotope Rx Asio Driver Problem

Izotope Rx Asio Driver Problem 4,4/5 8493 reviews
Plug-in Only

Overview

The RX Connect plug-in sends a clip, or multiple clips, to the RX 6 standalone application for editing and repair. This gives you access to all of RX 6’s modules in one place, and provides the benefits of RX’s offline processing and visual interface. RX Connect is available from the AudioSuite menu in Pro Tools, or as an AU or VST plug-in from your host’s effects menu.

Update: DJM-900NXS2, DJM-900NXS, DJM-850, DJM-750MK2, DJM-750 and DDJ-1000 driver Updates 12 March, 2020 Our XDJ-1000MK2 and XDJ-700 now support TRAKTOR PRO 3 including USB-HID control Updates 05 December, 2019 XDJ-RX Driver for macOS Update ver. Nov 14, 2016 I then downloaded a completely different DAW - this time iZotope RX5. This loaded the soundcard driver without any problem and recorded flawlessly. My takeaways from this are: 1. It's not the driver that's causing the problem. The correct version loads with 32 or 64 bit programs. IZotope RX is the most complete audio restoration product on the market, a unique standalone application designed from the ground up to combat a range of audio problems. Allows you to select a sound card driver model to use for playback and recording. Note: Some hardware devices monopolize the audio drivers when sending audio clips to RX via RX Connect. If you are not able to hear the audio sent to RX from your DAW via RX Connect, change the audio driver to RX Monitor in the Driver type menu.

Controls

For any program that you use that uses ASIO (including standalone plugins like Guitar Rig, iZotope RX, and so on), apply the following:-Anisotropic Filtering: Off-Antialiasing Gamma Correction: Off-Antialiasing Mode: Off-Power Management Mode (if applicable): Prefer Consistent Performance. I then downloaded a completely different DAW - this time iZotope RX5. This loaded the soundcard driver without any problem and recorded flawlessly. My takeaways from this are: 1. It's not the driver that's causing the problem. The correct version loads with 32 or 64 bit programs.

There are two modes for using RX Connect:

SEND FOR REFERENCE: This is meant for analysis only. The clips are imported into RX 6 but cannot be sent back to your host.

Note about Reference Mode

This mode of RX Connect will not open RX 6 Audio Editor automatically. Opening the Audio Editor after using send for reference will reveal the file in the RX Audio Editor.

SEND FOR REPAIR: Selected clips are sent to the RX 6 Audio Editor for repair, and you can send them back to your host from the RX Audio Editor.

More Information

  • For more information on using RX Connect in different hosts, please refer to the following sections, or refer to the knowledgebase for a more detailed list.

Host Specific Instructions

The following sections outline host specific instructions for using RX Connect to Send audio to the RX Audio Editor and back to your host application:

Adobe Audition CC RX Connect Workflow

  1. Inside of Audition, select the Waveform view.
  2. Highlight the area of audio that requires editing.
  3. In the Effects menu, load the RX 6 Connect plug-in from VST (or VST3) > Restoration> iZotope, Inc. (If you do not see the RX 6 Connect plug-in, open the Audio Plug-in Manager and Scan for Plug-ins, then make sure RX 6 Connect is enabled).
  4. When the plug-in window opens, click Apply.
  5. RX 6 will automatically load. Perform your desired audio edit, then click “Send Back” to send the audio back to Adobe Audition. The Waiting for Connect message will appear.
  6. Re-load the RX 6 Connect plug-in from the Effects menu. It will now display a message “Press Apply to commit changes.” Click Apply to apply the audio edit from RX to your audio file in Adobe Audition.

Avid Media Composer RX Connect Workflow

When using Media Composer, there are two separate workflows for using RX Connect depending on whether you are operating in Master Clip mode or Timeline Mode.

Master Clip Workflow
1. Open the AudioSuite Window from the Tools menu
2. Drag the Master Clip that you wish to edit onto the AudioSuite Window
3. Choose “iZotope RX 6 Connect” from the Plug-in Menu Selection
4. Click the purple Activate Current Plug-in button
5. Press the SEND button in Media Composer 7.0.x, or Optional in Media Composer 8.1.x to send the audio master clip over to RX
6. When you have finished editing your audio in RX, click the “SEND BACK” button
7. Back in the AudioSuite Window, press the OK button, and then Render Effect to commit changes
8. A new Master clip will now be generated into the designated bin

Timeline Workflow
1. Open the AudioSuite Window from the Tools menu
2. Select a single audio track in the Timeline, and then choose “iZotope RX 6 Connect” from the Plug-in Menu Selection
3. Click the Activate Current Plug-in button
4. Press the SEND button in Media Composer to send the audio master clip over to RX.
5. When you have finished editing your audio in RX, click “SEND BACK” button
6. In the AudioSuite Window press the OK button, and then Render Effect to commit changes

Recommendations

When rendering RX Connect as an AudioSuite effect in Media Composer, the resulting audio will exist in a rendered effect container for the duration of that clip on the timeline. If the clip length is extended beyond those bounds, the rendered effect will become un-rendered, as indicated by a blue dot.
To avoid losing the audio in the rendered effect container, we recommend either:

  • Achieve locked picture prior to the audio edit
  • Extend the bounds of the clip prior to the audio edit, perform the audio edit with RX Connect, mixdown the clip to a new audio file, and then reduce the bounds back to the original size
  • If you make extensive repairs inside of the RX Audio Editor, you can also save an .rxdoc of the file, which will preserve all your adjustments so you can modify them later if you need to.

Monitoring the output of RX Audio Editor

With some audio hardware systems, Media Composer will has control of your audio drivers so that you aren’t able to hear the output of RX.

However, we’ve built the RX Monitor tool to solve just this problem.

  1. Create a dedicated auxiliary audio track for monitoring RX
  2. Insert RX Monitor from the “Noise Reduction” or “Sound Field” menus.
  3. Now, go to the “Preferences” menu in the RX Audio Editor by clicking on the wrench icon in the top-right of the window.
  4. In the “Audio” tab, set your Driver type to be “RX Monitor.”
  5. Now you can hear the output of the RX Audio Editor through the audio output chain that Media Composer is using.

Avid Pro Tools RX Connect Workflow

  1. Choose the audio to be sent to the RX Audio Editor by selecting the audio clip(s) in the timeline that you want to edit, and opening RX Connect from the AudioSuite ‘Noise Reduction’ menu.
  2. If you just need to load a noise profile or analyze some audio, choose ‘Reference’ to send the audio one-way, but for the complete round-trip workflow click ‘Repair’ and then hit ‘Send’. You’ll see this opens the audio in the RX Audio Editor.
  3. With HDX systems, Pro Tools will have control of your audio drivers, so you aren’t able to hear the output of the RX Audio Editor. However, the RX Monitor tool is built to solve just this problem. In Pro Tools, create a dedicated aux track for monitoring RX, and insert RX 6 Monitor from the ‘Noise Reduction’ or ‘Sound Field’ menus,
  4. Then, go to the ‘Preferences’ menu in the RX Audio Editor by clicking on the wrench icon in the top-right of the window. In the ‘Audio’ tab, set your Driver type to be ‘RX Monitor’. Now we can hear the output of the RX Audio Editor through your Pro Tools output chain.
  5. After you’ve made the desired edits in RX, click ‘Send Back’ at the top of the window. Back at the RX Connect window inside of ProTools, click ‘Render’, and the repaired audio will be placed back into your session.

Tips

  • Some engineers might choose to create duplicate playlists before making any repairs to their audio, but you can ‘undo’ these RX Connect changes just like any AudioSuite process.
  • If you make extensive repairs inside of the RX Audio Editor, you can also save an .rxdoc of the file, which will preserve all your adjustments so you can modify them later if you need to.

Audiosuite modes:

When using Audiosuite plug-ins, there are various user definable input and output options, which affect how you may use RX Connect. These options are:

Input

  • Clip-by-clip: Recognizes individual clips in the timeline, as well as fades.
  • Entire selection: Treats the entire selected area as one clip.

Modes

  • Mono mode: Treats mono, dual mono and stereo clips, as well as multi-channel clips, all as discrete mono clips (e.g. a stereo clip will send as two separate mono files).

    Mono mode note

    Please note, this can result in large groups of audio clips being sent to RX, potentially exceeding the maximum file limit of 16.

  • Multi-input mode Treats dual mono and stereo audio clips as one entity.

Output

  • Overwrite files Destructive processing of the audio clip(s) in the session, overwriting the original file with the new file sent from RX.
  • Create individual files: Nondestructive processing of the audio file(s) in the session, replacing them with the audio processed in RX. This mode preserves individual clips and fades/handles.
  • Create continuous files: Nondestructive processing of the original audio file. Creates a new audio file with the audio sent back from RX, consolidated into one continuous clip.

More Information

For the most up to date information on the expected behaviors when using the recommended configurations, please click here

Steinberg Cubase & Nuendo RX Connect Workflow

  1. In Cubase/Nuendo, select the audio clip for processing.
  2. Select the RX 6 Connect plug-in from the the plug-ins menu (Audio > Plug-ins)
  3. The RX 6 Connect plug-in window will open.
  4. Depending on your requirements please select one of the following choices:
    a. Send for reference: meant for analysis only. The clips go to RX, but do not come back.
    b. Send for repair: the clips are sent to RX and, after they are cleaned up, you can send them back to your DAW.
  5. Once you have made your choice, press the process button to send the audio to RX.
    The RX 6 application will automatically open and receive the audio (if you selected send for reference, you will need to manually open RX and the file will appear).
  6. You can now carry out any repair, restoration or cleaning using the full selection of RX modules.
  7. Once you are happy with the edits, you can simply press the “send back” button at the top of the open window to send the audio back to your DAW.
  8. Once complete RX will show a window asking to re-open the RX 6 Connect plug-in.
  9. Back in Cubase/Nuendo, select the RX 6 Connect plug-in from the “Audio Plug-ins” menu.
  10. Press the process button to commit the changes to the original audio file.

RX 6 as an external audio editor

Some hosts don’t support the use of RX Connect for round-trip editing, please refer to the instructions below for host specific workflows.

Adobe Premiere Pro CC with RX as an external audio editor

  1. Inside of Premiere, right-click on an audio clip in your timeline and select “Reveal in Finder” (OS X) or “Reveal in Explorer” (Windows).
  2. Open the resulting file in RX 6 Audio Editor.
  3. Perform necessary processing in the RX application
  4. When you have made the desired changes to your file, go to the RX File menu and select Overwrite Original File

Note

  • If you have Adobe Audition installed as well, you can right-click on an audio clip in your timeline, and select “Edit Clip In Adobe Audition.” Then follow these steps for using RX Connect with Adobe Audition CC

Apple Final Cut Pro X with RX as an external audio editor

RX is a powerful audio editor that Apple Final Cut Pro X users can use to get better sounding audio in their video projects.

Izotope Rx Asio Driver Problem Windows 10

  1. Select the clip you want to edit in your Final Cut Pro project
  2. Hit Cmd-Shift-R to Reveal in Finder
  3. Open the revealed file in RX 6 Audio Editor and make any necessary edits.
  4. When you are done, in RX choose File>Overwrite Original File to automatically update the clip in your Final Cut Pro project, or File/Export to make a new file, and then import that edited file into Final Cut Pro

Apple Logic Pro X with RX as an external audio editor

RX is a powerful audio editor that Apple Logic Pro X users can use to get better sounding audio. To use RX with Logic, you must first set it up as an external audio editor.

How to set up RX as an external audio editor

  1. Open Logic Preferences and go to Advanced
  2. Under Additional options, enable the “Audio” check box.
  3. In Preferences, click the “Audio” tab and select the “Audio File Editor” tab.
  4. Under Audio File Editor, click on the External Sample Editor to select RX 6 from your applications folder

Workflow

  1. Select the clip you wish to edit in your timeline
  2. Click Edit > “Open in iZotope RX 6 Audio Editor”, [Shift+W]
  3. The file will open in RX 6. Once you’ve completed your edits, in RX 6 click File > Overwrite Original File
  4. Close the tab, navigate back to Logic Pro X and wait for the waveform to update

Earlier this year (in February), the studio that I work out of has moved from Mac OSX to Windows (Moving to the Samplitude DAW, which is Windows only). I have been using the same RME Fireface UFX interface. I used a firewire connection on Mac and now am using the UFX via USB on this Windows laptop. I am disappointed to say my experience has been not been too stable so far- I hear that RME interfaces are generally quite stable on Windows, although I have had some uncommonly bad luck it seems.

Occasionally, Totalmix FX will freeze and stop responding, and show the meters frozen as well. When this happens, the DAW freezes, and if the DAW was recording, audio capture also stops. During this time, no audio programs or Totalmix/Totalmix USB Settings will respond at all. I have to unplug or turn off the Fireface, and re-plug it/turn it back on, and immediately when unplugging the interface, the freeze stops, and the audio software begins to respond again. While Totalmix is frozen, the interface itself (its buttons and small built-in LCD screen) still respond okay.

Izotope Rx Asio Driver Problems

The bug seems to happen randomly, but does occur slightly more frequently while changing audio programs, loading plugins, or performing some sort of action in a DAW. Disabling 'D2D' in the Totalmix settings also makes the problem happen much more frequently, where the freeze would then be accompanied with a loud 'pop' noise.

I have tried the following to fix it:
-Upgrading to Intel's latest USB3 drivers, upgrade all of the laptop's drivers and firmware, and upgrading the interface's drivers and firmware to the latest versions
-Uninstalling RME drivers via 'Programs and Features' and re-installing
-Using an Expresscard USB2 adapter and plugging in the interface via USB2 instead of USB3
-Using three different USB cables
-Disabling Selective USB Suspend in power options
-Disabling power saving on the USB3 root hub
-Disabling integrated graphics and going to only discrete GPU
-Disabling CPU voltage throttling in the Windows power options by setting min and max CPU to 100%
-Disabling voltage throttling in the BIOS
-Disabling a number of security-related CPU features in the BIOS
-Run the DAW and Totalmix on integrated graphics only via the nVidia options
-Disabling hardware acceleration (D2D) in Totalmix
-Locking registry and enabling MMCSS in Totalmix settings
-Disabling Aero in the Windows 7 display settings
-Removing all peripheral devices
-Using another DAW
-Disabling anti-aliasing, v-sync, and other related settings in the nVidia control panel for Totalmix and the DAW
-Running Totalmix as an administrator, and using various compatibility modes
-Using another RME interface (I also tried using my RME Babyface, and the problem still occurs)

Here's the interesting bit: When Totalmix is minimized to the notification area, and no Totalmix window is actually loaded up, the problem never happens. This freeze only seems to happen if a Totalmix window is present, and showing on the taskbar. This lends me to believe it may be graphically related, although I am not 100% sure.

To further test, when I plugged in an old M-Audio USB interface, I was able to use it for several hours without any problems. For some reason, this issue seems to be specific to Totalmix.

I have noticed a few other threads that show similar problems, although I am not sure whether they are the same cause:

Asio Driver Mac

https://www.forum.rme-audio.de/viewtopic.php?id=22360
https://www.forum.rme-audio.de/viewtopic.php?id=16235
https://www.forum.rme-audio.de/viewtopic.php?id=12436
https://www.forum.rme-audio.de/viewtopic.php?id=21566

After e-mailing the RME support, they told me that this is not a reported problem at all, that the above links are not similar enough to my problem, and asked me to contact my computer manufacturer instead. Needless to say, Lenovo support had no expertise in this particular issue, and wasn't able to suggest anything that I hadn't already tried.

Has anyone experienced this problem, and knows what to do to fix it? Has anyone had this freezing issue on newer versions of Windows (Windows 8 or 10) as well? I tried using the interface via Firewire by using a Startech expresscard, but that did not work (every time I initialized ASIO, there would be a loud and constant distorted/crackling sound).

The laptop is a Lenovo Thinkpad P70. The specs, if they are important to know, are:
Intel Xeon E3-1505M v5 CPU, DDR4 type ram, running from a Samsung NVMe hard drive, USB3 and 3.1 ports, USB2 via Expresscard adapter, integrated and discrete GPU (The discrete GPU is an nVidia Quadro M3000m. Optimus GPU switching or discrete-only GPU modes are available, but integrated-only is not available on this laptop). The OS is Windows 7 64 bit. I use an external HDMI monitor (A Samsung TV) and use this HDMI connection for audio passthrough as well, for non-ASIO purposes like web browsing and so on. I also have two USB hubs plugged in, one with the keyboard and mouse, and the other with an iLok and eLicenser plugged in. I always record in 88k/24 bit or 44.1/24 bit, and my primary DAWs are Studio One v3 and Samplitude Pro X2, although I have seen this problem in Guitar Rig, Sibelius, and other programs using the UFX ASIO.

Asio4all

If anyone has any experience with this issue, please do let me know! Any help or input would be greatly appreciated.

______________
EDIT (25th October, 2016) - Solution:
After talking to nVidia and trying various versions of their Quadro graphics drivers, the issue seemed to be related to either the graphics drivers themselves, or how Totalmix was interacting with that particular variant on the graphics drivers. The older versions of the Quadro drivers were far worse. What is unusual is, not only was Totalmix affected by unstable graphics drivers, but the DAWs and all programs using ASIO were affected as well. For reasons I don't quite understand, a computer's graphics drivers seem to be able to directly affect the stability of ASIO (when, intuitively, it seems like they should be separate). In Samplitude Pro X2 (it seems to be improved in the new X3 version), the less stable versions of the graphics drivers would result in lost ASIO buffers every time I would load a plugin window, or do anything that required something to be rendered.
I've since then moved to Windows 10, and I'm happy to report that the newest versions of the nVidia drivers, combined with the newest RME drivers, seem to work without any problems, both on Firewire and USB. I have noticed that, on previous versions of the drivers, a few settings tweaks in the nVidia control panel improved stability a lot, especially with GPU-rendered plugins like Fabfilter and Vienna MIR Pro. If someone still has issues with what appears to be graphics-related instability, try the following:
Open the nVidia control panel, go to 'Manage 3D Settings', and then to 'Program Settings'.
For any program that you use that uses ASIO (including standalone plugins like Guitar Rig, iZotope RX, and so on), apply the following:
-Anisotropic Filtering: Off
-Antialiasing Gamma Correction: Off
-Antialiasing Mode: Off
-Power Management Mode (if applicable): Prefer Consistent Performance
-Multi-Display/Mixed GPU Acceleration: Single Display Performance Mode (Multiple monitors still work fine in this mode)
-Shader Cache: Off
-Threaded Optimization: Off
-Vertical Sync: Off
This seems to make a big difference. Also, it might go without saying, but if your laptop/computer supports nVidia Optimus GPU switching, disable that and switch to GPU only. Optimus is generally awful, and GPU-only-mode can (if need be) free up a little bit of CPU for audio processing too.