Batch Editing Images with Corona Image Editor

By popular demand, we have just released a script which allows you to batch edit CXR images with the Corona Image Editor.
Example use: save 100 frames of an animation in .cxr format, perform specific post processing operations and denoising on all of them, and output them in .png format.

The script comes with a help file and an example CXR, which you can experiment with.

The script can be downloaded here: [ LINK ]

Here is also a general guide on the CIE: https://coronarenderer.freshdesk.com/support/solutions/articles/12000030886

Requirements:
-Corona Image Editor installed
-Active Corona Renderer license

And now… Photoshop plugin! :slight_smile: Yes?

NOt bad. Buut, I hope, in some integration inside the CIE in the next Corona release. Batch isn’t very friendly.

Nice.

Hi,

I have encountered a problem with the script.

Basically, I do not have the CoronaImageCMD.exe. I have the CoronaImage.exe but not the command line version.
Should this be part of the standard install?

Corona version: 1.6
Full-speed, Non-debug, MaxSDK 2015
Build timestamp: Apr 24 2017 11:38:13
Defines: Wide RGB

My apologies! Seems I need Corona 1.6 Hotfix 1!

Thanks

Yes, the command-line version of the editor has been added in the 1.6.1 hotfix version.

Very nice feature…Thanks

I have a question actually. Yesterday we had a little job in rush, (it was only 30 seconds). And we needed denoise applied, so we sent it to the renderfarm and saved cxr. Then after downloading all files, I ran the script. The problem is it was slower than doing by hand. And as the job was in a little rush, opened and applied the pp file and saved all by hand since it was almost twice as fast as the script. That computer is i7-7700 32RAM. so I do not think that was the issue. Is there any way to solve this?

Hi, by “doing by hand” you mean opening the image in CIE and denoising it there? Are you denoising all elements, or just some selected ones? Please, could you share the image (and the postprocessing conf file) so I can inspect what is going on? You can use our private uploader for that: https://corona-renderer.com/upload.

uploaded and i guess denoise is already applied. Rebusfarm told me that to use denoise I need to save it as cxr, thats why its like that. otherwise i could have sent it as it meant to be.

And yes you got it right, it was faster for me to opening by hand, cliking load and selecting the file, then saving as png. :smiley:

Your set of steps did not include “Run denoising”… you did do that in the CIE?

The result i see on the image editor is sufficient enough. But the problem is, opening it by hand, then clicking load, selecting the file, then saving is faster than using the script. That is weird

Well, if you are asking the script to run denoising, it will take longer :smiley: Opening the image in the CIE with Denoise data that was saved for later does no denoising at all, you just have the regular non-Denoised image until you explicitly run the calculations based on the saved data. That is definitely the time consuming part, and if the scripting you are using invokes denoising, that is why running the script takes significantly longer, as the denoising is the time intensive part.

If you are just saving from the CIE without running denoising, that means you aren’t using it at all and could have submitted the job to the render farm going straight to PNG (at least as far as the denoising is concerned, depends on whether you are adjusting any other post process things like tone mapping etc differently than what was set in the VFB, though it doesn’t sound like it).

I have inspected the provided CXR and conf:

  • the image contains only beauty
  • it is already denoised and the conf has denoising turned off, so the command-line editor version (CLI) running behind the batch script is not performing any denoising
  • the conf switches bloom and glare on, hence the effects has to be computed both in CLI (automatically) and GUI (after manual loading the conf)

I see nothing wrong. The CLI version (and hence the batch script) is pretty swift on my machine. It takes about 3 seconds to process it. I doubt that I would be able to do it faster in GUI by hand.

I have also checked CLI executable what it truly does for that file. Everything seemed OK.

Is it slower every time? Even on different machines? What corona version do you use?

hi, I am done with the job so we cleaned the stuff a bit, I was using 1.6horfix2, since rebusfarm only has that ( iwas using daily 1.7 actually but for rebus, we merged the file into new one). and these were the files. For me the script took around 10-15 seconds, maybe there was a problem with my computer I dont know. But in near future ill have something similar.

but some pointers

  • yes it had only beauty, since its the only one I needed for that project
  • What do you mean? Was it disabling the denoise and then saving? I made it wrong i guess
  • about bloom, should it be off? I am not sure what do I understand about it

A question for rebus, I asked them what should i do for denoised image, because as we know, the render will finish, and then the denoise start, so I thought they might just stop it right there. So I asked them and they said I need to save it as CXR, but for example the next project is going to have around 10.000 frames, and that will be HUGE! to download and convert, do you know or suggest any other way?

OK, I understand. What I would like to ask you to do is test it on a different computer, since we are not able to reproduce such behavior for the files you have sent us. Would that be possible? The command-line version definitely should not be slower than the GUI version. And the batch script just runs the command-line version and passes a configuration to it.

No problem here. I was just saying …

No problem here either. It was OK. The CXR image from Rebus is already denoised. You can open the image in CIE (GUI) and check it in the combo box for switching render elements. There is a “” mark next to element’s name. The configuration file has denoising turned off. In your case it just means that the command-line CIE, i.e. the batch script, won’t denoise it again.

It is turned on because you have requested it. It is not a problem. Computing bloom and glare takes some time, but shall be the same for both the GUI and command-line version. Again, I was just saying …

Using the script is probably the way you want to go (form my point of view). It is strange that it takes more time to finish. It would be helpful if you could test it on a different machine (measure how many seconds it takes it in GUI and in the command-line version, visually check if outputs are the same). Maybe it is something wrong with your Windows setup. Hard to say.

Regarding activating in the script “Run denoising”…

The script seems to work for me regarding everything, saving in png also. But for some reason I’m not able to have it ‘Run denoising’ - which works if I do it by hand and save.

How do you set the script or configure it to activate the denoiser as if you were doing it by hand ?

Thank you

Hi, it is possible - you need to set the denoise.filterType option to Full. This can be done either explicitly on the command line, or via a config file saved from GUI after running denoising there. See CoronaImageCmd.exe --list-examples for example usage of the option.

can someone pls tell me what I’m doing wrong…

see linked video - grts