If I delete the Wavelab 8 preferences and relaunch, I still get the GUI error now. It seems to be hard to go back now…
I’m not sure if it was copying the WL or Ozone preferecnes back to my new OS that caused it. I noticed that Wavelab seems to add preference files to the root preferences folder when launching, so at this point there is a mess of possible corrupt preferences that could be the cause.
I will also contant Izotope to see how to cleanse my system of all Ozone preferneces to see if that is the cause.
If there are ANY preference file you can think of to delete, please let me know.
It’s so strange that it worked at first, but once I copied the WL8 and/or Ozone preferences, this bug came back.
I asked you the question, because I think the problem is not a preference issue. That must have been a coincidence. As you said, this is random sometimes.
Do you run on a new computer, or your just reinstalled OSX?
Is there a Wavelab uninstall tool that will cleanse my OS of any Wavelab related files?
I’d like to do this for both Wavelab and Ozone and start over without having to start over with the entire OS. I have a strong feeling that pasting some Ozone presets from my old system to the new one is what caused the bug to return. It may have been pasting the Wavelab preferences but I believe I tested after pasting Wavelab preferences and it was OK, and that it was the Ozone presets that caused the bug to return.
I tried deleting Wavelab 8 prefs and any Ozone presets or prefs I could find but the bug seems permanent now.
This is just driving me crazy, especially since I tested it after completely reinstalling everything on a new drive, and doing a test after getting Wavelab and Ozone installed and having the problem fixed with the default basic settings. It wasn’t until I started copying some settings/prefs/presets from my old system that the bug returned.
Ok. So I was able to resolve the issue again by deleting the Wavelab app and prefs folder, and all instanes of Ozone 5 presets and plugin versions that I could find.
I guess I will first add my WL8 prefernces folder back and see how it works.
My Ozone presets are not as important, but I have a few years of shortcuts and Wavelab settings that I don’t want to redo if I don’t have to.
I’ll report back if the problem comes back from something in the Wavelab prefs file.
I tested for 15 minutes using various plugins on the same plugin chain window with no more Ozone 5 blank GUI issues when going between plugins in a shared window after a new install of WL8 and Ozone 5.
As soon as I pasted the Wavelab 8 prefs folder back with my old settings, the issue came back.
Now what is interesting is if I make new sessions and don’t recall any saved chains, I don’t get the Ozone issue…but if I open previous sessions with Ozone 5 in a shared plugin window/chain I do get that blank GUI issue.
I’m not sure what the exact issue is but I hope I can at least move forward now with no issue. It really seems to be something in that WL8 prefs folder that causes this problem.
Now for a smaller issue. Ozone preset menu looks different and says something about banks instead of save preset as…
I’ll attach two screenshots. The one of the Waves EQ is how Ozone present menu was before, but now it appears as shown on the Ozone screen shot. The old way is preferred.
Your 1st picture is a VST-3 plugin.
Your 2nd picture is a VST-2 plugin.
Apart this, removing this pref file alone: WaveLab 8/Preferences/General.dat
will not touch your shortcuts, but could solve your problem, if you think it’s a pref problem.
Because of how Wavelab 8 is organizing my plugins now, it’s not easy to tell what are VST-2 or VST-3. It seems that after my re-install, Wavelab was using VST-2 Ozone 5 as a default by accident. I am just now realizing the 3 little marks by a plugin to indicate VST-3.
After testing VST-3 Ozone 5, the problem is back again.
So now I don’t know what to do. Is it bad to use the VST-2 of Ozone?
I also prefer to run VST-3 for best optimization. So UAD is still VST-2?
I will try deleting and reinstalling one more time and make sure I’m using VST-3 to test. After that, I give up, must be a Mac Pro specific problem.
To try and reproduce this problem, are you loading 2 plugins in a shared window (Waves REQ and Ozone 5 VST-3 for example)…and then toggling between the two? If Ozone is the only plugin in a chain or window, the issue doesn’t occur.
After completely uninstalling all instances of Ozone 5 and Wavelab 8 and reinstalling, I still get the error with VST-3 version of Ozone 5. VST-2 version doesn’t have the issue.
The issue occurs even with the default WL8 preferences so I don’t know what else it could be other than a bug between the two pieces of software, maybe specific to Mac Pro and the video card, but surely I’m not the only person using a Mac Pro.
Also, I don’t know if this is related at all, but on Windows 7, if you have Ozone in the plugin chain window, and you turn down the Opacity in the Ozone Options graphic section, it will turn down the opacity of any other plugins in the chain. Does that seem right?
Interesting. Seems to be the same problem. Though I could never reproduce it myself.
Also, I don’t know if this is related at all, but on Windows 7, if you have Ozone in the plugin chain window, and you turn down the Opacity in the Ozone Options graphic section, it will turn down the opacity of any other plugins in the chain. Does that seem right?
That’s another thing, and this is normal to me. In fact, when a plugin is not displayed in the chain window, its UI is simply not existing (it is not “hidden”). The UI is recreated when switching to a new tab.
Yes, can you try the steps to reproduce carefully again? I was wrong when I reported that the issue is only on Mac Pro but not on MacBook Pro. I was accidentally using VST-2 versions of Ozone on the MacBook Pro rather than VST-3 where the issue occurs. The problem seems to occur on all my Macs when I use VST-3.
I am on OSX 10.8.4 but it’s been happening for some time now so probably happens on 10.8 in general (if not more earlier versions).
Can you please try this?: Insert any plugin on the montage master (I just tested with Steinberg Studio EQ), then using the shared plugin window, add Ozone 5 vst-3 after the Studio EQ. Switch between the two plugins and you will probably find that the Ozone GUI is transparent when you go back to Ozone 5. I have to fold and unfold the plugin window to get the GUI to appear proper.
I also get similar results when using RX3 by iZotope. The GUI is OK if it’s the only plugin inserted, but using the shared plugin window with any other plugins causes this issue.
I noticed all your posts back to July say Ozone 5.04. If it’s the same or similar problem, they say to switch back to version 5.03 to solve the problem. They don’t specifically mention RX, but their other programs are listed so wouldn’t be surprised if RX was just not noticed.
