Using 1.0.0.1925, configure a Rec709 profile, 10-bit Legal, Virtual Probe Rec709 100 nits, and run a Gamut Sweep 75% Primary & Secondary characterisation. Enable HSL in the Bars Widget, and see that all but two points show a Hue and/or Saturation error. Now enable Point move, pick the point (721,327,327), which starts with a displayed positive Hue error, and alter the y value both up and down, and see that the Hue error is displayed as negative in both cases. Now pick the point (721, 458,458), which also starts with a displayed positive Hue error, and alter the y value both up and down, and see that the Hue error is displayed as positive in both cases.

You will only ever see this with the Virtual probe.
Please test with a real probe.

Steve

Attached are two red saturation measurements, both showing negative hue errors.

Attached file: Test.bcs

Yes - negative Hue errors are perfectly acceptable and valid.
A rotational error can be either positive or negative.
Both are totally correct.

The issue I was referring to is the fact an 100% error is shown when the actual measurement is totally perfect.
That will only ever happen with the virtual probe.

Steve

Actually, I think I do now see what you are actually trying to describe.
Red always shows an Hue error as being Negative.
Other colours do not.
Is that what you mean?
Please, please be very specific when trying to define any potential issue.

Steve

The two measurements I provided have opposite hue rotations, yet both are shown with negative hue errors; obviously they can't both be correct. The red hue errors aren't always negative; see my first post. For point (721, 458,458), both increasing and decreasing y (i.e., generating opposite hue rotations) result in positive hue errors being shown; obviously they can't both be correct.