Direct Display Profiling

Using the in-built LightSpace CMS patch generator

Using the in-built LightSpace CMS patch generator is one of the easiest way to perform accurate display calibration, and negates the need for separate signal generator hardware.

Calibration Client

LightSpace Direct Profiling

When LightSpace CMS is installed a sperate Java Application (called 'Calibration Client') is installed along with the main software, and can be seen within the main 'Programs' menu.

This application can be copied and loaded into any other system (PC/Mac/Linux) running Java to enable calibration of displays over a facility wide network.

This means that with LightSpace CMS running on PC, with probe attached, the patches can be displayed on any display connected to any other PC/Mac/Linux system on the same network.

In the above diagram LightSpace CMS is running on the laptop, with the Java App running on the Mac, connected to the LightSpace laptop via Ethernet. When LightSpace generates a patch colour the same colour is replicated on the Mac via the Java App, and the probe records the measured value and sends it to LightSpace CMS.

Calibration Client Java App

The Calibration Client can be seen in the 'Installed programs' list within the LightSpace PC. To copy it to any other PC/Mac/Linux system simply navigate to the LightSpace CMS installation folder and copy the 'CalibrationClient.jar' from within the 'Calibration Client' folder, if installing on a MAc or Linux system.

If installing on another Windows PC system it is easier to install the Free ZRO version of LightSpace, and access the Calibration Client from the install program link.

Using the Java App, any display connected to any PC/Mac/Linux system can be directly profiled from the LightSpace laptop with no additional hardware, using the 'Network Manager' to connect over an Ethernet network to the Calibration Client Java application, and control patch size and position. For more information see the Network Interface section of the LightSpace CMS Profiling User Manual.

Note: a double click on the Java App window will make the patch generator full screen, and remove the window border.

Patch Indent/Size & Extra Delay

LightSpace Connect Network

The Patch Indent/Size & Extra Delay controls within the LightSpace Network Manager can be used to set any specific patch size and position for display profiling, as well as a delay for probe measurement.

The 'Diagonal' box enables the selection of patches based on the ICDM Lxx sizes, which are defined as a percentage of the screen diagonal size. The 'Area' box shows the equivalent screen area percentage for the selected patch. It is possible to enter the desired area percentage manually.

The 4 indent values are also in percentage terms, and can be used to set a Custom width and height of the patch window, as well as the position.

To reposition the patch you simply add/subtract the same value from the apposing percentage boxes, which will reposition the patch, while maintaining the same patch size.

The 'Extra Delay Time' setting is a duplicate of the same setting with the 'Options' menu, as allows for a delay time in seconds to be set before the probe starts reading after a patch change has occurred. This is required when using an external patch generator (such as LightSpace Connect) with an in-built delay, meaning the patches on the display being profiled occur out of sync (delayed) with respect to the patch changes within LightSpace. Such a delay is easy to see visually, and a corresponding value entered to counter the visual delay.

Extra Delay

Note: If using an external patch generator that has no understanding of patch size and/or background colour, set the Indent/Size controls to 0%, and keep the Background Colour set to the default black.

Note: The Network Manager can be accessed during a Display Characterisation, enabling the patch size, position, and BG colour to be adjusted during profiling. Depending on the patch generation system being used, it may be preferable to use the 'Pause' button within the Calibration Status window, to pause the profiling before making such adjustments.

madTPG - Test Patch Generator

madTPG Calibration

Yet another option for remote network based calibration is to use the Test Patch Generator built in to madVR, which is a free Home Cinema player and can be download from

When installed, madVR installs a separate executable program called madTPG.exe, which can be run as a standalone Test Patch Generator, and controlled directly via LightSpace CMS.

For operational information see the madVR User Guide page.

Screen Mirroring

Miracast Profiling

One further option that can be used on modern home TVs is to use Miracast to mirror you PC desktop directly on your TV. If your TV doesn't have Miracast built-in an adaptor can be used.

