Updating this first post with the end conclusion.
The recent ColourSpace change to enable 256^3 LUT to be uploaded natively into madVR will only work if the user's PC is capable of generating 256^3 3D LUTs.
For PCs that are not capable of 256^3 LUTs an Env. Variable can be used to set higher ColourSpace licenses back to work with 65^3 madVR LUT sizes.

Steve

I thought the MadVR Envy could not accept a LUT size greater than 65^3. Do they have new firmware that allows a greater LUT size?

The native 3D LUT size for madVR has always been 256^3.
They added the ability to load eeColor based 65^3 LUTs as no calibration systems could natively work with 256^3 LUTs.
So it is the 65^3 option that was 'added'.

But, it seems Envy might not have previously been tested with direct 256^3 uploads, while the software madVR HTPC uploads with no issue.

Steve

MadVR PC and MadVR Envy are two different products. I do not "dabble" with the PC version much but heavily "dabble" with the Envy. The Envy has never been able to accept its native lut size. There are and have been another calibration systems (I personally know two exist) that could upload its native lut size.... if the Envy could accept it.

All I can say is that is not the information madVR have provided us from the beginning.
You might what to discuss this with them?
And 'Uploading' LUTs via madVR integration is not the same as importing LUTs held externally.
We've never use LUT import, as ColourSpace has always been fully integrated into madVR - software and hardware.

Steve

It think this is a case of you being out of the loop.

As we had this exact conversation with madVR before we announced the addition of the 256^3 LUT Upload option, I don't think so...
But I guess they they may have forgotten their own limitations?

Steve

@DNice could you try to upload a 256^3 LUT? For me it's not working. It crashes at 80%

Fabio - I sent you an email with some things to test.
Not heard back from you?

Steve

Will try that tomorrow and will let you know.

Fabio - I've just realised the issue is likely your PC - you have already said it cannot generate 256^3 LUTs natively, and if so it will likely not be able to upload 256^3 LUTs into madVR.
As we have discussed, as you are using VM there is likely a memory allocation issue stopping large LUT sizes working.
So it may not be a madVR issue at all.

But a PC that cannot actually generate a 256^3 LUT will never be able to upload a 256^3 LUT into madVR.

Steve

As a final post in this discussion, madVR have confirmed all that has been said above about all madVR systems being able to upload 256^3 or 65^3 LUTs.
Testing is ongoing, but the original issue looks to have been user error by trying to use a PC (a VM in this case) not capable of working with 256^3 LUTs.

Steve

Before we judge to early we should see if others with may more powerful machines then a M4 Pro with 48 GB of ram ran into the same situation.

As I've already suggested, try madVR HTPC - you will have the same issue.
We have tested that, and it works on a decent PC.
Fails with an M1 Mac via VM for the same reasons you have.

And any PC that cannot generate a 256^3 LUT natively will definitely never work to upload a 256^3 LUT into any madVR system.

Steve

How much RAM is needed for 256^3 LUT? Ballpark figure?