window size bug on 2nd display in 16.01
- KVRAF
- 1583 posts since 26 Aug, 2019
I can provide more details, but there appears to be a bug with window sizing on a second display. This is on a Mac M1 under Big Sur. Steps to replicate. Open plugin on primary display. Drag to secondary. Close plugin window. Reopen and will open on secondary display but be sized very minimally. Drag over to primary display and it will "magically" resize to the proper sizing.
-
- KVRian
- 915 posts since 2 May, 2015
If the displays are identical and have the same aspect ratio/scaling/etc. then that is a problem. If not, try setting the displays to the same "etc." I sometimes run with three displays and the "above" can really be challenging, especially when working with video sources/etc...HTH.../s~
mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
- KVRAF
- Topic Starter
- 1583 posts since 26 Aug, 2019
The display are not the same resolution, nor can they be made to be so, as one is a laptop and the second is a connected HDMI monitor. I have been using mismatched dual monitors on mac systems for many many many years and this wack resizing issue does not pose any other plugins problems that I have so dramatically noticed ... and I take more plugins for a test drive than the average tire kicker. Thanks for the tip though. It might help explain past and future glitchiness. For now I'll just resort to dragging the malsized window to the primary display for a resize and then dragging back. Still a bug.steve2KVR wrote: Mon Oct 17, 2022 4:47 pm If the displays are identical and have the same aspect ratio/scaling/etc. then that is a problem. If not, try setting the displays to the same.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
This is a general macOS problem with systems with multiple displays with different DPI - every DAW reacts differently and on macOS the situation is a pure chaos. So we generally try to make it work on Logic and the other DAWs just have to get it work similarly. So for now we are dealing with each DAW at a time, some devs are willing to improve their stuff, others not really... well, it's a mess.
-
- KVRian
- 915 posts since 2 May, 2015
...fwiw...I use "Display Menu" to get things to work across multiple, dissimilar monitors and system configurations. Works quite well actually, from clamshell to total of four monitors...hth.../s~
mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
- KVRAF
- Topic Starter
- 1583 posts since 26 Aug, 2019
Steve, thanks for the suggestion. I already have too many menubar items to the point that I need a menubar item to manage the menubar items, so it wouldn't be my first choice. I might install and see what it gets me.
Vojtech, I went back and looked at your window behaviour in Studio One, Reaper and Kv Element on my display setup. Each of them behaves sub-optimally with Melda windows, but each in slightly different ways. I have not seen plugin windows from any other vendor showing the same. Given that your window management seems to be a function of your own code, and not the OS or the DAW, at the end of the day I would call it a bug in your code, albeit an edge case. Usability suffers but I can get by with my work-around. I do appreciate the explanation that it requires potentially a different fix for each DAW, and that it's not a priority for you.
Vojtech, I went back and looked at your window behaviour in Studio One, Reaper and Kv Element on my display setup. Each of them behaves sub-optimally with Melda windows, but each in slightly different ways. I have not seen plugin windows from any other vendor showing the same. Given that your window management seems to be a function of your own code, and not the OS or the DAW, at the end of the day I would call it a bug in your code, albeit an edge case. Usability suffers but I can get by with my work-around. I do appreciate the explanation that it requires potentially a different fix for each DAW, and that it's not a priority for you.
