I know this has come up before… but dang it, it sure would be great to have this issue finally fixed:
I’m trying to apply DX Revive Pro to a group of events, all different files in the same project (obvs).
Per every iteration of Cubendo, the DOP hangs and never completes, ultimately ending in a nice red “Nuendo is not responding” in my Force Quit dialog box.
I empathize completely with the Nuendo vs iZotope multiple clip processing issues in DOP; those people have been moving backwards on RX since version 10 and have never really gotten DOP straight. But Revive is a regular (And, OT, amazing) plugin, being used in a way that seemingly OUGHT to work. I’ve tried processing multiple clips both from the Pool and the Project Window. No joy.
Any ideas, workarounds and/or fixes? Having this work properly would be an enormous time-saver. In this case I’ve got narration from various studio rooms where I’m trying to minimize the differences. DXRevive does a GREAT job of handling this, but for this project of 60+ chapters I’m having to treat each one individually, and it’s a major time-suck. Am going to deal with it now by bringing them into RX10 Standalone and running a batch, then re-importing.
In my view, that’s a step I shouldn’t have to take, given the promise of multiple clip processing in DOP.
Am I mistaken, or is this a problem being worked on?
Thanks; no rant intended. Now to process those files outside of Nuendo. See you all later.
And a little update… despite the “Not Responding” and apparently stalled app, there is activity in the “Completing Offline Processing” window. In other words, looks like it is working, despite other Indications.
May be worth noting that VERY little demand is being made of my computer’s processors.
When processing in RX, all cores are typically maxed when lots of files are being worked on.
I haven’t been through this exact problem, but I’ve noticed that DX Revive is quite taxing on DOP for some reason. It is a very heavy plugin to have as an insert as well, so that probably has something to do with it, but it doesn’t seem to stop there.
In my case, for example, no matter what I have in DOP on a clip, DxRevive always takes the first slot of processing. I have no idea why. I just can’t keep any plugins before it. Go figure.
Perhaps too many instances of DxRevive in DOP is simply too much for Nuendo to handle and it just breaks down, seeing how fragile DOP seems to be.
To me, as great as DOP is, it needs a major overhaul. We have issues in reliability, workflow, consistency of behavior (some plugins make the audio “slip”, for example), etc.
We should be able to access a list of DOP processing in a project, we should have a fully working transport+clip timeline for clips, we should be able to see where each processed region is in a clip, bypass on and off shouldn’t warrant a reprocessing of the clip, favorites are incredibly unflexible and half-assedly implemented, etc.etc.etc.etc.
Just reporting back here that an hour and a half later the DX Revive processing successfully completed. And that having been said, I agree with Mssr. Staino– there’s significant room for improvement here.
For me, multi-core use, plugin processing-wise would be great. Have no idea how that would work; I’m not a coder. Maybe it’s not possible within the Cubendo framework. But if it is… well… it is one thing that iZotope actually does reasonably well.
Anyway… my files are batch-processed; back to work.
Still… great feature, could use some sprucing up after all this time.
I have not used dxrevive in nuendo yet, only in PT. But it is a cpu hog to say the keast. Rendering a 45m interview took 22min (studio3 4 bands).
Soo perhaps this is just a matter of a very heavy tool.. i do think however that DOP should show some kind of progress bar or at least not become unresponsive.
Yeah while reading this thread I was going to sugget to check your processes to see if Nuendo is working in the background. Sadly this happens for alot of things and can feel like Nuendo is not responding (may even indicate that but its actually still working). For example on track import of a large session. We need some possible UI indicators of the program working at least, progress bar etc.
This is less a comment on DX Revive’s CPU use (I say, great: whatever it takes to make it do what it does, as well as it does!) as it is that DOP is not the most reliable tool in the shed under certain conditions.
I’m more concerned with Nuendo’s apparent inability to maximize use of available resources when processing, and especially the lack of an effective batch processing feature.
These are not generally concerns for me when working on music (unless I’m dealing with especially noisy tracks that could be handled with the same plugin chain).
But when working with narration in audiobooks, it’s not unusual to have source material from more than one studio (or different rooms in the same studio). DX Revive is a great way to find a happy medium between various locations, and if I detect that early enough in the process I can batch the files using Revive as a plugin in iZotope RX. But sometimes, for whatever reason, the initial pre-processing is not enough, and if the stuff is already in the project it can be a real pain to send the files out for additional processing and then bring them back. RX 9 can’t handle DX Revive as a plugin, and RX10 doesn’t play nicely enough with Nuendo (forget about RX 11!), so I’ve taken iZotope’s advice and just use RX9 for working within Nuendo. This means that if I want to batch process using all of my available CPU, I have to re-batch in RX10 Standalone, where DX Revive DOES work.
I know this is a bunch of plugin word salad. Bottom line, again: It would be GREAT to be able to do all of the stuff I need to do within Nuendo… and for it to use all available cores.
I came here because I’m experiencing exactly the same… staring at the screen for 30 mins now, 45 mins to go according to Nuendo. And yes, about 16% CPU activity, 3% network/disc…. don’t get it.
I guess the workaround is only do small batches… I would have forced quit but Nuendo has also decided not to auto save today. .-D
Yes, I can confirm DXRevive keeps crashing in N14 (via DOP), often with different error messages.
I’ve already sent the logs to the developer, but the issue still persists.
Seems like the plugin is quite unstable inside Nuendo.
I have not had any problems with DX Revive crashing; it’s been very stable here. This thread is more about performance in general as it relates to DOP batch processing.
