A 14" 4K laptop and a 65" 4K TV have the same number of pixels, but the greatest distance that your eyes require to resolve a certain object on a 14" 4K display is less than the distance required to resolve the same object on the 65" 4K display. This means that two displays of equal resolution but different PPI happens any display size require the same field of view. This is not my opinion, it's geometry. The only difference is that, with a smaller display, our eyes need to converge more because the focus is on a close object, which some people may find fatiguing. If you have high visual acuity, you will be able to put your display further from your eyes which will give you a narrower field of view, and therefore you'll require less head and eye movement than someone whose visual acuity requires the monitor to sit closer to them.T-CM11 wrote: Sun Aug 29, 2021 4:52 pmHead and eye movement are relative to size (and distance), not the amount of pixels. e.g. A 14 inch 4K laptop has the same amount of pixels as a 65 inch 4K TV.
Put another way, for a fixed PPI, a display that has more pixels across will obviously require more left-right head movement. You could push the display back away from you to reduce the extent of head movement, but the projection of the pixels on your retina will become smaller, and therefore your eyes may not be able to resolve some objects.
Assuming your eyes are equally capable to focusing on near and far objects, near-and-small and far-and-big would produce effectively the same viewing experience, because the projection of the screen on your retina would occupy the same retina space, if that makes sense.
If I wasn't 100% ITB I'd just have a large monitor hung on the front wall or on a trolley for flexility, and display scaling set to something like 150% so I could see it from other parts of the studio.T-CM11 wrote: Sun Aug 29, 2021 4:52 pmALL aspects (resolution/size/distance/panel type) are important, depending on the use case. You're thinking too much of your own situation. Not everybody is a 100% ITB sit-at-desk user.
Your viewing distance of 40cm for a 27" 2560x1440 display sounds about right. For that monitor my viewing distance would be 45 cm, so it's similar to yours. Of all currently commercially available resolutions, 2560x1440 strikes the best balance of screen real estate and viewing comfort (narrow field of view and long viewing distance at 100% scaling). At the same PPI as your monitor, a 4K display would still be 40 cm from your yes, but your head and eyes would be moving a lot further to reach the display edges.T-CM11 wrote: Sun Aug 29, 2021 4:52 pmFor my other PC (general usage / also music production / no audio hardware / desk-based), I find my 27" 2560x1440 (40 cm viewing distance) to be perfect. The PPI is on the high side, but older, non-resizable plugins are still usable.
I've tried bigger screens and multi-display setups and I'm not convinced having everything visible simultaneously is necessarily beneficial, since my eyes can only focus on a relatively small area of the screen at a time. I still have to rely on short-term memory to retain and compare information. I do have a custom AutoHotkey script that enables me to do things like toggling a window always-on-top property (left-click+T) and to perform editing operations such as copy, cut, paste, clipboard swapping and delete with mouse and left-hand keys combinations (the mouse buttons function as modifier keys). I also use a script to launch a rather nifty screen capture app which I have bound to a keyboard shortcut (left-click+Backspace, and my backspace key is Caps Lock on my Ergodox EZ keyboard). This largely reduces the need for more display real estate as the window will stay on top regardless of focus, which is similar to having a secondary display. All this is just thinking outside the box to improve my workflow. Getting a massive screen is the brute-force approach.
PS: The Chinese screen show on the video works extremely well. The only snag is that the UI is in Chinese... I just ignore the Chinese characters and remember what the buttons do, but I'm sure there's an equivalent English alternative.
