In ColourSpace v1.0.1.2233, the new option "Separated Grey Scale from Cube size for profiling" (Grey Axis Size) appears to misrepresent what is actually measured. With a 13³ Body Centre Cube Based profile, the default greyscale contains 25 grey axis patches. If I increase Grey Axis Size to 101 or any other number, the RGB Balance/EOTF graph re-scales and the point spacing changes, which visually implies that ~101 greyscale samples exist. However, the profiling run still measures only the original 25 greyscale patches—the additional grey patches are not generated/measured/included in the profile data. So the UI/graph suggests an expanded greyscale axis, but the measured dataset remains at the default count (25) even when set to 101 (see screenshot).

The new Ramp Size setting for QP works correctly.

Yes - there is something not working correctly there.
It seems some setting/operation triggers the issue, as it is not initially a problem.
But is is not related to Body Centre Cubes.
It would help if you can test better, and provide more accurate info, as will help isolate the issue.
For example, does deleting the .ini file and starting afresh change things?

We will look into it and sort a fix.

Steve

Thank you!

I tried to isolate it further, but the behaviour is consistent on my side:
· Persists after a clean start: deleting the ColourSpace .ini and starting fresh does not change the outcome.
· Not BCC-specific: I can reproduce it with regular cube patchsets as well (not only Body Centre Cube Based).
· Core symptom: increasing Grey Axis Size (e.g., from the default greyscale count to 101) changes the graph scaling/spacing in the RGB Balance/EOTF view as if the additional grey samples exist, but the actual profiling sequence/profile data still contains only the default greyscale points (no additional grey patches are generated/measured/included).

At this point I'm not sure what additional "better" test would meaningfully narrow it down because the issue is quite obvious.

It is a weird bug.
Not there on first install/operation for most users.
But then is there.

We will find and fix.

Steve

I can confirm that the bug is fixed. Cube based and also BCC with extended Grayscale works correctly now! Thanks for the quick fix.