fury wrote:I work for a manufacturer (automotive supplier) and we're just getting started with displays. So, maybe I'm jumping in the deep end before I learn to swim. I just know from my experience in using high refresh rate displays, it makes a big difference in how responsive and smooth the system feels
It certainly does!
And even 120Hz is not the final frontier either, as seen in
1000Hz Journey -- if future Hz becomes cheap, it will get milked by future manufacturers. (Much like for formerly-expensive 4K becoming cheap today)
fury wrote:If a TCON can do 60hz at 1920x1080, would it be able to do 120hz at, say, 800x480-960x540 without modification, or is that not how those things work?
Not exactly, and answering that question often required paid training, engineering books, or even deeper research.
While lower rez can sometimes makes higher Hz easier, there are other complications (e.g. scaler electronics malfunctioning at higher refresh rates, eliminating your ability to do scaled resolutions like those) and since you have to replace all those chips anyway, might as well try to do full 120Hz at native. Be prepared to work with FPGA chips if you need high-Hz at high-rez, though I know the Razer phone manages to avoid that.
Since Blur Busters (not just a media site) is also now in the business of helping manufacturers boldly venture where they have not ventured... I may be able to network around a little bit for you (e.g. try to reach out to some of my industry contacts willing to do 120Hz small-screen displays). Email me at
[email protected]
fury wrote:I did explore the idea of using the iPad Pro as an external display - what ended up working best there is a native UI running on the iPad sending control messages back to the target; anything else had too much latency and defeated the purpose of the 120 Hz (at least for me). I probably can't fit an iPad into this anyway. The prototype might end up in a double DIN chassis so I can stick it in my car, so either 7" or smaller, or the display sits outside of the front panel
If you're reluctant to learn the advanced engineering of TCONs (or wait for 120Hz to be a widespread generic standard), this is your chief "easy" engineering option: Use Razer as the display.
Yes, the display itself being the computer, is a possible workaround. Consider that the 120 Hz Razer are already fairly powerful, so you could potentially do that too, using the USB port (it can run as a USB host, I believe) as your communication method. Disable all radios, and even use your own slimmed-down Android build, and treat the Razer like a tiny 120Hz computer screen -- at least during the prototyping or experimentation stage.
Consider that the Razer Phone 2 has a more powerful chip than many iPads. It has a 2.8 gigahertz Snapdragon 845 processor which is an 8-core ARM processor with 4 high-performance core and 4 power-efficient cores. By all standards, that's quite a powerful microprocessor already, because Razer is a 3D video gaming smartphone that must crank its Android games at 120 frames per second at 2560x1440 -- which it manages to successfully pull off in certain games. That's damn impressive, considering all the pixels at all that frame rate. All that computing horsepower is all already built bona-fide in the Razer 2 phone -- so it could simply run what you need. Just get rid some of the Android bloat (thankfully, Razers are usually often fairly lightweight stock Android installs by default)
Even its GPU can be commandeered to do basic natural learning and artificial intelligence tasks, being it one of the most powerful moble GPUs on the market even running circles around 10-year-old desktop GPUs. All things considered, that phone has more computing power than the computer that generated the original Toy Story movie in 1995. The problem is it heats up a bit, and then it automatically thermally throttles after a while. It uses a vapor cooling mechanism to help out, but tacking-on some additional add-on cooling (a simple engineering problem for you, hopefully) on the phone's back will help keep it from thermal-throttling too much -- allowing more continuous computation.
Now, this is not necessarily practical for retail units, but would potentially be fine if the phone had enough computing power to be the built-in-computer for your needs. Unless you're needing to use one of those ultra-powerful self-driving-car processors.
But you could even communicate between the two computers using the USB port too, like a networked supercomputer, with two applications co-operating with each other.
You could even use 3D-geometry-over-wire too, simply using the phone as a texture cache & 3D renderer. I don't know how much bandwidth of data you need but if it fits in the USB budget, the Razer 2 is fast enough to display stuff at latencies of mere milliseconds. You might have a problem if you're trying to display multiple video windows at once, then you're going to need to become very creative with that.
Since selfdriving cars are a booming tech.... Let's say you're working for one of them, working on a better/faster LIDAR+RADAR merged display. You could just invent your own streaming protocol for whatever data (e.g. aggregated realtime lidar data) treating the Razer as as a realtime drawing device; just sending batches of geometry data to the "phoneputer" which then draws in realtime in low latency. Being it originally a game phone, it has had to gain one of the most powerful smartphone processors.
Unless... You'd like to study display engineering instead?
I can help with certain elements of the display chain -- depending on the direction your company goes in.