Layer Shading Clipping in Render

[Yosemite Sam]

So this has been going on for a long time, and now it's also happening in 14.2. If I do a render preview, everything's fine. But if I export I get this.

Any ideas on how to remedy this issue?

Thanks!

I included a wide shot to show it only happens when the frame border cuts off the character.

[slowtiger]

I think this can't be helped because of Moho's way of applying FX: first a layer gets rendered, then an FX is applied to it. Since Moho only renders inside the project window, the layer shading algorithm starts at the borders and creates what we see as artefacts.

Workaround: extend your project's dimensions by 100 px or more, and cut off that frame in editing.

[Greenlaw]

I run into a similar issue when compositing in After Effects and need to apply a glow or a blur effect that doesn't support 'extend edges'. This can happen with any footage, not just from Moho.

To solve this with Moho footage, I made a Moho template project with an overscan for 2020 x 1180, which extends the FHD edges by 50 pixels. This template also contains a matte overlay set to Do Not Render, Ignored By Layer Selector, and Immune To Camera, and set to 50% opacity. The overlay shows me the true visible area for the final comp output. Then, after exporting the footage using Layer Comps and Moho Exporter, I import the results to my Ae comp set to FHD, so the edges automatically get cropped. When I apply any effect that 'smudges' the edges, they look clean because it includes the color data from outside the edges.

If you don't use an external compositing program, you can do a two-pass render using Moho; the first pass with the overscan, then import the overscanned render into an empty project with the final dimensions to render the second pass with the cropped edges. If you plan ahead, you can set this up in Moho Exporter to do it all at once. Remember to save the Profile so you can easily load-and-go for later fixes and re-renders.

[Yosemite Sam]

I think this can't be helped because of Moho's way of applying FX: first a layer gets rendered, then an FX is applied to it. Since Moho only renders inside the project window, the layer shading algorithm starts at the borders and creates what we see as artefacts.

Workaround: extend your project's dimensions by 100 px or more, and cut off that frame in editing.

Slowtiger,

Thanks for the response! I'll give that a try. The thing that baffles me is that Moho is capable of rendering it properly. In the past, if the shot were under 20 frames, I'd render them individually and composite them in premiere. But as soon as you instruct Moho to render them out as a video, this happens.

[Yosemite Sam]

I run into a similar issue when compositing in After Effects and need to apply a glow or a blur effect that doesn't support 'extend edges'. This can happen with any footage, not just from Moho.

To solve this with Moho footage, I made a Moho template project with an overscan for 2020 x 1180, which extends the FHD edges by 50 pixels. This template also contains a matte overlay set to Do Not Render, Ignored By Layer Selector, and Immune To Camera, and set to 50% opacity. The overlay shows me the true visible area for the final comp output. Then, after exporting the footage using Layer Comps and Moho Exporter, I import the results to my Ae comp set to FHD, so the edges automatically get cropped. When I apply any effect that 'smudges' the edges, they look clean because it includes the color data from outside the edges.

If you don't use an external compositing program, you can do a two-pass render using Moho; the first pass with the overscan, then import the overscanned render into an empty project with the final dimensions to render the second pass with the cropped edges. If you plan ahead, you can set this up in Moho Exporter to do it all at once. Remember to save the Profile so you can easily load-and-go for later fixes and re-renders.

Appreciate this info! Good stuff to know.

As I responded to Slowtiger, Moho is capable of rendering this effect properly. I've overcome the issue in the past by simply rendering out the frames individually and compositing them in premiere. But if it's over 15-20 frames at 4k it becomes too much. So odd as soon as you render it out as a video, this hiccup happens.

[Greenlaw]

For example...

Here's my FHD Plus template, which is 1920 x 1080 plus 50 pixels overscan all around...



This template includes an overlay to show me the cropped region. The overlay is the darker 50% opacity region surrounding the clear center. The outer region is just Moho with Show Output enabled to display a built-in matte with 35% opacity. (Remember to enable Save and Restore Viewport Settings to make this setting stick as your default.)



And here's what the template looks like with one of my animations...



Hope this helps.

[Greenlaw]

...I've overcome the issue in the past by simply rendering out the frames individually and compositing them in premiere. But if it's over 15-20 frames at 4k it becomes too much. So odd as soon as you render it out as a video, this hiccup happens.

Ah, glad you got it solved, and thanks for letting me know what happened and how you fixed it.