Izotope RX Connect issues

Wait!
Don’t start the ‘it’s all iZotope’s fault’ posts until I have my popcorn ready…

1 Like

This. I have this happen frequently. Or sometimes I undo one too many times (undoing RX Connect add/modify) & have to start over on my edit. I’d love some sort of enhancement to improve this workflow.

I just typed a detailed overview of the initial problem with RX, but then I saw Oliver Lucas’ post …
And decided to let it rest. Been there, done that, bought the T-Shirt.
:slight_smile:

Fredo

1 Like

You can only RX Connect one clip at a time for it to consistently work. It’s a drag when it’s a complicated edit, so I duplicate the edited clip group (leaving head and tail if I need to Learn noise), bounce the dupes to one file, then process that. You can also round robin it through the pool and process the whole unedited clip.

1 Like

I’m having the same issues :frowning:

Seriously wish this would be fixed (don’t really mind how or by who). Without a proper RX Connect workflow I’m leaning back onto ProTools and nobody wants that!

Also - can anyone answer why the audiosuite RX modules (most notably Dialogue Isolate and Dialogue De-Reverb) don’t show up as direct offline processes?

I asked izotope about that lately considering the purchase of rx 8 but still modules aren’t available as DOP in Nuendo. They said because of the huge CPU load these Plug-Ins cause…to me that’s not really comprehensible cause why would it take less CPU Power in Pro Tools than in Nuendo? It’s more likely that Pro Tools is meant to be kept in a slighly better position but write to izotope - you’ll always get response and if many want to have dialogue isolate/de-rustle/dialogue de-reverb as a DOP then maybe they’ll start programing :wink:

What a pile of bull****.
CPU is CPU, no matter if Nuendo, PT, Reaper or Pornhub is running.
Secondly, during an offline process, CPU- performance is a non-issue.
Even if you would only have the smallest amount of CPU power, it will just take longer to process.

Fredo

https://support.izotope.com/hc/en-us/articles/360032637174-How-to-use-RX-Connect-in-Steinberg-Cubase-or-Nuendo

8.1 is out which fixes some Nuendo/Cubase RX Connect issues.

Agreed. I suppose that’s based on the assumption, that VST (3) plugins are always realtime processes, while AudioSuite is a plugin format specifically tailored to offline processes. However, VST 3 plugins can provide special support for offline (non-realtime) processing as well, as this information is provided by the API (if called on export or in DOP). So the excuse by iZ is a bit lame.

Cheers,
Mike

I’m not able to get Connect working with Nuendo 11 and Izotope 8. After sending to RX, running processes, and sending back, I hit ‘Apply’ and it sends it back to RX afresh. I can’t see any way to get the processed audio to be accepted by Nuendo. What am I missing?

Looks like it’s an old problem, and on Macs only (not on PCs).

The workaround I’ve discovered so far is that for some reason, RX Connect 7 (rather than 8) is actually working – so I’ll be using that for now –

I’m continuing to have trouble getting RX Connect to work at all, either 7 or 8 – is anyone actually having it work consistently, and have any tips for getting that to happen? Thanks!

I edit my clips first and then “bounce” them to a new audio file which I then transfer. I feel I have had the most problems when I have used clips “as is”.

go back to Pro tools already. lol i’m joking, but aren’t you the guy that was a long time Nuendo user that left for Pro tools mostly because of RX connect issues? If so why lurk around here

You asking me?

no replying to Oliver’s comment above

exactly works fine this way.

RX8 actually works for me, but occasionally I get a blip. Make sure you uncheck auto-apply. RX8 connect actually works sometimes but could glitch up and not apply your updates/edits in Nuendo. My best workaround is to select the event, go to Audio—edit in Wavelab, and then use RX8 as external editor, save the file in RX after editing, return to Wavelab and click send back to Nuendo/Cubase and your changes are reflected. It works 100% of the time, no glitches.

I have been trying to get Izotope to address this issue for a while now. They replied with a possible solution to the problems. However, it does not work for me most of the time. Maybe some of you will have more luck with this hack. As for now, RX6 is still the only version that works without any major issues.

"Hello,

Thank you for contacting iZotope Customer Care! I’m sorry to hear that you’re having trouble!

Currently, our developers are aware of this behavior and we hope to have a fix for this in the next update. In the meantime, we do have a workaround to get it to work again.

This behavior usually happens when closing a file tab in RX. It seems to put Connect in a state where it does not realize that it sent an audio file to RX and therefore will not allow you to apply changes.

  1. Delete the files within your RX 8 Session Data folder, this is located within the “Hidden Library” folder.

  1. Restart Neundo, and it should work as normal again.

If you have any additional questions, please feel free to contact me back!"

Good luck guys!

I just got a similar response:

"Thanks for reaching out to us.

Currently the limitations between RX Connect and Cubase or Nuendo are known issues that are on the RX team’s fix list. I do apologize that this isn’t resolve at this time. My best recommendation here would be to use both applications (Neundo and RX) in tandem to export and edit your audio as needed."

Good to know they’re finally acknowledging it and working towards a solution.