Projects using Ozone broken after upgrade to V5

LarryP wrote on 4/30/2004, 6:48 PM
Fix: Uninstall Ozone 2 and 3 and re-install Ozone 2 and 3.

I’m not sure if this is a Sony or Izotope issue.

Izotope decided, unwisely, to include the version as part of the plugin name. After I upgraded Izotope Ozone from 2 to 3, some time back, it showed up as “Ozone 2” in the fx chooser for backward “compatibility” according to Izotope. Their little charade was unmasked by the upgrade to V5 and I now see “Ozone 3” instead of “Ozone 2”. Vegas 5 (and Vegas 4) dutifully complain about the missing “Ozone 2” plugin and remove all references to it.

This probably means I’ve lost all the previous projects using Ozone which would take dozens of hours to re-create and probably not be the same. Does anyone know of a way to create an alias for Ozone 2 or any other tricks. I did try renaming “Ozone 3” to “Ozone 2” but that didn’t help. I can re-image my C: drive from an old image but that would be inconvenient to say the least.

Thanks. Larry


Comments

planders wrote on 5/1/2004, 7:00 PM
It's kind of funny, the Ozone 3 upgrade masking itself as Ozone 2 was done to avoid precisely this kind of problem. Too bad there's no way for Vegas to ask for an alternative plugin when it can't find the original one.

A feature suggestion, perhaps--even if it would be of fairly limited use?