Thanks for your input, Dave.

I have just saved a RAM preview using the Output Module settings below,

and the result is a 32bit .tga sequence with premultiplied alpha.

As I understand it, the only limitation is that a RAM preview doesn’t generate

interlaced fields, so this method is only valid for a progressive composition.

I also recommend double-checking on the type of alpha channel to be delivered: Premultiplied or Straight.

This is a method I use internally for DI's... so no delivery concerns.

And I learned something new today as well, so thank you.

I believe if someone knew everything there is to know about AE,

it's likely their head would explode.

Thanks again for your input.

Thank you Todd for the detailed clarification.

I don't save my RAM previews in all instances... usually linked comps

that I know will slow a final render and export in Premiere if I don't use a DI.

Like you, I would never use the 'Save RAM Preview' function if the render queue

would recognize and utilize the frames that are already rendered into RAM.

If the 'RAM Preview Options' are identical to the 'Render Settings' in the Render Queue

(i.e. full frame rate, full resolution, active camera view),  the queue should see and use

any frames sitting in RAM, skip to the 'Output Module' and write the file(s) to disk.

Instead, the Render Queue ignores the already rendered frames waiting in RAM,

and starts over rendering every frame again.

For example, if you have rendered every third frame at full resolution as a RAM preview,

the render queue should see those frames and just send them to the Output Module

and only need to render the two in-betweens.

By setting RAM Preview Options to full frame rate, full resolution, active camera view,

I can essentially skip directly to the Output Module by saving the RAM preview.

The primary benefit is that I can output the same RAM preview to multiple Output Module

settings without re-rendering the frames by using the Output Module Templates dialog

box to choose a different output module template for RAM Preview, and re-exporting.

These differently formatted outputs will utilize the frames waiting in RAM, and do

not require any additional rendering time... only the time to write the file(s) to disk.

If you send a comp to the Render Queue, choose an Output Module, duplicate the

pending render without changing the Render Settings but change the Output Module,

the queue will render all of the frames twice in order to write to the two outputs.

Saving two RAM previews cuts this time in half.

Unless I have missed something, I suppose this is a feature request?

Aha!  So, I did miss something:

Multiple output modules assigned to a single render item.  Thanks for that.

But... if I take the time to do a RAM preview, those rendered frames are still not

utilized in the final output if I use the render queue instead of a saving a RAM preview.

I suppose this should be the feature request?

If the 'RAM Preview Options' are identical to the 'Render Settings' in the Render Queue

(i.e. full frame rate, full resolution, active camera view),  the queue should see and use

any frames sitting in RAM, skip to the 'Output Module' and write the file(s) to disk.

For example, if you have rendered every third frame at full resolution as a RAM preview,

the render queue should see those frames and just send them to the Output Module

and only need to render the two in-betweens.