Comments

farss wrote on 10/9/2012, 3:33 PM
Why not just Save As a new take out of RX2?

Bob.
FrigidNDEditing wrote on 10/9/2012, 8:31 PM
I am, but the workflow is extended, and I'm already working 16-20hr days right now, so was trying to work it out in Vegas if possible. Hence the reason I'm asking if anyone can confirm :)

Any luck reproducing it?

Dave
Ros wrote on 10/9/2012, 9:19 PM
Works fine here, I applied Denoiser from RX2 as a VST on an event and rendered it.

Rob
Laurence wrote on 10/9/2012, 9:30 PM
I've noticed that V12 is actually quite stable until I start adding plugins. Yeah I've been getting crashes with iZotope, New Blue and BorisFX. Usually restarting Vegas clears it up and it nowhere near as bad as it was in V11. Audio plugins seem more crash prone than video plugins, and I've also noticed gain structure changes when I add audio plugins.
malowz wrote on 10/9/2012, 10:38 PM
same here, vegas 12 worked fine in everything (no GPU), until started using 3rd party plugins.

got crashes while using newblue filters, boris continuum complete filters, and on izotope rx2 VST as well.

not a single crash using only "standalone" tools so far.
Grazie wrote on 10/10/2012, 12:39 AM
I've had IZO VST issues from VP10 thru VP11. I now, by choice, go DX.

I did have success when I did rescan the VST folders but slowly got the VST issues back. I had IZO error messages which fired-up an error report to be sent back to IZotope, but apart from an auto email response I've never had a follow up check on me.

Grazie

farss wrote on 10/10/2012, 1:54 AM
The problem *may* be that these are non realtime FXs.
I have noticed when working in Rx it does quite a bit of buffering which also indicates that some of them at least need to do a bit of to'ing and fro'ing to weave their magic.
For this reason alone I've never even tried to use them inside Vegas, it is just quicker to open a copy, do the work in Rx which is a better host anyway and then Save As back as a Take. Job done, and however much CPU / GPU work is involved its out of the way leaving the vegas engine room free to work on the video.

Bob.
Grazie wrote on 10/10/2012, 2:14 AM
When I use the DX versions of Izo and Ozone5 it's pretty darn slick and quick, could be that my PC is beefy?

No complaints on the DX within Vegas here.

Grazie

farss wrote on 10/10/2012, 3:34 AM
"could be that my PC is beefy"

That certainly helps. I used to take a big hit running Wave Hammer until I upgraded my hardware.

Still though, if you're having issues....

Plus it might depend on which Rx plugs we're talking about here. Doing the full noise reduction / spectral repair thing is very CPU intensive. I just cannot see the upside to trying to do all this in realtime inside Vegas. I go into Rx where I have all the plugs and all the tools to use them fully.

One of the reasons why Vegas doesn't have the same kind of forensic filters that Rx was well explained by the SoFo engineers ages ago, they are a massive CPU hog, the higher the Q of a filter the more iterations of the code is required. I really don't want my CPU bogged down doing that when I'm trying to edit video nor do I want to risk it when rendering.

Bob.
Laurence wrote on 10/10/2012, 7:58 AM
There are a couple audio things that I do on pretty much every project. One is cleaning up ambient room noise in interviews and voice overs. The other is a little overall compression and peak limiting on the master audio bus. I have started using Waves NS-1 instead of Sony or iZotope for getting rid of ambient room noise. It is easier (one fader), works well from within Vegas, and seems to be free of that weird phase shifting sound that you get with iZotope and Sony NR plugins. For the overall audio compression, iZotope Ozone is my go to master limiter.
dlion wrote on 10/10/2012, 12:55 PM
i still believe that something as cpu-intensive as noise reduction does not need to be done in real time or during a vegas render. i'd apply the fx and write it to a new track before rendering.