Workflow with Render Manager and AI Enhancer in Corona – How to Access VFB Image

Hello, we usually render using the take system. So far, we have solved this by leaving the images in the VFB (autosaving the images in Corona at the end is enabled in corona settings) and then enhancing them afterwards from vfb history with Corona AI.

Now, however, we want to use the render manager (i.e., open multiple Cinema 4D files with multiple takes). The rendering works as expected, even if nothing appears in the VFB, but then we no longer have the option to access the images in the VFB because they are not displayed there.

Is there a way to use our workflow and still improve the images afterwards with Corona AI?

In particular, I have read that since Corona 14 Update 1 there is an option — Added option to save an image that is viable for AI Enhancer from VFB. How do you use this?

Thanks,
Tuami

Hi, the option mentioned in the changelog is available here (see screenshot), however I don’t think it will be useful in your case. We will need to look into this and see if we can come up with some workflow.

Thank you, Maru, but unfortunately this doesn’t help further. At the moment, it’s not possible to do the following with the AI Enhancer:

  • Rendering using the Take System and Team Renderer – the workaround we currently have (autosaving the images at the end, enabled in the Corona settings) only works for local renderings with take system.
  • Rendering with the Render Manager – here as well, no usable files are generated that could at least be enhanced by the AI afterward.

This is really important because, in the future, we want to avoid having to manually prepare each image for the AI one by one. For some projects, we render more than 500 images, and right now, the only way we can manage is to render each image locally one after the other.

It would already be a great help if the usable AI-enhanced files could be saved in a specific location – so they could then be loaded into the VFB (history?) and from there sent to the AI for post-processing. Right now, this only works with local rendering and the Take System – everything else unfortunately doesn’t.

tuami

I am afraid there is no workaround for now. Could you please log this as a feature request in our Ideas Portal? https://chaoscorona.ideas.aha.io/

Perhaps I’m misunderstanding something.
But why shouldn’t the generated .cxr-files from autosave don’t qualify for AI enhancement ( loaded in the VFB history)?
-granted the number of images kept on render end is set to the number of takes you have?
( and of course Ai Enhacer is loaded in the Multi-Pass setup)

Autosaving the images at the end, which can be enabled in the Corona settings, does not work with Team Render .When rendering via Team Render, the images do not appear in the History. It only saves the images to the History when rendering locally.

I discovered it that it is possible to render multiple images sequentially in this way and then send them to the Corona AI afterward, Unfortunately it doent work whjen using teamrenderer.


Hello Corona Team,

Could you please make it possible to save the images in the Frame Buffer History when using the Team Render?
At the moment, the images are only stored in the history when rendering locally (and, of course, only if the corresponding option is enabled in the Corona settings).

This would be an immense improvement to the workflow. I am currently rendering hundreds of images locally and, for the reasons mentioned above, I unfortunately cannot use Team Render.

Thank you very much in advance.

Best regards,
Tuami

This is reported as (Report ID=CC4D-1303).

thank you, hope this will be fixed soon
cheers

Hello, are there any updates on this, especially with the new Corona version approaching?

There have been noticeable issues for quite some time — like this one here — where features that should normally work still do not function properly. In my opinion, it would be very important to continue prioritizing the correction of existing issues and improving the stability and reliability of the core functionality alongside the development of new features.

I know this is slightly outside the original topic, but with an upcoming major release, I think ensuring a solid and reliable workflow is especially important.