Corona Renderer Forum

Corona Renderer for Cinema 4D => Corona Renderer for Cinema 4D - general => Topic started by: jp3112 on 2017-11-27, 02:08:35

Title: Save as .cxr from the rendersettings
Post by: jp3112 on 2017-11-27, 02:08:35
Hey everyone,

I started using Corona for C4D about a month ago, and I'm getting used to it more and more, and with this I'm more and more amazed, coming from Physical Renderer.
One feature I love most is the options it gives for postproduktion within the VFB and especially with the Image Editor.
But I'm heading a little problem, for which I haven't figured out a solution yet.
I'm rendering very frequently at a render farm (Rebus) at the moment, so I need to use the Rendersettings "save as" for saving, which isn't giving me the possibility to save a file as a .cxr to adjust the lights, exposure etc. later in the Image Editor.
Is there any way to work around this and I'm just to stupid to find it, or is that a thing I just have to take for the moment as it is and hope for Changes?
Title: Re: Save as .cxr from the rendersettings
Post by: houska on 2017-11-27, 13:33:23
Hi, currently the autosave feature needs fixing and saving .cxr files from C4D is a bit more complicated than we'd like. But what you can use for now is automatic saving of images into VFB history. Those images are dumped to the disk as well. So just enable saving of history at the end of rendering and locate your render in the correct place on the disk (if that's at all possible on a render farm). See the attached image
Title: Re: Save as .cxr from the rendersettings
Post by: jp3112 on 2017-11-28, 02:49:13
So at the moment there is no way for doing this as long as there is no way to get to that folder, which isn't possible on an external render farm like Rebus?
But even if that is the Case, your tipp is pretty useful, thanks for that!
Title: Re: Save as .cxr from the rendersettings
Post by: alessandromichelazzi on 2018-03-17, 16:13:28
I would put a +1 to this feature! :) I'm also using a lot the .cxr for editing further the file at the end, and having a way to save on the rendersetting will help to automate with the Tasks job.
Title: Re: Save as .cxr from the rendersettings
Post by: shane_w on 2018-03-28, 21:58:41
I tied this hack and it doesn't seem to work on my render farm (on a Mac anyway).  I was able to get the .cxr when I rendered the file locally but is doesn't appear the file is saved on a client machine.

Title: Re: Save as .cxr from the rendersettings
Post by: oroeo on 2019-02-14, 15:01:19
Sorry for awaken this thread but did something happen here? I contacted RebusFarm Support and they told me you can't render an CXR through their farm using Corona in Cinema 4D. Do you have any news?
Title: Re: Save as .cxr from the rendersettings
Post by: martonlente on 2019-03-29, 13:55:56

I'm also very much interested if it's already possible to save render results with Cinema 4D's standard render settings as CXR, in order to be able to postprocess them within Corona's essentially important Image Editor?

As many users noted, currently the only possible way of saving CXR is to setup Corona autosave as described in docs, which is a hacky workaround for an essentially important feature. It prevents users from using Corona e.g. with RebusFarm, and is very problematic in a business IT environment, if using Image Editor as part of a production workflow.

Do you have any plans to make saving CXR possible with Cinema 4D's standard render settings? Rendering to CXR and then postprocessing (and lightmixing) within Image Editor is simply the best workflow for still images Corona has to offer, but currently it's significantly compromised because of the lack of this feature.

If there is another workaround to use LightMix with another format than CXR within Image Editor, please also let me know.

Thank you for your information in advance,
Márton Lente
Title: Re: Save as .cxr from the rendersettings
Post by: houska on 2019-03-29, 14:15:12
Hi everyone,

sorry for the information embargo on this one! On a more serious note, we are aware of the fact that this is an important functionality, but unfortunately it's not so easy to implement as again, C4D API does not allow us to do what we would like. We do have plans to implement this in the future and maybe that future is not so far away, but I cannot promise any time frame as of now.