I know you meant June. I did read it. Thank you.
- You tell AME which AE comp you want to render.
- A headless version of AE spins up in the background. (Regardless of whether or not you have the project open in an active version of AE.)
- The headless version of AE renders each frame and hands it to AME.
- AME encodes the frames to the settings you defined.
I was not sure what headless version spins in the BG meant? In regards to #4. So by checking off my switches for Blur, Blend, etc and change the BPC to 16 in my comp then save it. that is what AME uses to render? Also to disregard Rick's post on this one then? Thanks for your input on this.
June or July, what's the diff when it's almost November? (Thx for pointing out my typo. Edited my last post to the correct month for the benefit of future readers.)
Netcommercial wrote: I was not sure what headless version spins in the BG meant? In regards to #4. So by checking off my switches for Blur, Blend, etc and change the BPC to 16 in my comp then save it. that is what AME uses to render? Also to disregard Rick's post on this one then? Thanks for your input on this. |
When AME renders an AE comp, it launches a version of AE that runs without showing any UI, aka "headless". This happens silently, "in the background", invisible to you unless you're watching what processes are active on your computer with Task Manager/Activity Monitor. The headless background version is launched even if you have AE launched already (this way you can keep working in AE while AME renders).
To make the difference between AE and AME's capabilities clear for you, I think we need to be more specific about the difference between Rendering and Encoding. We often use those terms interchangably as umbrella language for getting your frames out of an application and into a file, but we should put them into proper context for this particluar pipeline.
Rendering is the calculation of the pixels in each frame of your comp. AE will always be the application rendering the frames in your comp, even if it's just a headless background version of AE.
Encoding is taking the series of frames in your comp and writing them into a file, using an algorithm (codec) that you choose. Both AE and AME can encode frames from your comp into a file.
The big difference, and where I think you're getting hung up, is this: in AE's Render Queue, the Render Settings options allow you to change how AE renders the frames before they're encoded but only for when AE does the encoding. AME does not have this option, nor does it read Render Settings from AE's Render Queue.
Further, to clarify: AME does not know anything about what is in the Render Queue in your AE project. You don't need to put your comp in the Render Queue in order to render it with AME, and any settings you make in the Render Queue are ignored by AME.
Clear?