MacOS 9 had contextual menus.
That's all well and good if you only do audio work or if you never do video work at higher resolutions - if you are only targeting 1080i/p resolutions or are simply viewing the video in order to produce the audio then have fun.BONES wrote: ↑Tue Jun 02, 2020 1:51 amafter trialling dual 4k screens for 6 months, giving most of the 20-odd artists in the department the opportunity to work on them, we unanimously decided to go with dual 2k screens instead. Everything runs at native res, we don't have to worry about Hi-DPi support or any of that bullshit, and we get much more grunt from our graphics cards than we were with the 4k screens. So it' s completely thinkable that professional software like Cubase have development priorities other than providing screen scaling
I happen to do both video and audio editing. While my primary computer does not currently have retina (hi-dpi) displays, I will eventually need to start switching to those to support working on video footage intended to be delivered at higher resolutions. If the audio software can't handle that well, I will need to choose different audio software.
Note this does not really mean the audio software needs to actually leverage the higher resolution: it doesn't really matter to me if it thinks it is on a 4K display or a 2K display as long as it works smoothly alongside the video software that will need to leverage the extra resolution.
However, any performance benefit of having the software think it is running at 2K resolution when it is actually on a 4K display is likely to be negligible at best. If it is running on a 4K display then it may as well take advantage of it where possible.