Legend

Question

Can no longer render layers with 3d movement?

Forum|Forum|3 years ago
August 22, 2022
2 replies
577 views

Here is a screen recording of the simple comp I'm working on:

If it makes any difference, the comp is 30 frames per second.

Also, my specs are here and here.

I'm not a pro, just trying to help my wife with her business. So please forgive the amateur nature of my project and question... trying to learn.

We're just doing a reel promoting some new t shirt designs. One visual I like is creating a "tiled wall" of graphics using CC Repetile, and then zooming it out and letting it move on various axes, for instance what happens at about 00:20 in the video above. I have done this before, on this same computer, in other projects, and it has worked. I just check the 3D box and then keyframe the position, rotation, scale, etc. At the end of the video above, I open up a layer to show those keyframes.

I first noticed the problem in Premiere Pro actually. This comp is not the whole video, it's meant to be composited over a background and with Essential Graphics (text) in Pr. But I first noticed there was a problem there because I couldn't render my Pr timeline. I narrowed it down with trial and error... everything renders/exports fine, in both Pr and Ae, EXCEPT for the Ae layers in this comp that contain that 3D movement. If I turn those layers off, it exports beautifully.

As you can see, it previews fine which is why I could make a screen recording. I've tried rendering both with GPU and software only. I've also tried opening a new Ae project and importing this into it.

The reason I'm stumped is because I've done this before, on this machine with these specs. The only thing that's different is the newer version of Ae and also Windows has updated a time or two since the last time I did this. Would that have anything to do with this? Is there anything I can do to get this to render/export?

Thanks!

This topic has been closed for replies.

C

cre8vimpAuthor

Legend