Note: The one potential issue with a direct wifi connection is that it bypasses the hardware HDMI input on the TV, and may not be a faithful representation of the TV's response to signals via the HDMI port. But, it is very simple to verify this by comparing to a direct HDMI connection from the LightSpace CMS PC.

HDR10 Calibration

HDR Metadata

PQ based HDR displays use metadata within the signal to trigger the display's HDR capabilities. So, if the HDR display to be calibrated cannot be set to HDR mode manually a method for metadata insertion into the HDMI signal path is required.

The HDfury Integral4K60 can be added to the HDMI signal path from the LightSpace CMS laptop to the HDR UHDTV, injecting the required metadata.

If the HDR display can be set manually to HDR mode no metadata within the HDMI stream will be required.

HDFury HDR10 Metadata

Using the HDFury GUI add the required custom HDR10 Metadata.
(Always tick the REC.2020 flag)

  • Custom Metadata (P3 Primaries, 0.005 Black / 1000 nits Peak / 1000 MaxCLL / 400 MaxFALL): 87:01:1a:74:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80 :3e:13:3d:42:40:e8:03:32:00:e8:03:90:01
  • Custom Metadata (P3 Primaries, 0.005 Black / 4000 nits Peak / 1000 MaxCLL / 400 MaxFALL): 87:01:1a:b0:02:00:c2:33:c4:86:4c:1d:b8:0b:d0:84:80 :3e:13:3d:42:40:a0:0f:32:00:e8:03:90:01

And set the required custom AVI InfoFrame.
For For PC/Laptop with HDMI 1.x and PGenerator, set output RGB-Data and patch scale 16-235 while for AccuPel and DVDO AVLab set RGB-Video output with no patch scale.

  • 82:02:0D:AE:00:E8:64:10:00:00:00 for 1080p60 RGB
  • 82:02:0D:AE:00:E8:64:20:00:00:00 for 1080p24 RGB

For DVDO AVLab, as an additional option RGB-Video 2160p24 8bit output can be used

  • 82:02:0D:AE:00:E8:64:5D:00:00:00 for 2160p24 RGB

For PC/laptop with HDMI 2.0 output, RGB-Data and patch scale 16-235 can be used

  • 82:02:0D:AE:00:E8:64:51:00:00:00 for 2160p60 RGB

Direct HDMI Profiling

Direct HDMI

There is a lot of confusion regarding the direct use of a PC's HDMI output as a patch generator, mainly related to historic issues with old graphics cards and chip-sets.

The reality is that modern Nvidia graphics cards and Intel HD Graphics chip-sets have very accurate output signals, and can be used for extremely accurate patch generation and hence display profiling and calibration, if the VCGT is correctly nullified using SpaceMatch DCM.

Note: the standard Windows API/reset call for the VCGT doesn't generate a true Null setting, as explained within the SpaceMatch DCM page.
Additionally, AMD/ATI graphics cards have proven to not be transparent, and are therefore not recommended for direct patch generation and profiling.

A direct HDMI connection from the LightSpace CMS PC can therefore be the one of the best options for accurate display profiling, with the VCGT issue managed correctly, and the correct graphics card/graphics chip set used.

PC Configuration

When using direct HDMI (or DVI/DisplayPort) output for patch generation there are a number of primary considerations that must be kept in mind.

ICC Profiles
A major potential issue with HDMI output is the use of ICC profile within the PC for internal calibration. Such ICC profiles will distort the HDMI output, making any attempt to use the output signal for profiling and calibration totally inaccurate.

Graphics Card Settings
As with ICC profiles, any inaccurate set-up of the graphics card settings will also distort the output HDMI signal.

Extended display identification data (EDID) is a data structure provided by displays to describe their capabilities to a graphics card. It is this that enables the graphics card to know the correct signal information to send to the display.

DDC-CI stands for Display Data Channel Command Interface, and is a collection of protocols for communication between a display and a graphics card that enable the PC to adjust display parameters, such as brightness and contrast.

