Two bugs I found with the most current build.
1. HCFR reads "too fast". When having set it to use a DVD as a source device you get these pop up windows which ask you to change patterns. When clicking OK - Windows takes some time to "phase out" the OK prompt itself, while HCFR is already reading.
I found this - because I was measuring my video players output after a new intel driver install and therefore used a video as the pattern source and not the built in pattern generator.
The error averages out at 0% ire (black), but 10-50% ire got significantly wrong readings every time I measured. At 60% and above it seemed to average out again. It was only after some time that I noticed that HCFR might pick up the not already "desolved" ok prompt in windows - and sure enough, when I moved the prompt each time, before hitting ok (it always appears in the center of the desktop), readings were fine.
Btw - this MIGHT also effect HCFRs readings for 0% ire (black), or red, or ... even if you use HCFR itself as the pattern generator - because there is an OK prompt before as well.
: I'm not sure how you should handle this one as the chances that someone would use HCFR as the measurement tool on the same device as he/she was measuring the video source - at the same time - while _not_ using HCFR as a pattern generator are slim, and also you can already circumvent the problem by moving the ok prompt in each step beforehand - but still, maybe a delay? (Dont especially like that one either...)
2. Your "yellow play symbol averaging on the softwares side" thingy is still active all the time after you start HCFR, even though the symbol shows it as deactivated. I have to manually deactivate it every time I start HCFR or else my readings take longer (i1d3 has this built in and doesnt need software side averaging). At which point (the first click), the Play symbol will NOT change to a stop symbol (which is correct) but the message that it "has been disabled" will pop up (also correct) indicating that it was running in the background all along.
Its not a settings thing, as it is persistent through reinstalls. Also it is VERY frustrating, because you _will_ notice your measurements taking excessively longer, if you forget to turn it off again...