![]() Then they pop open their other favorite audio editing tool and all the plugins look fine on the same system and monitor. ![]() Increasingly, collaborators are complaining that WaveLab doesn’t render plugins at a readable size, which is annoying and a slowdown. Please note that this request is being written from the perspective of a longtime fan and supporter of WaveLab who has pushed studios and collaborators to switch to WaveLab because of its excellent capabilities. This has been tested across a variety of systems and monitors and the consistent issue is with WaveLab’s rendering of the Thank you for taking the time to review this request - much appreciated! The settings you mention are indeed preferred however, many plugins simply render too small on 4K/8K screens with these settings. Cantabile even has a program option: “Hi-DPI User Interface: Enabled & Upscale Plugins.” So it seems it can be Thank you for the thoughtful suggestion. ![]() The PatchWork, inTone and Cantabile application UIs themselves remains sharp at all zoom levels, and almost all plugins render at a readable, usable size. (I should note: As a few examples, Blue Cat Audio, Audified and Topten Software each seem to have solved this issue with their PatchWork, inTone and Cantabile VST hosting tools, respectively. ![]() Would it be possible to create a solution where plugins can be optionally rendered like the System (Enhanced) high-DPI override, while the WaveLab UI itself remains scaled with default settings? The current workaround of editing executable properties fixes the plugin size issue at the expense of overall UI you have brilliantly solved issues like this in the past. Ideally, the WaveLab UI would remain crisp and sharp as it is with default settings, while supporting the rendering of all plugins at large, usable sizes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |