Fabio - Unfortunately not, as your 'crap' profile works with my PCs (multiple machines, including a really basic Microsoft Surface Laptop 3, as in the HERE links provided above) the issue is obviously with your system's allocated resources.[/url] links provided above) the issue is obviously with your system's allocated resources.
As I have suggested in our email discussion, I think you should talk to Parallels support, as it seems they may have have an issue with the way they manage Windows resource allocations.
I'm using VMware Fusion, as I gave up paying for the inferior operation of Parallels.
(But there are issues with VMware Fusion too!)

My M1 Mac, which is far inferior to your M4 Pro Mac, will work with just about any profile, other than your crap one, at 256^3 LUT Generation and madVR Upload.
That your Mac cannot upload a Unity LUT when set to 256^3 madVR upload operation is the same issue as not being able to actually generate 256^3 LUTs.

And you have also told me your Mac cannot do 65^3 LUTs, when my M1 Mac will do them all day long, with any profile, including your crap one.

I am really sorry, but all this really does point to an issue with your Mac resource configuration.
And that really is 'User Error'.

Steve

Gian luca - If you mean moving a ColourSpace license, please see the 'Licensing' page of the website.

Steve

Today I created a 3D LUT in space map at 256 without any problem, while after 5 hours the chroma peak got stuck at the end! The 3D LUT space map was created correctly, but when I load it it still reaches 80% and says loading error.

As the User Guides explain, the Map Space option for LUT Generation uses a multi-step approach to LUT generation workflow that requires far less PC resources than needed by Peak Chroma.
And as stated above, the Upload process requires the same resources that are used in standard LUT Generation - Peak Chroma - so if you cannot generate a 256^3 LUT via Peak Chroma you will not be able to upload a 256^3 LUT generated by less resource demanding options.

I would recommend using the Env. Variable, and sticking to 65^3 LUTs for madVR with your PC system.
You will get excellent results setting LUT Generation Size to 128^3, and performing 65^3 LUT Uploads into madVR.

Steve

Today Enrico connected me to the PC explaining the procedure to be able to use the latest version of colourspace with the Env environment variant!

Setting Env. Variables is a standard Windows procedure.
Very simple to do, and the required Env. Variable info is available as a download from the website.

Steve

I am the one who proposed Gian luca to test 256 on his Envy.
Then, as his PC is low in performances (I5), even if used only for running CS, I have generated them for him (we have the same licence level, so I thought it is fair)
And then he discovered he cannot upload them. Not only, if he does not perform a specific action (no mention in the release notes), he cannot even upload new LUTs on his Envy. Based on this discussion, what is the sense of doing a LUT at 65 and uploading it at 256? So, why not using the LUT Vertices setting for enabling 256 LUT uploading? Anyhow I agree with you Fabio (Blackjoker): it is not a user error.

Steve, some question for clarification:
1. Do you have users reporting that 256 LUT uploading is working with Envy?
2. Can we assume that if a PC can generate at least a 256 LUT, it can also upload to Envy? Gian luca's PC generates 256 LUT if Fit Space is used. No way with Peak Chrome (endless for 8 hours). That's also following your I5 PC recommendations.
3. How can Gian luca, and in general users, be sure that the PC they will be buying supports 256 LUT generation?

As has been said a number of times, if a PC doesn't have the resources to generate 256^3 LUT (not using lower resource options, such as Map Space) it will will not be able to upload to madVR.
If a user attempts to use a PC without the resources to be able work with 256^3 LUTs, that is User Error.
We have defined this multiple times within the User Guides, as well as on these forums.

And no, LUT Generation size has nothing to do with madVR LUT Upload size.
For example, there are likely serious benefits in generation a 128^3 LUT, and uploading inti made VR at 65^3, as already stated.
I assume you know about Nyquist Sampling?

Our own testing with madVR HTPC show a PC with the required resources works as defined.
We have requested madVR test an Envy, but they are too busy
But, anyone with an Envy can also test using madVR HTPC to define if there are any differences, as has already been stated in this discussion.
(The suggestion has been ignored so far - but if you can prove there is a difference, madVR would need to look into that.)
If there are any differences, that would be a madVR issue.
And no, as already stated, using low-resource LUT Generation options, such as Map Space, will not guarantee the PC can upload a 256^3 LUT into madVR.
(The resources required to convert the ColourSpace 256^3 LUT object into the correct madVR 256^3 object, and upload it, are high - basically the same as generating 256^3 LUT within ColourSpace using Peak Chroma...)
And I have defined the PCs we have tested on, and the settings used, in the linked to thread HERE.

And as you know, the profile your cannot get to generate a 256^3 LUT with your system works perfect well with all my systems, as per our email exchange.

Steve

You should take in account legacy: think all high licence users that due to PC limitations will not be able to upload LUTs to their Envy/Madvr (and forced to use that user configuration they might heve never used). You should consider to have 65^ upload as the default option for next releases.

Yes I know. And I am trying to do some assessment I have finished I will post here

So I understand my 66^3 profile, generated with Virtual Probe (with some tricks, otherwise impossible to be run in CS), profiling a ST2084 rec2020 and having as Source Gamut a DCI P3 with gamma 2.4 with an Alternative WP, worked also on your I5 PC? How long did it take?
Once it also worked on my PC (Microprocessor AMD Ryzen 7 5825U with Radeon Graphics, System memory 16 GB) with default settings (so I have it). But all the other times CS crashed, even when I have followed your recommendations allocating 300GB of paging memory on my SSD.

As the issue is PC resources there is nothing we can do for anyone using legacy PCs.
It is not a ColourSpace issue.
And that is why the madVR upload size option can be user set via an Env. Variable, which you set once and forget forever.

And it is not just RAM or paging file sizes for the LUT generation/upload.
It is CPU resources, and even GPU.
As well as background processes, etc.
All have different impact on the actual resources available within any PC or VM.

If you have issues, simply set the LUT Generation Size to lower value, and set the Env. Variable for madVR to 65.
It really is very simple, and we have provided all the tools & options necessary.
You could even ask madVR to add a 128^3 LUT option...

Steve