We’ve spent a lot of time in the past couple of days talking about generational improvements and interfaces, but the main selling features of the ArcticLink III VX will remain our Visual Enhancement Engine High Definition Plus (VEE HD+) and Display Power Optimizer High Definition Plus (DPO HD+).

Those familiar with our products know the advantages of VEE and DPO.  This is how we improved them in the ArcticLink III VX (ALIII).

Resolution and Speed Support

The limiting factor of VEE in the current ArcticLink II VX (ALII) is its resolution support, which is 1366 x 768 at 60 FPS (frames per second).  We’ve advanced the support to 1920 x 1200 @ 60 FPS on the ALIII.  Being able to support resolutions 2.2X greater on the ALIII gives us the ability to address future designs.

For those applications which don’t require such high resolutions, we do offer different devices which support lower speeds.  To be clear: these are NOT speed-graded devices.  Rather, they are designed with specific architectures that only support certain resolutions.  For instance, the VX3B2B (MIPI -> MIPI) supports only up to 1366 x 768 through its MIPI 2-lane architecture, where it’s big brother, the VX3B3B supports 1920 x 1200 through its MIPI 4-lane architecture.  Speed in both these cases is limited directly by the number of MIPI lanes.  The same holds true for other MIPI devices, as well as RGB and LVDS devices within the product family.

Intelligent Brightness Control

In the ALII, DPO 1.0 was in the hard-coded logic, whereas DPO 2.0 technology, featuring Intelligent Brightness Control (IBC), was an option that we would load into the fabric during production.  In the ALIII, we went ahead and hard-coded DPO 2.0.  Any customer using the ALIII can take advantage of IBC’s content-based power savings features.

Streamlining of Technology

VEE is a very complex technology, and as such has a lot of smaller components to it.   When we first set out to design VEE HD+, we looked at each of these and decided what could be combined, reduced, or eliminated.  This allowed us to make VEE HD+ in the most space-efficient manner as possible without changing how it’s implemented in a system, or the performance.  This is very important, and I cannot repeat this enough – we have not changed how VEE HD+ and DPO HD+ are implemented in a system, and the visual and power savings results should be just as impressive as before.