Vocalpoint, you seem a little aggressive and dictatorial.
4K monitors first came into use around 2013, and have been widely used by the public since 2016. (There is evidence for this even in these very Steinberg forums.) 4K monitors are not bleeding edge and are in fact quite common.
Philippe himself uses two 4K monitors in his primary configuration:
• 32 inches / 3840 x 2160 (150% scaling)
• 30 inches / 3840 x 2160 (200% scaling)
• 32 inches / 2560 x 1440 (100% scaling)
Almost all software does scale correctly and usably on a 4K monitor. Have you tried a high-resolution monitor? Even WaveLab itself does scale correctly and usably on a 4K monitor. The request is simply to help plugins which do not scale nicely in WaveLab, in a manner similar to how other tools (Cantabile, PatchWork, Audacity, et al as shown above) gracefully scale the same plugins.
The actual benefit can only occur when ALL software in use is written specifically for that resolution (and scales with 100% accuracy) in order to take full advantage of that space.
This statement is simply not true and does not follow logic.
Studios will simply configure hardware and software for maximum capability, reliability and usability. When a tool creates a speedbump, a studio will often resort to other tools that don’t create the same speedbump. If a studio has committed time and resources to configurations and workflows that include 4K monitors, then often WaveLab is going to create a speedbump when 3rd-party plugins are involved. This request is to remove a speedbump that prevents users with 4K monitors from simultaneously enjoying crisp UI and readability of all plugins in WaveLab.