Page 1 of 1

Bug? Images + cross dissolve + fusion node breaks rendering

PostPosted: Sun Jan 24, 2021 9:53 pm
by twinoak
Hello,
This made me scratch the old head a bit when it first appeared. I'd appreciate if someone could try to duplicate.

I've boiled it down to these steps:

  1. Create a new project and go to the Edit tab
  2. Insert an image to a track (I've tested with jpg and png), copy it and append it to the first one
  3. Add a cross dissolve between the two clips
  4. Right click the second clip and select Open in Fusion Page
  5. Add a fusion tool between MediaIn1 and MediaOut1, shouldn't matter which one, I've tested with Transform->Transform and Effect->Duplicate
  6. Save the project, Shift+1 to open the project manager, right click the project and select Close, open the project again
  7. Go to the Deliver tab, render the entire timeline, settings probably don't matter. I've tried MP4 with h264 as well as MXF OP1A, DNxHR 444 12-bit. Full HD, 25fps.
  8. On my machine, this consistently breaks the rendering with the message
    Code: Select all
    Render Job 1 failed as the current clip could not be processed. The fusion composition on the current frame or clip could not be processed

System:
Surface Book 2
i7-8650U
16 GB RAM
GTX 1060

Thanks!
Alexander

Re: Bug? Images + cross dissolve + fusion node breaks render

PostPosted: Mon Jan 25, 2021 5:56 pm
by Jim Simon
Go to Preferences>User>UI Settings and uncheck Stop renders when a frame or clip cannot be processed.

Re: Bug? Images + cross dissolve + fusion node breaks render

PostPosted: Tue Jan 26, 2021 8:59 pm
by twinoak
Thanks, but that is not going to help!

What I forgot to mention (because I was focusing on the test project and replication steps, and not the production project that I first saw the error in), is that this error can manifest itself visually.
In the production project, the result is a cross dissolve that starts out looking normal, but from the beginning of the second clip it's mixed with a fade from black type effect. Not fully black, but a very noticeable jump in intensity.

The only workaround right now is to delete and re-add the transition before rendering, it's fine for subsequent renders until you close and open the project again. And if I turn on the option you suggest, I'd have to wait the whole render time to find out that I forgot to replace the transition. Stop on error can be a time saver in that respect.

Best regards
Alexander