# Testing the Pipeline This image shows the testing in action. First an explanation of what the image shows and how it was created. This is a single screenshot, on macOS with ColourSpace running in a Windows virtual machine. DaVinci Resolve is running in the background ColourSpace in the centre overlaid with cs_remote to the left and cs_patch_translator on the right. ![[ValidationTest.png]] The flow of the patches: 1. cs_remote generating the colour triplet numbers and sends them to 2. ColourSpace managing the measurement and transmission on to 3. cs_patch_translate converting the protocol to send to 4. DaVinci Resolve Here they are all the same, however the timing can make this hard to catch, to be sure, slow the patch transmission down. Do this with the 'Auto' function in the Probe config in ColourSpace, to maybe 1.00 then it is easy to see the transition, especially if the dialogs are on different screens. *This is what the Auto function calculates by measuring the patch sent is the one measured.* ## Pipeline Follow the steps outlined below to be sure the patch values are following through the full pipe from: CS Remote -> ColourSpace -> CS Patch Translator -> DaVinci Resolve ## Tesing set up 1. Open 1. ColourSpace 2. DaVinci Resolve 3. CS Patch Translator 4. CS Remote if you are using it 2. Set them up as described in the Guides - [[CS Remote guide]] - [[CS Patch Translator guide]] 3. In ColourSpace select the **VIRTUAL** probe 4. Set the 'adjust' value to a few seconds, enough time for you to read the values in all four places 5. run a short patch set like 'Mastering.' 6. For each change be sure to check the colour values change all the way through the pipe 7. If in doubt make a video or take photos 8. When you are confident, use the Auto button function on the Probe config page in ColourSpace to be sure the configuration is working for the measurements, which is what matters!