I just purchased an Izotope bundle, particularly for Ozone 7 Advanced's Matching EQ function. My question is, can this work in Vegas as a plug-in? It shows up in Sound Forge but it doesn't show up in Vegas, at least on my machine. Thanks for all help!
I haven't got Ozone 7 but I do have Ozone 6 (standard) ... and it does show up in Vegas Pro 13's audio plug-in chooser.
I've only used Ozone 6 a few times in Vegas - it seems to slow things down and the audio doesn't always play all that well on the timeline on clips with Ozone 6 used. I tend to use it more as a stand-alone or in RX4.
If you've got Alloy 2 as part of the bundle, I've found that Alloy works quite well in VP13, but that of course is probably not going to give you EQ matching. I could be wrong, but I thought that EQ matching was a feature of RX4/5 Advanced rather than Ozone.
RX doesn't appear in VP's plug-in chooser. To get RX to work in Vegas, you need to make RX you're audio editor of choice in Preferences/Audio/Preferred audio editor.
It shows up quite well in Vegas. I have Izotope Ozone 7 and it plays very very well
with Sony Vegas, So double check that Vegas is pointing to the 64bit VST plugin
folder in the vst effects tab in Preferences.
Lagging during timeline playback is sometimes normal if your CPU is underpowered,
as Izotope Ozone is very CPU intensive, but Ozone 7 has improved dramatically in
this area.
As for all their other plugins, including RX, Shows up and interacts wonderfully with
Vegas. The only thing with RX now is, if you want to use the Spectral repair, you have
to go outside of Vegas and use the standalone.
OK, I've got a followup question now. I've got Ozone running as a plug-in. In my work flow I have the reference information for the Matching EQ on one track and the target file is on another track. My problem seems to stem from the two files being on different tracks (maybe, anyway). When I go to the reference track and capture the reference material it all looks good. When I go to the other track and open the plug-in there, the reference material is no longer there - so it's a dead end. Anyone have an inspiration?
Thank you Grazie and Steve for alerting me to the fact that RX4 plugins do work in Vegas. I finally realised that they were under the Steinberg folder in Program Files after I reinstalled RX4 and saw the destination folder during the install. Now I get the RX4 plugins in Vegas that you've got showing in your plugin chooser, Grazie.
And thanks for the RX Connect recommendation - I'll give that a try. I must admit that I much prefer to keep the Preferred Audio Editor in Vegas linked to Sound Forge as I then get the ongoing link in SF to SpectraLayers.
Yes, Vegas (and SF) need to be pointed to the correct folder for many VST plugs, which when installed create their own folder.I've encountered this for many plugs. Fortunately this only needs to be done once OTOH, the VST plug's .<.dll> file could be moved or copied to your desired VST folder. This could affect stand-alone operation with some though.
Yes, that's it, a corrective EQ based on a good track, applied to a "bad" track. I heard from Ozone support today that I can't actually create a source profile from one track and apply it to another track - it must be on the same track. And, though I haven't tried it yet, I am also now assuming that each event on the same track is probably mutually exclusive, as well.
Well, it took a couple of weeks, but a perceptive young visitor at my house who is rabidly interested in audio/video editing tackled my Vegas/Ozone plug-in puzzle with me and we figured a way to grab a reference EQ from one clip and make it available to another clip in Vegas. It's pretty simple, it turns out:
Add Ozone as a plug-in on the reference clip and capture the reference audio. Then, name and save this reference-only information as a preset in Ozone. (BTW, in my case at least, I had to run Vegas as Administrator in order to save presets in Ozone.)
Next, go to the target clip, add Ozone as a plug-in there, load your new reference preset, continue Ozone's procedure of capturing the target audio and then adjust to your heart's content. Duh, how easy is that?! Finally, I went back to the original reference clip and removed the unneeded Ozone plug-in there.
My project is moving ahead full speed again and I am very pleased with the results!
Hey Doug, do you have Alloy, too? It's probably the better tool for this, as it is meant for mixing and real-time playback. Ozone is a mastering tool that, especially when multiple instances are used, can quickly bog down a CPU during timeline playback. 'Pologies if you know this already...