Author Topic: Corona render selected  (Read 14358 times)

2015-11-17, 22:23:32

jaco graaff

  • Active Users
  • **
  • Posts: 21
    • View Profile
I had some issues with using Render selected with Backburner/network render

I first tried using max standard "render selected" with "auto-region" selected - it worked for a couple of renders for a while and then suddenly all my renders defaulted to one specific region render

Then I watched the video on the feature again (
) and searched for more info and found there is a option in the Render dialogue under
Render Dialogue -> Scene Tab -> General Settings -> Render Selected:  Viewport selected
This worked locally but failed on network render, all frames came out blank

I then used the Include/exclude list option
This seems to be working now

2015-11-18, 12:48:29
Reply #1

atelieryork

  • Active Users
  • **
  • Posts: 283
    • View Profile
    • Atelier York
Doesn't surprise me that the viewport selected option doesn't work on nodes, since it's not really loading with the object(s) selected on those nodes.

Much much safer to use an include list or ID list etc.
Alex York
Atelier York
www.atelieryork.co.uk
max 2016 sp1, corona 1.3 final, win 8.1. pro

2015-11-18, 13:30:31
Reply #2

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13675
  • Marcin
    • View Profile
Hi, this is not going to work with network rendering. See:
https://coronarenderer.freshdesk.com/solution/articles/5000675901
https://coronarenderer.freshdesk.com/solution/articles/5000675900

You should get an error message informing you about this. Are getting it? Maybe you clicked "ignore similar"?
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2015-11-19, 02:10:42
Reply #3

jaco graaff

  • Active Users
  • **
  • Posts: 21
    • View Profile
The solution for Corona Render selected for network render: please see attached image

answers on replys:
No I did not see an error message

Yes I can understand/guess/deduct that the problem was the nodes did not know what has been selected in the viewport where the render originates from, except if the function was programmed to automatically include the ID of the selected in the render instructions send to the server. This should be documented somewhere (I think default max/scanline/mental-ray behavior allows this, that is why I used this approach first).

It did work using the selected ID feature. But I had to debug the problem by going to the dialogue and looking for additional features, searching on this forum and do several test to see if my solution now works before committing a job.

Great feature by the way, It cut down several sequences of 200 frames down from 10 minutes to just under a minute each.

I wish there was more explanatory help files where I can look up a feature I want to use (e.g. render selected) and the see an in-depth documentation of the feature-set instead of looking for answers in videos and guessing what the software developer's intend and target functionality was by reverse engineering the capabilities through trial and error.

I am not unhappy with Corona - this is a problem with most of the software I have worked with over the last 21 years. You most often need a 3rd party to come out with the Ultimate In-depth guide where functionality properties are explained and tested.

Also why I put this post up, because I could not find the answer and after 7 trial renders to the network trying different combinations I found the answer was to select the object manually again through the include/exclude dialogue.

Hopefully the next person will get to this post after one failure.

Thanks guys


2015-11-19, 02:18:05
Reply #4

jaco graaff

  • Active Users
  • **
  • Posts: 21
    • View Profile
Please see the attached images

1. CoronaRender_Ideal_As-it-should-be.jpg: Explains using the Max Render Selected with Auto Region option: This is in my case is the ideal since the edges are Anti-Aliased with the correct background and overlapping objects. Good for compositing. It does not work for animated objects or camera movements since the region is locked in place on a network render and do not follow the selected object. The render also takes longer since other objects not selected that fall within the region are also rendered.

2. CoronaRenderSelectedWeakness.jpg: This image show a blow-up of the edge pixels with unwanted effect of having over-dark edge anti-aliasing

Maybe I am just missing something

2015-11-19, 11:25:19
Reply #5

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13675
  • Marcin
    • View Profile
I think this is purely dependent on the compositing software you are using. Photoshop does not cope with this very well, but some applications allow you to use premultiplied/unpremultilpied mode (sorry, I never remember which one does what :) ). See: http://www.spherevfx.com/written-training/miscellaneous-written-training/understanding-premultiplied-images/
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2015-11-19, 21:37:28
Reply #6

jaco graaff

  • Active Users
  • **
  • Posts: 21
    • View Profile
Yes after effects use premultiplied or straight mode - but it still causes issues especially if there is heavy motion-blur or depth-of filed causing larger transparent edges. The problem is less visible if everything is in focus.

In this case doing motion-blur and dof in post will help

But the ideal is to have the edge-pixels colored with colors as close as possible to the backplate, which means the area-render around the selected object.

2015-11-20, 13:08:55
Reply #7

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13675
  • Marcin
    • View Profile
Sure, but I don't think this has anything to do with Corona. :)

In the previous images you are simply comparing cutting out an object which is on black background with cutting out an object which is on its border-colored background.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us