From: Greg Ercolano <erco@(email surpressed)>
Subject: [Q+A] AfterFX: How to render duplicated comps as separate jobs?
   Date: Mon, 19 Aug 2013 21:27:04 -0400
Msg# 2354
View Complete Thread (1 article) | All Threads
Last Next
> We want to render out a single AfterFX comp (317 frames) in three different
> output file formats; a .mov file, a .mp4 file, and as a .tif sequence.
>
> To do this, we drag the comp into the AfterFX Render Queue,
> and then make two duplicates of the comp, and change the output module
> for each duplicate.
>
> Trouble is, when you duplicate the comps this way, the three entries
> in the AfterFX queue all have the same comp name.
>
> How to we render these three AE Render Queue items separately in Rush?

    Right, so you basically have this in the AE Render Queue:

[Render] [ ] [#]  [Comp Name]        [Status]     ..
   ▷      ✓   1    Comp1              Queued      .. Output To: TEST_010_v01_Comp1_e01.mov
   ▷      ✓   2    Comp1              Queued      .. Output To: TEST_010_v01_Comp1_d01.mp4
   ▷      ✓   3    Comp1              Queued      .. Output To: TEST_010_v01_Comp1_f01.[#####].tif

    ..where items #2 and #3 are "duplicates" of item #1 (right clicked on item #1 and chose "Duplicate" twice)

    Because "Comp1" was duplicated, the duplicates are all named "Comp1",
    so you can't really use the comp name to render each item separately.
    I think in this situation, if you submitted a job with "Comp Name:" set to "Comp1",
    AE will only render the first matching comp (the .mov generator), and ignores the others.

    Adobe's "aerender" command actually has a special command line option for this situation
    called "-rqindex" which expects the AE Render Queue index number to be rendered.

    I've modified the 103.03 (and newer) submit-afterfx script to include an "RQ Index:"
    prompt (to the right of the "Comp Name:" prompt) so that you can specify index numbers
    in place of comp names. This also automatically makes the job's log directory pathname
    unique by tacking on the rq index number to the pathname. This way you can submit
    several jobs with the same scene file using the newer script, and the logs won't overwrite
    each other. So with the new 103.03+ submit script, you could submit the three jobs this way:

JOB #1
       Job Title: AFTERFX_MOV
      Scene Path: /path/to/your.aep

          Frames: 317
    Batch Frames: 1
 
Output Pathname: <leave blank>
       Comp Name: <leave blank>
        RQ Index: 1
            Cpus: +any=1.1@1

JOB #2
       Job Title: AFTERFX_MP4
      Scene Path: /path/to/your.aep

 Output Pathname: <leave blank>
          Frames: 317
    Batch Frames: 1
       Comp Name: <leave blank>
        RQ Index: 2
            Cpus: +any=1.1@1

JOB #3
       Job Title: AFTERFX_TIF
      Scene Path: /path/to/your.aep
 Output Pathname: <leave blank>
          Frames: 1-317
    Batch Frames: 5
       Comp Name: <leave blank>
        RQ Index: 3
            Cpus: +any=10@1


    This renders the two movie file renders (.mov and .mp4) as 'single frame rush jobs'
    so that each renders on a single machine, and the tif sequence as a multiframe rush job
    batching the 1-317 range in chunks of 5 frames each.

    For older submit scripts (102.xx), you'd have to fill out the submit-afterfx form this way
    to make use of the -rqindex flag:

JOB #1
       Job Title: AFTERFX_MOV
      Scene Path: /path/to/your.aep
          Frames: 317
    Batch Frames: 1
 
Output Pathname: <leave blank>
       Comp Name: <leave blank>

            Cpus: +any=1.1@1
    Render Flags: -rqindex 1

JOB #2
       Job Title: AFTERFX_MP4
      Scene Path: /path/to/your.aep
 Output Pathname: <leave blank>
          Frames: 317
    Batch Frames: 1
       Comp Name: <leave blank>
            Cpus: +any=1.1@1
    Render Flags: -rqindex 2

JOB #3
       Job Title: AFTERFX_TIF
      Scene Path: /path/to/your.aep
 Output Pathname: <leave blank>
          Frames: 1-317
    Batch Frames: 5
       Comp Name: <leave blank>
            Cpus: +any=10@1
    Render Flags: -rqindex 3

    With the older script, you'll need to click past a warning about the 'Comp Name' field
    being empty because you're using the -rqindex flag to control which comp to render.
    (the newer 103.03+ script won't have that issue)

    Also, with the older script, the log directory will end up being the same for each job,
    causing the logs to overwrite each other. This is because the log directory is automatically
    generated based on the scene name, and will end up being the same directory if the jobs
    all use the same scene filename. One way to work around that is to make two copies
    of the .aep file with slightly different names, and submit those so that the log directory
    ends up being unique for each one.

    The newer 103.03+ script won't have this problem because it includes the RQ Index
    and Comp Name in the log directory pathname to ensure it's unique, even if the
    scene file is the same.



Last Next