Which Window Manager and Operating System is that?
I’m not able to reproduce this using regular Windows 10.
Also suspect in the screenshot you posted is that the Listbox dropdown
is showing the pre-set un-flppped, im sure its the same type of Widget
the rest of the GUI uses… probably TCL a derivitive… so it may be a clue.
Yep, both the Waves Central and oVox are up to date according to Waves Central.
Wonder if it is related to the ‘big sur’, idk… does it happen if you open oVox outside of Renoise?
Still bugs me that only some GUI Widgets are upside down.
What occurrs to me is, since most “Canvas” widgets, like
Zinc for example, utilize OpenGL to provide transparency
and other features, wonder if un&re-installing or updatng
OpenGL could provide some relief.
Upon delving deeper into the issue: it is probably due to the Core Graphics coordinate system. If the programmers would check which coordinate system is being used for handeling the drawing, the output can be put right for all hosts.
Probable culprit may be the use of direct Core Graphics calls (which yield far greater power over graphics) in stead of UI graphics calls (which compensate for any coordinate system mixup).
@taktik: Could there be a possible workaround on the Renoise side to enable Waves plugins to display a proper GUI on macOS? I’m having the same issue with 3.3.1 and Waves 12.7 on macOS Big Sur 11.2.3 as shown in this image.
FYI, and I won’t repeat over and over any further info here anymore: Waves “fancy” waveshells can load the same plugin thru different waveshell versions. So it might be the case that your flipped plugin was loaded thru the wrong waveshell version. This is due the way Renoise special-case handles the waveshells (other DAWs might handle this in a smarter way). So the steps to try would be:
Check your waveshells in your vst dir, remove everything old. Normally you only need waveshells from one and the same version and filedate.
But first close Renoise, remove ALL waveshells from VST dir. Start Renoise and do a vst scan (if you do that manually). All waves should be removed from list.
Now close Renoise again. Add only the proper waveshells back to the vst dir. Start Renoise, do a scan.
If that did not work, try the other waveshell instead, if there was any other waveshell version, and repeat the steps above.
PS: And step 0: First completely remove all waveshells from audiounit dir and restart macos.
Another one running into this problem here - I accidentally made the mistake of updating to Waves V12.7 and trying the VST2 plugins, oops.
I can add that it’s not just a Big Sur problem - it’s happening in Renoise 3.3.2 on High Sierra 10.13.6 on a MBP2012 as well. (That said, I’ve not yet tried ffx’s suggested full uninstall trick.)
I’m pretty sure it’s a Waves problem, because every other plugin works with Renoise… but Waves have confirmed they won’t fix it as Renoise is not officially supported. The last hope is if taktik can somehow find a way to patch around it.
I somehow wrote an appeal to those waves support and the answer was: we do not support renoise, so if you want you can install the old version of the installer.