Image Editing tonemapping error

[PMVis]

Hello,

Since upgrading to Corona 12 I'm experiencing a problem when opening CXR files through the image editor.
The tonemapping settings and especially the LUTs are not loading correctly and I get the following error message (see attachment below)

I merged the scene into a new scene and tried re-saving and that hasn't helped.
I also haven't changed the default location of the LUT files.

Any assistance would be appreciated.

Thanks
Phil

[Max Knol]

I had the same issue but it has vanished slowly by itself over time. I suspect the new VFB in corona has some changes that werent properly pushed through to the image editor (i.e. the image editor didnt get a proper update eventhough the vfb in the renderer did causing some small incompatibility)
I'm just speculating here though.

[PMVis]

I had the same issue but it has vanished slowly by itself over time. I suspect the new VFB in corona has some changes that werent properly pushed through to the image editor (i.e. the image editor didnt get a proper update eventhough the vfb in the renderer did causing some small incompatibility)
I'm just speculating here though.

Thanks, for responding. I'm glad to hear I'm not the only one having this issue.

Anyone from the Corona team with any input on this issue?

[TomG]

The CIE is not updated (as this would require it being rewritten into Qt too). However, the VFB 2 in Max can now act like the CIE in that you can load a CXR and immediately edit it, regardless of what scene (or none) is loaded in Max. Previously, you had to load the same scene into Max, then "resume render from file" for at least 1 pass in order to get the CXR "active" for editing in the VFB, but that's no longer needed, you can just load the CXR into the VFB 2 and do CIE things to it with all the new parameters and functionality. If the CIE is a must (e.g. for some sort of batch editing of many images), then using the old VFB in Max would be the way to generate and save the scenes.

[PMVis]

Thanks for the reply Tom. Are there any plans to update the CIE in the future? I find it more convenient than opening CXR's in max, which takes so long to open these days.
 

[pokoy]

Yes, CIE's fate seems shaky for some time now. Is there a plane on how to get it up to date and also provide some of the long requested abilities like better (UI based) batch/sequence editing, and more consistent denoising options? In fact, I'd take the features over a Qt rewrite.

[TomG]

There is no timescale set, but the CIE is not being abandoned. Nothing has happened yet for two reasons - the VFB 2 is still being developed, and right now it would take duplicate work if we were to try to keep the CIE up to date with the ever-changing VFB 2. Better to have the VFB stabilize out a bit first.

Then there is also hope that we could rework things so that basically updating one would update the other; but this takes totally reworking the CIE to get to that very beneficial position. And I guess a third reason is that yes, we'd like the update to be major in terms of features too, e.g. improved batch editing is something I think would be very useful, as you mention something that was UI and not command line driven.

So those are what we'd want to achieve, no timeframe on it, other than "not this year" :) Beyond that, we'll keep you updated!

[PMVis]

OK, sounds great. Thanks for the info Tom.