So I think I've discovered the real problem: it's not the 3D motion as I thought, but those clips are the same ones that have CC Repetile on to achieve that floating grid effect. When I turn off CC Repetile, everything renders fine. (I'm using the Render Queue and software only rendering, suggested to me by @Rick Gerard and the error dialog in AE respectively.) I don't remember the exact verbage, but something in the error dialog led me to believe that I have tried to replicate the grid to a size too large for AE to process (too many pixels vertically and horizontally). So tomorrow I will try decreasing that and make sure my 3D movement is not so drastic that it reveals the edges of the grid. Hopefully that works.

R

Rick Gerard

Community Expert

You can sometimes solve problems with CC Repetile by pre-composing. It all depends on your comp.

C

cre8vimpAuthor

Legend

Thanks! I tried precomposing, but it didn't work. 😞 What did work was to shrink the size of the canvas created by the CC Repetile effect... bring down the pixel amounts some on each side to just barely what was needed. I also had to adjust the 3D motion because if it's too drastic it requires a very large canvas. Then I had to render with software only. I didn't finish the render because it threatened to be a 12 hour ordeal, but hey... at least I found out it will work. So I'll just let it render all the way when I finish. Thanks for your help!

Last question: what are the pros/cons of the render queue vs AME in this case? I realize the available presets aren't the same, but regarding performance, is one better in this case and why? Seems like the render queue would be better because it doesn't require having a second app open... but on the other hand, AME can run by itself too. And I could in theory work on something else during. So is there a reason you suggested specifically the render queue? Thanks!

R

Rick Gerard

Community Expert

Any comp that takes more than one or two seconds to render a frame should be Rendered using the Render Queue and the default High-Quality Output Module template. The rendered shot would then be brought into Premiere Pro to replace the original shot, and Dynamic link removed.

Rendering a dynamically linked comp in Premiere Pro opens a copy of After Effects in the background and uses that to render inside Premiere Pro. It is always slower than rendering using the Render Queue. Sometimes, much slower. Some effects may not use GPU acceleration when rendering in the background.

That doesn't answer your question about the render failure problems you are having, but it will probably solve your problem, and I'm sure it will take less time in the long run to complete a project. I use Dynamic Link to create comps from shots in Premiere Pro all the time, but about 90% of the time, as soon I save the comp, I undo the DL in Premiere Pro, finish the comp, render it, and then replace the shot in the PPro sequence. It's just a lot more efficient workflow.

There are dozens of things, from 3rd party software updates to AE updates, that could have caused your problem. Even lower disk space or some app that is using up RAM. It's hard to diagnose without knowing a lot more about your comp, your workflow, and your setup.

C

cre8vimpAuthor

Legend

Thank you so much!

So is there a performance difference between using the AE render queue and AME? I don't usually use the AE render queue at all. It was in AME that the comp wouldn't finish.

If it matters, I forgot that I intended to show the AME log for my repeated failed attempts:

08/21/2022 09:39:07 AM : Queue Started

- Source File: D:\tshirtdemoreels\tshirtdesigndemo_AME\tmpAEtoAMEProject-main comp.aep
- Output File: D:\tshirtdemoreels\tshirtdesigndemo_AME\main comp 220821a.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 25 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:49:24
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:

08/21/2022 09:56:06 AM : Queue Stopped

08/21/2022 01:47:52 PM : Queue Started

08/21/2022 01:53:46 PM : Queue Paused

08/21/2022 01:53:50 PM : Queue Stopped

- Source File: D:\tshirtdemoreels\tshirtdesigndemo_AME\tmpAEtoAMEProject-main comp_1.aep
- Output File: D:\tshirtdemoreels\tshirtdesigndemo_AME\main comp.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 25 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:49:24
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:

08/21/2022 02:03:04 PM : Queue Started

- Source File: D:\tshirtdemoreels\tshirtdesigndemo_AME\tmpAEtoAMEProject-main comp_2.aep
- Output File: D:\tshirtdemoreels\tshirtdesigndemo_AME\main comp_1.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 25 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:49:24
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:

08/21/2022 02:32:22 PM : Queue Stopped

08/21/2022 02:36:18 PM : Queue Started

08/21/2022 02:38:36 PM : Queue Paused

08/21/2022 02:38:40 PM : Queue Stopped

- Source File: D:\tshirtdemoreels\tshirtdesigndemo_AME\tmpAEtoAMEProject-main comp_3.aep
- Output File: D:\tshirtdemoreels\tshirtdesigndemo_AME\main comp_2.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 25 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:49:24
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:

08/21/2022 02:42:52 PM : Queue Started

08/21/2022 02:44:05 PM : Queue Paused

08/21/2022 02:44:12 PM : Queue Started

08/21/2022 02:44:18 PM : Queue Paused

08/21/2022 02:44:22 PM : Queue Stopped

- Source File: D:\tshirtdemoreels\tshirtdesigndemo_AME\tmpAEtoAMEProject-main comp_4.aep
- Output File: D:\tshirtdemoreels\tshirtdesigndemo_AME\main comp_3.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 25 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:49:24
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:

08/21/2022 03:30:11 PM : Queue Started

08/21/2022 03:39:58 PM : Queue Paused

08/21/2022 03:40:02 PM : Queue Stopped

- Source File: C:\Users\jeffm\AppData\Local\Temp\Untitled Project_AME\tmpAEtoAMEProject-main comp.aep
- Output File: D:\tshirtdemoreels\422testa.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 30 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:50:00
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:

- Source File: C:\Users\jeffm\AppData\Local\Temp\Untitled Project_AME\tmpAEtoAMEProject-main comp.aep
- Output File: D:\tshirtdemoreels\422testa.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 30 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:50:00
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:
- Encoding Time: 00:19:41
08/21/2022 03:49:56 PM : Encoding Failed
-------------------------------------
The Operation was interrupted by user
-------------------------------------

08/21/2022 04:20:54 PM : Queue Started

- Source File: C:\Users\jeffm\AppData\Local\Temp\Untitled Project_AME\tmpAEtoAMEProject-main comp_1.aep
- Output File: C:\Users\jeffm\AppData\Local\Temp\Untitled Project_AME\main comp.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 30 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:50:00
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:

08/21/2022 04:36:49 PM : Queue Stopped

08/21/2022 04:38:36 PM : Queue Started

- Source File: C:\Users\jeffm\AppData\Local\Temp\Untitled Project_AME\tmpAEtoAMEProject-main comp_2.aep
- Output File: D:\tshirtdemoreels\main comp_1.mov
- Preset Used: Apple ProRes 422 LT
- Video: 1080x2280 (1.0), 30 fps, Progressive, 100 (63% HLG, 51% PQ), Quality 100, Apple ProRes 422 LT, 00:00:50:00
- Audio: Uncompressed, 48000 Hz, Stereo, 16 bit
- Bitrate:
- Encoding Time: 00:00:47
08/21/2022 04:39:27 PM : File Successfully Encoded

08/21/2022 04:39:27 PM : Queue Stopped

Also, here is the first error dialog I got in Pr when I tried to to Render In To Out the first couple times.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded