RX4 connect

Yeah not in the same ball park. Wavelab actually bundles Sonnox restoration plugs. Not as good by a long shot.

Hi all - wondering what luck you’re having with RX Connect. I’m at about 65% success rate right now.

Nuendo is crashing quite a bit when connecting files back from RX4 Advanced to Nuendo 6.5. I think I’ve narrowed it down -

Working on an extensive dialogue edit for a short film, most shots are LONG (in time) so pulling a lot of PFX from the parent region matching the cut. I’m on an NR pass of the PFX, RX Connecting the region from Nuendo > RX4 Adv, processing, then RX Connecting them back from RX4 Adv > Nuendo. I’m noticing that when I send a region from PFX (again, edited from the main recorded track, obvs.) to RX4, the entire parent region is showing up to be processed in RX4. I’ve only cut out the door slam, but the entire track shows up. As you would expect, when I Connect the next region, (a door open, from the same file but later in time) the entire parent region shows up in RX, again. Connecting the files back successfully can mean multiple copies of the same file.

Like I said, I have success but not nearly as much as I would like. I’m wondering if there’s a Nuendo pref in regards to file handling that I should have selected. As a workaround, I’m RX Connecting files from Nuendo to RX, processing, then simply exporting from RX to a folder with files to import with new, TC-based filenames. Would love to hear any suggestions.

iMac, Mac OS 10.8.5, Nuendo 6.5.3, Apogee Duet

Its a drag but you could bounce audio in place before connecting - create new files. Easier than exporting from RX to a new folder.

There is a pref in Nuendo to ask you if you want to create a new file after offline processing, but I think it defaults to “on”. Either way, it won’t help with what’s being sent to RX. I think bounce before RX is the only solution.

What’s weird is that I at first had no problems with Nuendo crashing using RX connect, then all of a sudden I started getting them. The experience is similar: Select event in Nuendo, connect it to RX, edit in RX and send it back, and then upon using connect to “re-import” it I get a dialog box and Nuendo freezes with no way out except for a “force quit”.

I did update to the latest version of RX but it changed nothing. So I agree, either bounce audio or skip ‘connect’ all together. I’m inclined to do the latter now. No time for frozen apps and then having to redo work.

Very disappointed this doesn’t work better.

Agreed, Lydiot - I upgraded thinking it would solve the issue, but it appears that the more I use it, the more consistent the problem becomes.

One of the issues I think I’m coming up with is duplicate file names on the way back to Nuendo, without matching files. After a crash, I’ll reopen my session and pick up where I left off. I think that, despite that Nuendo didn’t import the file into the timeline, a file with an identical name has replaced the original at that point. Re-opening the session and reconnecting what I thought was the original file caused crashes on way back to Nuendo over and over. Not 100% sure, but I think this is a cause of my headache.

Again, workflow killer. Definitely bounce the files before sending to Connect and Connect them back if that’s how you want to work - if you don’t bounce, it appears that the original TC metadata (origin) is erased after exporting from RX. Additionally, if you don’t bounce, you’re left with a TC-less PARENT file with no time information for sync.

UGH.

Just confirmed that the problem on my end involves a duplicate filename, perhaps originating in Nuendo. I’ve found that bouncing the file twice, and using the last (2nd) file as the file to process in RX alleviates the crashing for now.

Alright, so processed a file in RX via RX Connect, sent back to Nuendo, Connected no problem. Cut a piece of that just Re Connected region, sent that to RX via Connect, processed, sent back to Nuendo and got a crash.

I’m working on a show right now so I won’t have time to test until later. I noticed however that after a crash Nuendo would revert to the previous version of the file. This to me is bizarre since I would think RX would either a) write to original file, or b) write to new file and tell Nuendo to reference that new file. However, if it’s the latter I would expect to find that file somewhere on my computer, and I haven’t so far. If I did, at the very least I could re-import that into Nuendo after it’s rebooted. As it stands now not only is my Nuendo crashing and restarting without the latest cleanup in RX, the file disappears in RX after the attempted connect leaving me with lost work, period.

But I suspect you may be right. I started bouncing files before connecting and it worked for a while, but I also haven’t paid attention to how or if I labeled those bounced files. I’ll do some testing since my hunch was what yours is, that something is funky with duplicates. Perhaps relabeling will help…

I sure appreciate this thread. I’ve been slammed since RX4 showed up, and based on all of this I’ve sidestepped the Spectral Editor/ RX Connect thing completely. I’m running the regularly offline processable RX4 plugins as key commands, but am, as Lydiot suggested earlier, sticking with the RX3 Spectral Editor. Wish I had time to jump in on the testing.

Sure wish they hadn’t removed it, but the old one still does the job as well as it ever did.

Chewy

My previous workflow (that I’m still using since connect ain’t workin’) is to just create a separate track called “to rx” and then move any event on there in the dialog edit process, then bounce it, then switch over to RX and import a bunch at a time. I then just export back to the audio folder and import back in Nuendo to a “from rx” track and line up. With ‘connect’ being so wonky it’s actually just as fast once key commands are set.

does anyone uses Nuendo 6.5 and RX4 connect on Yosemite? I get a crash of Nuendo everytime. Does anyone has a fix for Yosemite?

http://www.steinberg.net/en/newsandevents/news/newsdetail/article/yosemite-compatibility-information-2945.html

Another quick update/notice -it would appear that the waveforms of previously RX Connected files are, at times, incorrectly displayed.

FRUSTRATING.

In what way?

Should have posted. Best I can tell is that they are displayed as the original file (instead of RX processed), in this case very low gain files.

Copying a file and bouncing it shows the correct waveform.

Yes, I see the problem as well. I think this is related to how Nuendo handles audio file labels in folders. I just tried to record a file on an audio track, called “spdif in” resulting in the file “spdif in_12”. I then copied and pasted that audio and then bounced it which gave the name “spdif in_01”. But it just so happened that the audio files folder already contained a file with that name and now contained two, and upon reconnecting from RX back to Nuendo it crashed.

What is weird is that I restarted and did the same and now the name of the bounced file is “spdif in-01”, i.e. a different naming convention…!

Either way one has to be careful here. I suspect that this issue may compound as crashes occur if files aren’t automatically deleted in the crash. What I mean is:

1: You have a project with a bunch of files, call it “set A”.
2: You do edits etc including bouncing files and get “set B”.
3: You round trip to RX fine, except somewhere in the previous step you ended up with a duplicate that now crashes Nuendo when using connect.
4: You force-quit and restart Nuendo which now has references to “set A”. Since it doesn’t remember “set B” - because it wasn’t properly shut-down/saved - further bounces can yield more duplicates (?), which yields more crashes.

It’s not working for me at all. I used to use RX denoiser for cleaning up guitar parts and electric bass hum but I can no longer get it to work inside Cubase. I tried the connect feature and sometimes it opens up but it does not process anything.

Does anyone have a fix or workaround for this?

Start a new topic in the Cubase forum, and specify the version of RX you’re currently using please. It will help us to help you.

I don’t know where the “Process” button is that it is asking me to press??
It seems that I perform the fix, send it back, and then it asks me to “press process to commit changes” but there is no button to press? When I hit apply it just takes me back into connect. Does anyone know how to process this?