I moved my Windows 10 operating system, software and VIRB Edit video and GMetrix files to a new computer (an HP Omen 870-245qe desktop) with an NVIDIA GeForce GTX 1060 3GB PCIe graphics card and a Samsung 960 EVO PCIe NVMe 256GB SSD drive that I added to the M-2 slot on the motherboard. While this combination allowed me to edit and view videos from my VIRB 360 camera in full 1080p mode I noticed that as the videos advanced the displayed GMetrix data (track position, GForce, OBD2 speed, throttle position, engine RPM and others) would fall behind so that after several laps around my local road course the video would show me going through a turn while the GMetrix data would be back at the beginning of the straight section leading to the turn. This behavior persisted after numerous attempts to synchronize the GMetrix and video data. I tried many things, including uninstalling and reinstalling VIRB Edit, with no success, On a hunch, I finally moved the video and GMetrix files from the SSD drive to a 7000 rpm SATA HD that is also in the system. That resolved the problem. I have concluded that having the video and GMetrix files located on a PCIe based SSD drive which shares PCIe lanes with the graphics card leads to data transfer conflicts that result in the graphics data being processed more quickly than the GMetirx data. Curiously, however, the MAP view position data, which also comes from the GMetrix file, would correctly show my position throughout the entire duration of the video. I could have the MAP view and the Track position gauge displayed simultaneously and watch as the track position would fall farther behind the MAP view positon with each lap.
I am sure that my computer combination is not that unique so I have posted this to alert others who may have a similar setup to a potential problem and the workaround that I found for it.
