#PUREBASIC DISPLAY PICTURE FULL SCREEN DRIVERS#
#PUREBASIC DISPLAY PICTURE FULL SCREEN DRIVER#
#PUREBASIC DISPLAY PICTURE FULL SCREEN MANUAL#
#PUREBASIC DISPLAY PICTURE FULL SCREEN FULL#

Running 1920X2160 side-by-side with two separate monitor inputs seemed (to me, at least) to be a standard use case for a 4K monitor that's capable of handling more than one input at a time. It nagged at me that this wasn't something that manufacturers had already solved. We even conducted an over-the-phone session to ensure we were apples-to-apples on the settings and output. All of their suggestions simply re-iterated through the combinations of settings I had already tried, to no positive result. And while this team was more polite, the initial response wasn't all that helpful. So I sent a message to the second manufacturer's tech support group.

#PUREBASIC DISPLAY PICTURE FULL SCREEN FULL#

While running full screen the images scaled to the full height of the display area, there was still letter-boxing occurring. However the second PBP result was not much better than the first. The second monitor was lighter, used less power, was practically immune to screen burn and was nearly $100 cheaper than my first choice. At least the product return process worked perfectly, so that feature was fully implemented. At that moment I realized I had not bought a monitor.

#PUREBASIC DISPLAY PICTURE FULL SCREEN MANUAL#

So, in effect the customer has to use their psychic powers to know that 10-pages deep into the manual there's a proviso which says that full screen PBP is not possible. Please make sure you are running HDMI 2.0 turn to page 10 in the user manual, PBP will have bars on the top and bottom. I contacted the manufacturers technical support team and in few days I received a rather curt response. I tried all combinations of display properties, from 1:1 to full width, and nothing made any difference. Needless to say this is not at all what I was expecting.

Here's a photo of the first 4K monitor I bought, with the initial attempt at PBP shown below. So the use case is fairly simple and straight-forward, or so I thought. In fact, one of my early use cases was to set up my personal machine for various machine learning benchmark exercises (in Windows 10 and Ubuntu) while the work notebook handled general office and light-lift development duties. The work I'm planning focuses more on using my system GPU for small-scale TensorFlow experiments. I'm not looking to frag virtual enemies at 120fps. While researching I quickly set aside the idea of an ultra-wide curved monitor. I also wanted it to handle more than one input simultaneously, so I can work across multiple systems. So when I moved to remote work full-time, I looked for a purpose-built 4K monitor. It is an earlier generation 4K TV and simply wasn't designed for at-arms-length viewing. Eventually I started using it more generally, but for detailed coding work it created too much eye strain. Mostly it served as a proxy for a white board during group working sessions with video feeds and slide/board presentations. This journey started with my 55 inch 4K TV, which was occasionally pressed into service while working from home. So consider this in context if you're thinking about running multiple systems into a single display.

#PUREBASIC DISPLAY PICTURE FULL SCREEN DRIVER#

While it's tempting to call out certain vendors, the half-life of driver implementations (and generations of monitor hardware technology) is so short that this article might be out of date by the time you read it.

#PUREBASIC DISPLAY PICTURE FULL SCREEN DRIVERS#

But not all PBP designs and not all monitor drivers are equal. Just the acronym is all that's needed to sell the concept. Picture by Picture (PBP) is a feature so common you'll scarcely see it in long form in the description. Use a 4K monitor to run multiple computer screens simultaneously.

Purebasic display picture full screen