When I re-select a profile generated after a customized ramp + with 169 patches (virtual probe) the original ramp+ indicator, as recognised by CS during profiling, is changed to generic profile:

I suspect that Multi-Primary Colour Engine is not enabled.
The same operation on a customized patch-set generated after a 141 patches patch-set works fine.
That does not change until I restart CS.
To reproduce you have to leave LUT tools selected to the bcs with the patch-set "export"
An old back-up version I keep (September 2023) does not show this issue.

Attached file: Related bcs and csv

On your first feed-back I produced a recording: https://1drv.ms/v/s!Agrddzvyi1trgZRGHGTQx7UWiISnDQ?e=kjjOLc
It is interesting as you can note (due to the slow speed of the recording), that when you select, it suddenly change to profile. Maybe helpful to you.
I could not find in my mind any case in which in LUT tools you change something in profile information (indeed the profile information are not changed, but its representation changes until CS is restarted.

Not sure if Multi-Primary Colour Engine is still invoked, as it appears that "ramp +" info is lost.
Can you please clarify?

This is expected operation, as the profile exceeds the limits for + profiles.

The website User Guides have been update to define the limits.

We will also look to remove the initial incorrect profile type info. This is caused by the profile NOT being loaded when the type is first defined, and is then corrected when the profile is loaded.

Maybe we can increase the limits as well, as PCs are obviously more powerful now, and we have multi-threading for LUT Generation in the higher ColourSpace license levels too.

Steve

I.e.:

The current built-in size is 141 patches. It is based on a 20 points grey scale. Basically I have room for adding only one level


My feedback: With my PC (Operating system Windows 11 Home 64 bit Version: 22631.4169, Microprocessor, AMD Ryzen 7 5825U with Radeon Graphics, System memory 16 GB), a 141 patches LUT generation takes seconds. Definitely shorter than the time it takes a large profile with augmented data.
PS: Should I interpret your "will" as a WIBINI?


It looks like a bug! Your first reaction when I described what was happening was "Not possible". And that is corrected only till CS stays open. Definitely you should avoid that a ramp+ profile with more than 150 (indeed 148) is recognised as ramp +.