Monitor Command Control Set, or MCCS, defines the protocol for controlling the properties of a display from a PC, or set-top box, etc., often using DDC-CI for communication.

PC Desktop Set-up

To use a PC (normally a Laptop) for display profiling via its HDMI output, first connect the display to calibrated to the HDMI output, set the desktop to 'Extended' mode (not 'Clone' mode), and re-start the PC, so the display is correctly identified.

Extended Desktop

The above shows the standard Intel HD Graphic configuration for Extended Desktop, with the Second Display as the display to be profiled.

With any graphics card ensure you select the correct display to configure - usually the external HDMI connected display.

Select Monitor

With the PC now connected to the display to be profiled set the PC desktop background to 'black', so when displaying the profiling patches the background is not intrusive, or potentially changing the profiling results, as with plasmas ABL.

Extended Black Desktop

Extended Desktop, with the left hand side being the LightSpace Laptop, and the right hand side the display being profiled.

ICC Profile and VCGT Management

ICC Profiles can be managed manually, if you know what you are doing. If you are unsure SpaceMatch DCM can be used to verify the status of any active ICC profile and the graphics card's VCGT, and can re-set any found active to Null, as is needed for accurate HDMI output.

Using a true Null LUT to replace the VCGT data is critical, as outlined above.

SpaceMatch DCM

The above shows an active ICC profile as reported via SpaceMatch DCM. This needs to be re-set to a Null profile before the HDMI output can be used for display profiling, which SpaceMatch DCM can do using a true Null LUT generated via LightSpace CMS.

Graphics Card Setup

The PC graphics card, or graphics chip-set, needs to be set to standard default settings, as any setting changes will again distort the HDMI output.

Graphics Card Settings

The above shows the Null settings for an Nvidia graphics card, with all settings set to their default values, and the below the same for the Intel HD Graphics chip-set.
(Note: the VCGT must be set to a true Null status via the user of SpaceMatch DCM and a true Null 3D LUT.(

Graphics Card Settings

The above Graphics Card controls can use DDC-IC / MCCS commands and protocols to directly adjust the display where applicable, or directly adjust the graphics card output. For accurate calibration it is therefore necessary to 'Null' all such settings, to enable the LightSpace CMS calibration to operate as required.


EDID is important for HDMI use for patch generation, as the protocol can be difficult to manage if it operates incorrectly, due to incorrect display and graphics card communication. Luckily, such problems are few and far between with modern displays and graphics cards.

DDC-CI and MCCS can effectively be ignored, so long as all graphics card settings are set to Null, as above.

EDID on the other hand attempts to ensure the image signal supplied by the graphics card is compatible with the display's expectations. That is all well and good when the communication is accurate, but can be a pain to overcome if the communication is inaccurate.

Inaccuracies are usually incorrect black and white levels, and are usually obvious to see, as defined in the Data vs. TV Legal Levels user guide.

With some graphics cards, such as Nvidia shown below, you can use the 'video' mode to compare the main graphics card output to the video output.

Graphics Card Settings

These settings change the black/white point for video output (only visible when the video is playing!), enabling a comparison to be made with the desktop output.

Graphics Card Settings

The above shows a live video stream set to 16-235 TV legal levels, with the desktop background set to 0-255 data levels.

When EDID goes wrong there are a number of options, depending on the graphics card or chip set being used.

ATI graphics cards have a manual option to force the card's output to data or TV legal ranges (0-255, 16-235).

Nvidia graphics cards do not have the same option, but can be forced via a utility file - such as NV_RGBFullRangeToggle.exe - if needed (although this is not always successful, depending on your graphics card drivers).
An alternative approach to force data range (0-255) is to set a 'custom resolution' (using the actual resolution figures), with a Hz rate that is slightly different to the expected standard - say 59Hz, rather than the standard 60Hz.


One device we have found rather useful with EDID issue is the small Dr HDMI box.


This allows independent control of most aspects of the HDMI signal, and we have used it will great success to overcome all issues we have not been able to manage with other approaches.