Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

multiple aerender instances show multiple "Repeated Frame" messages when run in parallel

Explorer ,
Nov 06, 2018 Nov 06, 2018

I'm running several instances of aerender, and the logs keep showing this "Repeated Frame" message:

PROGRESS:  0:00:12:00 (1): 2 Seconds

PROGRESS:  0:00:12:01 (2): 0 Seconds

PROGRESS:  0:00:12:01 (2): 0 Seconds

PROGRESS:  0:00:12:02 (3): 1 Seconds

Repeated frame 2

PROGRESS:  0:00:12:02 (3): 0 Seconds

PROGRESS:  0:00:12:03 (4): 0 Seconds

Repeated frame 3

PROGRESS:  0:00:12:03 (4): 1 Seconds

PROGRESS:  0:00:12:04 (5): 0 Seconds

Repeated frame 4

PROGRESS:  0:00:12:04 (5): 1 Seconds

PROGRESS:  0:00:12:05 (6): 0 Seconds

Repeated frame 5

PROGRESS:  0:00:12:05 (6): 1 Seconds

PROGRESS:  0:00:12:06 (7): 0 Seconds

Repeated frame 6

PROGRESS:  0:00:12:06 (7): 0 Seconds

PROGRESS:  0:00:12:07 (8): 0 Seconds

Repeated frame 7

PROGRESS:  0:00:12:07 (8): 1 Seconds

PROGRESS:  0:00:12:08 (9): 0 Seconds

Repeated frame 8

PROGRESS:  0:00:12:08 (9): 1 Seconds

PROGRESS:  0:00:12:09 (10): 0 Seconds

Repeated frame 9

PROGRESS:  0:00:12:09 (10): 0 Seconds

PROGRESS:  0:00:12:10 (11): 0 Seconds

Repeated frame 10

... and so on.

It seems to be rendering the same frame twice.

It doesn't happen when I run the same job in only one instance.

The final render seems to be OK, but does anyone know what this means and how to prevent it?

1.9K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Nov 07, 2018 Nov 07, 2018

Did you separate your comp into smaller pieces before rendering and if not, have you checked the skip frames option in the render queue?

*Martin

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 07, 2018 Nov 07, 2018

martinr84659894  wrote

Did you separate your comp into smaller pieces before rendering and if not, have you checked the skip frames option in the render queue?

*Martin

Yes, each instance is rendering a separate range of frames.

And there is no render queue involved, each process renders a comp by name, with no "-i" setting.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Nov 07, 2018 Nov 07, 2018

I've never seen such a output before...

What's the command line you are using, what does the whole environment look like?

Do you get more repeated frames when you start 3 processes on parallel?

On a sidenote: have a look at RenderGarden | by Mekajiki

They are using an AE script for separating the comp and python scripts, to launch aerender.exe.

*Martin

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 07, 2018 Nov 07, 2018

Actually I'm using a modified version of RenderGarden.

I just realized the "Repeated frame" message is being generated by RenderGarden itself as it parses each line aerender output.

I'll ask Mekajiki.

Thanks

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 07, 2018 Nov 07, 2018

I tried running the same aerender command manually, and it does show many frames being rendered twice:

PROGRESS:  0:00:00:00 (1): 0 Seconds

PROGRESS:  0:00:00:01 (2): 1 Seconds

PROGRESS:  0:00:00:01 (2): 0 Seconds

PROGRESS:  0:00:00:02 (3): 0 Seconds

PROGRESS:  0:00:00:02 (3): 1 Seconds

PROGRESS:  0:00:00:03 (4): 0 Seconds

PROGRESS:  0:00:00:03 (4): 0 Seconds

PROGRESS:  0:00:00:04 (5): 0 Seconds

PROGRESS:  0:00:00:04 (5): 1 Seconds

PROGRESS:  0:00:00:05 (6): 0 Seconds

PROGRESS:  0:00:00:05 (6): 1 Seconds

PROGRESS:  0:00:00:06 (7): 0 Seconds

PROGRESS:  0:00:00:06 (7): 0 Seconds

PROGRESS:  0:00:00:07 (8): 0 Seconds

PROGRESS:  0:00:00:07 (8): 1 Seconds

PROGRESS:  0:00:00:08 (9): 0 Seconds

PROGRESS:  0:00:00:08 (9): 1 Seconds

PROGRESS:  0:00:00:09 (10): 0 Seconds

PROGRESS:  0:00:00:09 (10): 1 Seconds

Why would it do this?

command:

$ "/Applications/Adobe After Effects CC 2018/aerender" -project "/Volumes/Common/_Automation/testing/YV-v6.6-template.aep" -OMtemplate YesDVC -comp "YV2" -output "/Volumes/Common/_Automation/testing/test4/output.mov" -s 0 -e 9 -v ERRORS_AND_PROGRESS

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Nov 07, 2018 Nov 07, 2018

Where is this command-line from? How do you set up your render garden?

I'm wondering about rendering into a MOV with multiply instances, which isn't working. You can only use parallel-rendering in combination with image sequences.

Also, it's using the output module template YesDVC, whatever this is.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 08, 2018 Nov 08, 2018

Command line is written by hand.

This is NOT rendering multiple instances. Just one.

No parallel rendering.

Output module makes no difference, whether Lossless or this DVCPRO.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Nov 08, 2018 Nov 08, 2018

The only thing I can think of are fields.

When you put your comp into AE render queue, check render settings as well as output module. If both are as you wish, use your command line without -OMtemplate argument. This is just for trouble shooting...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 18, 2018 Dec 18, 2018

Just experienced this as well, using Render Garden.

Seems that rendering the proes-file with audio output causes this for me. Turning off audio-output in the render queue fixes it.

Not sure how I'd output something with sound now – I'd have to add it later.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Dec 18, 2018 Dec 18, 2018

https://forums.adobe.com/people/Aktuba%20Ink  thank you for finding out!

I just recognized, that the repeated frames in the output is always 0 secs rendering time. So, maybe this is just an output message and it doesn't affect overall rendering? Could you may make a little speed-test?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 18, 2018 Dec 18, 2018
LATEST

Don't have time to test right now (on a deadline) but I'm sure it was stuck much longer that 0 seconds on those frames – my render also didn't finish properly. Rendering sound separately now and adding it using an old QT7 pro.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines