Hello,
currently, PremierePro does Smart Rendering
as FCP7/X or MediaComposer does, only for a handful of formats
which means, only those portions of the sequence are rendered
that need to be in case, the sequence-codec/format and the clip codec/format are the very same.
See here:
https://blogs.adobe.com/kevinmonahan/2012/10/11/smart-rendering-in-premiere-pro-cs6-6-0-1-and-later/
When exporting via AME this means, every time You output the sequence in PremierePro, 100% of the images are processed during export again.
If You export a sequence into 3 different
delivery formats, the whole sequence is rendered 3 times.
Therefor, to render a sequence doesn’t make much sense.
You COULD set the preview codec to e.g. ProResHQ
and check ‘use preview files’ in AME.
BUT: this would mean, if the render-files are ProResHQ and You export the sequence into a ProResHQ master, the ProResHQ render files are decoded and re-encoded into the very same format again…
So: DON’T DO THAT!
When You need to export into several formats:
PremierePro’s rendering workflow delivers a better quality
but it also takes longer.
(But as long as PP’s image processing pipeline is not 100% 32bit-float,
combined with CPU-CUDA differences in quality, this advantage is very theoretical…)
One thing I don’t understand:
Why does Adobe offer so many different sequence presets?
Since PremierePro’s sequences are codec-independent,
there seems to be no technical reason for that!
It appears to be a help for those who don’t know in which
video standard they are working…
Best regards,
Bernhard