Hi all!
New (maybe) weirdness I’m having. Maybe this has always been the case but I started doing more and more Rx editing and less individual iZotope plugin edits through DOP to get more surgical and precise with Dx cleanup. In DOP you can bypass/move back through the history of edits, which has always worked great for me with individual iZotope plugs.
But with connect whenever you bypass it or move to a previous part in the chain it completely erases what was done through the Rx Connect. I can work around this, and I can see why this behaves this way (I’m guessing to Nuendo all it sees is that the file was connected to Rx, it doesn’t actually “save” the processing?), but I’m hoping maybe I’m just missing something.
Anyone have a good workflow when using Rx connect for easily going back a few steps without needing to redo processing?
This is called INNOVATION! Thank you dear Steinberg! Appreciate much for this!
That’s a ridiculous take on this. How is Nuendo supposed to know what processing actually took place - including settings of parameters - inside an outside editor???
And if your answer is “just reuse the old processed file” then the answer is still that all the iZotope Connect plugin does is send audio to and from RX. That’s all that’s there. So DOP likely properly executes the actual plugin’s (Connect’s) parameters.
And even if it could retain the audio itself then the question is what use it is if you choose to redo processes before the RX process. RX would have to recalculate anyway.
This is pretty much purely a problem with using an external editor and is exactly why ARA inclusion is what people have been wanting.
So while you whine about this not working, something probably NOT within Steinberg’s control, they actually did add something useful to help you exactly with this problem; ARA and Spectralayers integration.
Yeah, Nuendo could be better. It will improve. But let’s at least not complain about things Steinberg probably can’t fix in the first place.
Yeah I kinda figured. Thanks!
What’ s the benefit of this behaviour? What’s the purpose to process affect again?
Old processing function prior to N8 worked rock solid with understandable undo/redo. What was the purpose to break it? To look fancy? I still can’t understand.
How did Nuendo 7 work with iZotope RX Connect at the time? Any differently?
Like a charm! It sends and receives without bugs, glitches and double recalling RX connect window! And undo/redo switches on the fly! It’s very important for my workflow.
I still don’t understand - what was the purpose to rewrite such an important part of the program! In favor of what? Drag and dropping plugins from tracks? Huge mistake by steinberg
Possible it was on iZotope’s end. Mattias is right that Steinberg has no control over what 3rd party companies decide to do with their coding that can affect how it behaves with Nuendo, which is why I wasn’t too surprised to hear my gripes are normal. 
Now that iZotope 11 is being introduced with ARA for Pro Tools I hope to see future updates with Nuendo. Although currently it’s just basic controls, no specific modules or module chains. Step in the right direction though.
It’s not ONLY RX. It’s all cpu hungry plugs. Expecially if you process multiple objects. Pressing undo/redo can take a huge amount of time.
And I’m triying to figure out, what is really the benefit.
All users who worked in N7 and previous versions can confirm that the previous version of offline processing was rock solid through all versions, starting from N2.
And DOP window is also sometimes unpredictable. with some FX I have to press FX shortcut twice.
This is a known issue with iZotope, not Steinberg. We’ve been through this a million times. iZotope releases new versions and they break functionality with DOP. It’s not the Nuendo version that’s the problem.
So just so we’re 100% clear now, this is the process in older Nuendo versions:
1: You use “Connect” plugin to send to RX.
2: process in RX.
3: send back to Nuendo.
4: “Commit” in “Connect”.
5: apply another process.
6: undo your RX process in Nuendo.
7: Redo your RX process.
And the result is exactly as it was after step #4 without ever touching RX a second time?
The purpose was stated several times over the years. One argument in favor was that it takes load off your computer by moving processing offline. Another argument was indeed the possibility of drag-and-drop processing from tracks. Yet another was the easily accessible presets.
I just used drag/drop on a job a couple of days ago. It’s incredibly convenient if I’ve chosen to automate a plugins settings for a range and change my mind to do offline processing instead. Just open the window for that event and drag and drop onto it. I also use presets on literally every job I do. For some jobs I know exactly what needs to be done on some dialog and just open up the window with all relevant regions selected, click three boxes, done.
There are so many improvements in Nuendo 13 relative to versions before 8 it’s almost mind boggling to consider going back to that. Like it’s not even close.
If v13 is so bad I really wonder how I’m able to put in all these hours on it delivering to everything from AMC to CBS to FOX. It’s weird.
Well what are you referring to? Are you saying that if you have a processing chain of let’s say 5 steps and you press “undo” DOP will reprocess 1-4?
Or are you saying; what if you delete step #3 and want to keep 1, 2, 4 and 5?
It’s a false and manipulating take!!!
Everything was there since Nuendo v1
We used offline processing for more than 20 years - so nothing new!
So the only difference is drag and drop and more user friendly presets! In cost af multiple non ending bugs and awful undo/redo!
It was just a comment on the general idea of offline processing. Calm down.
So something new after all.
Could you answer my two questions though? I’m trying to understand exactly what you think is broken or worse.