Ae cc (2014) render queue vs media encoder

hey there,
when i render one of my current clips (1080p animation with about 10min duration) from after effects with output format quicktime, codec h264 and quality 100, the file will have about 2gb (about 40 to 50 mbps). but when i send the comp to AME and choose "qt with h264 at 100" the file will have only about 300mb. even though the bitratelimit is at 20000 kbps and the quality slider is at 100 the result has only a bitrate of about 5000 kbps.
so here are my questions:
1: can i set the desired bitrate instead of the quality?
2: how can i get the "almost lossless" quality from the inside-ae-render (40mbps) in AME?
3: when i send someting from AE to AME, what about the rendersettings? is everything "on" or "as is" (like effects, proxies etc)?
thx...

dear rick,
of course you are right. for the actual masters i use motionpng or motionjpg . sometimes cineform. for shorter clips tiff-sequences.
but this does not answer my question. in the current case i have to have "master-like" files (for re-encoding) that are still playable in most players and on most devices. therfore h264.
but actually my question is not about which codec to use for different purposes (had long research- and discussion-sessions about that already).
the question is: why do the seemingly same encoders in ae and ame (quicktime with h264 with qualityslider 0-100) deliver so much different results?
i'm trying to figure out, whats the difference between ae-rendering and ame-rendering. how do i deal with rendersettings (effects, proxies etc) in ame? which one is better to use? and why the fudge is there a difference of 1:10 with the same settings in the different solutions????
thx...

Similar Messages

Where are the AE render settings in Media Encoder?

I'd like to use Adobe Media Encoder for background rendering, but how do you set the render settings (like bit depth, motion blur, solo switches, guide layers, ect)?
Also, how do you select the output color profile from AME?

Hi Clint,
Sorry for the long delay on replying, I've been busy. Doesn't look like you've cross-posted this to the AME forum, so I'll take a crack at the answers:
1) AE renders compositions at a bit depth of 8, 16, and 32 (float). AME can encode frames at 24, 32, 48, and 64 (for ProRes 4444, for example). How do these things relate to each other, and how/why should you use a particular AME bit depth setting for an AE comp?
These numbers all represent bit depth. AE states bit depth in terms of bits per channel (bpc). AME usually states bit depth in total bits per pixel (bpp = bpc multiplied by the number of channels). It's one of those little inconsistencies that comes from the two apps growing up under different development teams.
RGB has three channels. RGB + Alpha has four channels. Doing the math:
RGB 8 bpc = 24 bpp
RGBA 8 bpc = 32 bpp
RGB 16 bpc = 48 bpp
RGBA 16 bpc = 64 bpp
So if you want 8-bit output with an alpha channel, you'd set the bit depth in AME to 32. If you don't need an alpha channel, set it to 24. Note that AME doesn't have equivalent options for 32 bpc formats. (If it did, the bpp equivalents would be 96 and 128 bpp!) There are very few such codecs anyway.
2) What effects does "Use Maximum Render Quality" have on a comp? Does it only come into play if your are encoding to a different resolution to the source comp? Will it change the color processing?
IIRC, the "Use Maximum Render Quality" switch doesn't affect AE comps. It only has an effect when the source is a Premiere Pro sequence. This article has some detail about how the switch affects Premiere Pro sequences:
http://blogs.adobe.com/premiereprotraining/2010/10/scaling-in-premiere-pro-cs5.html
3) Does AME always render at "Full" resolution or does it look at the resolution setting in the AE comp window? What if it's set to "auto"?
4) Does AME pay attention to the comp window Region of Interest?
5) Does AME care about the composition motion blur button or does it just look at the layer motion blur settings?
7) How does AME handle color management? Does it always output in the working space?
These questions all have the same basic answer. When the AE comp is loaded via Dynamic Link, it will be processed using the state of the comp at the time the AE project was saved. Any switches available in the Timeline panel like Motion Blur will be used in their current state, and there is no control over them from the AME side.
Keep in mind that comp viewer switches like Region Of Interest and preview resolution aren't a function of the comp itself, and thus aren't seen by AME. They are a function of the Comp viewer panel. (The difference being the same as between a piece of artwork and the glass of the frame. If the glass is warped then the art looks warped. AME only looks at the artwork without the glass.) Color Management, similarly, while controlled at the project level is interpreted via the Comp viewer panel or by AE's Render Queue; AE's color management is not in the chain of processing used by AME. But you can acheive the same color management transforms via AME by using the Color Profile Converter effect and setting the input and output profiles specifically.
So, what AME sees in an AE comp will be identical to what you see in the Comp panel in AE at full resolution when ROI and any other viewer switches (like the Transparency Grid or guides or color channel selection) are turned off, and without a project working color space being set. From this point the pixels could be affected by AME via scaling or if there is a color space transform inherent to the chosen output format (ex., RGB to YUV).
6) How does AME decide whether to interlace the render?
This is defined by the Field Order setting in the AME Output Settings. That seems pretty straightforward to me, so if I'm missing something about your question please clarify.
-=TimK

Send a render job to Media Encoder on another system?

I am a recovering Final Cut Pro user. Switched over about version FCP X 10.3. The railroad tie that broke the camel's back for me was a removed feature I am hoping I can do with Premiere in some way.
In FCP 7 and even FCP X up to 10.3, you had the option of sending a render job to their version of Media Encoder (Called "compressor") just like Premiere Pro can do now. However, you had the option of being able to use a "render cluster" by where if compressor was loaded onto other macs on your network, it would send the job out to one of those nodes or even split it up and send parts of it to several computers to parallel encode the job. Made large jobs faster and allowed you to not have to bog down your processors on you main computer with a render job. Apple just took it out with 10.4, which was a deal breaker for me.
I know Premiere/Media Encoder does not have the ability to split the job up, but was wondering if there as a way I could send a render job to Queue up on the Media Encoder of another system...say my Mac mini server which also has Media Encoder on it. Is there any way to select the path to the Media Encoder and thus have it deploy the render job to the other machine?
Thanks.

You can export a Sequence on another machine on your network, if that's what you want to do.
You can save your Sequence on your A machine, then import the sequence to AME on your B machine, and export away.
I do this myself. I allows me to keep working on my A machine at more or less full speed while my B machine is cranking out review movies or whatever. There's a little network overhead, but not enough that I notice.
Just click the + icon in AME on your B machine, and navigate to your project and sequence on your network.

AE CS4 render engine / Adobe Media Encoder won't create a container for h.264 blu-ray

here's the problem.
First, I tried to render a comp using the render engine inside AE using h.264 blu-ray preset.
It was supposed to create 1 file, but I ended up with 3 : audio track, video and a file with .xmpses extension.
I then decided to render it in lossless .mov, which works fine, but 3:40 minutes is taking up over 8gb, which is of course, unacceptable.
After that, I've put the .mov file into Media Encoder to try h.264 blu-ray there.
Absolutely the same ********.
I'm using the Mac version of AE CS4.
Here is the screenshot of original .mov file and the result. As you see, it refuses to make a container. This is absolutely unacceptable

It raises another question: what settings do I need to encode the comp in 720p resolution without taking up lots of space?
Well, it depends on whether you need a production master (something for broadcast, for example, or to use as a source for other encoding tasks) or if you want a version for distribution. If it's the former, there's nothing wrong with "lots of space" - A Quicktime file with PNG or Animation codec is a good idea, but it will take a lot of space. If it's the latter, H264 is perfect but there's no built-in preset to take 720 material to the web.
You could do this:
* Pick the generic H264 template. You'll see that it will give an error if you attempt to render, because the default setting uses an H264 profile/level which doesn't let you use HD resolutions.
* In the H264 video options, set the "Profile" menu to "Main" and "Level" to 4.0. That will keep it compatible to Quicktime and Flash player, while allowing larger frame sizes and higher bit rates.
* Set Target Bitrate to 5-8 Mbps and Maximum Bitrate to 9-10 Mbps if you're targetting web delivery. That's a bit over what Apple uses for 720p content on the Apple TV, for example.
The H264 original preset will instruct you in the comment field to stretch to 640x480 in Output Module. There's no need, since you are using a profile/level combination which allows higher frame sizes.

Twixtor plugin doesn't render using Adobe Media Encoder

Hello, I'm having a weird case here with Twixtor 5.0 and Premiere CS6.
First I was getting the orange screens rendering a sequence with twixtor in it. Them I read the solution for it, that is: "The seuquence have to be the same setting as the clip with twixtor applied"
So I did it, and profit! It was working. I fixed all my sequences, and send to Adobe Media Encoder. After I burned the DVD with the MPEGs AME created, the orange screens were there again.
If I export straight from Premiere, the video is fine! No orange screens, but if I send the sequence to AME, or even import it straight from AME, the video will have the error.
Please, can someone help? There's a lot of chapters, and I don't want to render one by one trough Premiere, I could even put everything in one final sequence, but them I don't know if the final MPEG would save the chapter marks I would have to create in it...
I really like AME, and want to use it
Thanks!
P.S:
Windows 8 PRO
Premiere CS6 6.0.3
Twixtor V5.0

If you set Encore chater markers in PP, name them and export out using MPEG2-DVD, they will carry over to Encore.

Save queue in Media Encoder... where does it save to?

Hi. When you have your projects queued up in Media Encoder, under File you can 'Save Queue'. This does not actually let you save as, and does not indicate where the information is saved to.
Does anyone know where the information is saved to? Is there a queue file I might be able to view outside of Media Encoder?

Hi Wayne,
You are correct. In the iMovie Projects folder in your User>Movies folder, right-click (or Control-click) on the name of your project. From the pop-up menu select Show Package Contents. There you will see a Movies folder where your shared movies for that project will be located.
John

Render issues in Media Encoder

This has happen a few times, but when I go to render my movie in Premier and then it opens up the media encoder program to render and I hit start, it freezes up a lot or takes a very long time to render. If I take that same Premier project and bring it into After Effects, it renders no problem.
Does anyone know what would cause this?
My files are basic .MXF files, quicktime with animation compression, or avi with lagrath compression. But this is very random. Some times I never have an issue, and other times it acts up and I just end up rendering in AE.
Any thoughts would be great.
PS...I ever tried of seeing if it was a certain file...so I would get rid of all my .mxf files and still...then I would get rid of all the .mov files, ect... I never could find a common problem to this.

Are you by any chance using the Titler in Premiere? I had some problems with render jobs hanging mid stream on one project and learned that the Titler is not entirely stable.
That's about the only experience I have in this area, wish I could help more.

Premiere Pro Unresponsive after queuing to Media Encoder

In the current version of Premiere Pro (8.1.0), every time a send a sequence to the Media Encoder, Premiere becomes unresponsive. But not in a spinning beach ball of death fashion. It's like the UI is non responsive, with some very strange behavior. For example, when I try to quit and save, the save dialogue just sits there until I have to force quit the application.
Any thoughts? This is extremely annoying!

Exact same problem here, plus exports are slow
Specs
latest CC
OSX 10.9.2
3.4GHz Core i7
32Gb 1600MHz DDR3
GTX 680MX GPU
4TB Thunderbolt GRAID, footage/project files
3TB USB3 Seagate for cache
1TB Apple for system

Problems with "queue" to Media Encoder

I just downloaded the latest CC updates yesterday which was for AME and PPCC ...
After the update when i go to >EXPORT> MEDIA > then press queue it locks up/stalls. Nothing goes to AME. I have to keep turning off the process.
I tried a 3 minute clip and it worked but anything above 20 mins it stalls...
Rather than "queue" i have to use "export" which means i cannot use premiere pro while it exports my project. I usually have to export 4-5 things from one project so its very time consuming and its waisting alot of my time.
I tried opening up AME seperately then either drag and drop or go to >add files and adding the sequences from the project, but when i do this i get a message that say "READING XMP' and it just stays like that for ever unless i kill it through task manager...
I run a production company so these kind of issues are super frustrating and costing me money.
Im guessing its has someonthing to do with the new updates as this wasnt occuring before the updates... has anyone had same issues ?
Shouldnt be having these basic problems.... Pls fix or help asap ADOBE !!!
windows 7
adobecc
i7-2600K 3.40Ghz
16GB ram
just realised some other wierd things since the update..... is there anyway of taking off the latest updates and rolling back to the previous version ?

Just a comment:
I'd say you found a workaround...not a solution, though it's helpful to know there IS a way around the problem.
I'm having a similar problem, and am still searching for an answer. (Unfortunately, my project is due tonight, and I'll suffer the lengthy software-only encoding, spending time in this forum rather than gamble/waste time experimenting/uninstalling/re-installing). This is ruining my Easter weekend.
This is my 2nd round of problems using CC (a few months back I uploaded a file which went missing for a few days while Adobe scrambled to fix what was apparentyl a widespread problem, while I had to re-build a project from a prior version. That took me days, though I did it before the file I uploaded was "found". And, of course, I encountered the problem following the latest update at the time...just like today's problem).
I get the sense they're pushing things out, i.e. new "versions"/"updates", before adequate testing is done. I worked in QA for many years in the corp hq of a Fortune 500, and was afraid CC would suffer the "rush" to distribute without proper testing. I feel as if end-users are testing new updates, which makes me question the reliability of new releases. Unfortunately, this raises questions about CC being "professional-level software". If it's not thoroughly tested, how can professionals rely on it?
End of rant...Thanks.

Premiere Pro CC not queuing exports into Media Encoder CC

I try to make this simple...
standard export from PP CC to ME CC
File -> export -> media, then hit queue.
Media encoder opens and just sits there. Left it for hours to see if anything would ever happen, and nothing ever did.
I've restarted the programs and machine dozens of times and that does nothing.
I can still export from PP CC.
I have no CS6 products left on my box.
I also tried to open the project from Media Encoder and load the sequence that way with no luck.
Thanks for the help!
On a Mac Pro
Premiere version 7.0.1
Media Encoder version 7.0.1.58
Adobe Creative Cloud for Teams Member (so it's licenced and updated to the fullest)

rforgaard wrote:
I had this exact same problem, and I figured out the solution in my case. I know the original problem report is ancient, but there are recent replies, so I am adding my solution here. I spent untold hours figuring this out, so hopefully this will save someone else some time.
There can be other causes to this problem, I'm sure. I'm just telling you about what fixed this problem for me.
Just to clarify, here is the symptom: Running Windows 8.1. Standard export from Premiere Pro CC 2014.2 to Media Encoder CC 2014.2, using File -> Export -> click Queue. Media Encoder opens and just sits there. Premiere Pro is hung and has to be forcibly terminated.
I spent countless hours on this. I thought I had messed up my computer's configuration somehow, so (believe it or not) I re-installed Windows on a freshly formatted hard disk, re-installed Creative Suite, same problem. (I can't believe I wasted all that time; I feel like a dummy.)
I finally narrowed it down to a very simple test case with a very tiny one-clip sequence that is less than one second long. Same problem.
It turned out to be a problem in the Premiere Pro project file itself. I suspect that a small file corruption somehow snuck into the project file, that was completely invisible. In that clip in my project, if I removed the "Vocal Enhancer" effect, the problem with exporting to Media Encoder went away. If I then re-added the very same "Vocal Enhancer" effect, the problem was still gone. It must be some small corruption in the ".prproj" file that went away when I removed the "Vocal Enhancer" effect and re-added it again.
NOTE: I DON'T think that there is some kind of bug with the "Vocal Enhancer" effect. I don't think this problem has anything to do with "Vocal Enhancer" per se. It is just some kind of small generic corruption in the project file. When Premiere Pro tries to export that sequence to Media Encoder, the problem occurs. It was just a coincidence in my case that removing and re-adding the "Vocal Enhancer" effect made the problem go away.
BOTTOM LINE: If you find that you have this bug where Premiere Pro hangs when exporting to the Media Encoder queue, try the following: Create a brand new project with a single clip in it, and export it to the Media Encoder queue. If that works, you know that it is not a problem with Premiere Pro in general; it's a problem in your specific project file. Once you've made this determination, make a copy of your original project file, and remove clips from the project until the problem goes away. Keep narrowing it down until you find the clip(s) that are the issue. Then, try removing and re-adding any effects on those clips, or even removing and re-adding the clips themselves, to fix the problem. Eventually, by removing and re-adding a specific effect or clip to your project, the problem will vanish (hopefully). It's just a matter of narrowing down which half of your project the problem occurs in, then which half of that half, etc., until you have it narrowed down to one clip or group of clips that need to be removed and re-added.
Having said all this, it is a bug that ideally should be fixed so someone else doesn't spend untold hours trying to figure out the problem. To that end, I create a tiny ZIP file that just has project file and the single media clip needed to reproduce the problem, along with a small description "READ ME.txt" file that explains the very simple steps to reproduce the problem. I have submitted this as a bug report to Adobe using their official online bug report form at www.adobe.com/cfusion/mmform/index.cfm?name=wishform along with a link to the ZIP file so they can download and reproduce the problem.
If anyone else is curious about reproducing this same bug, you can also download the small ZIP file if you want to. I guarantee it doesn't have any viruses or anything - it's just two small files to reproduce the problem. To download the ZIP file containing that project file, media file, and "READ ME.txt" file, you can get it at www.forgaard.com/files/PremiereProBug.zip.
I hope this saves someone some time. This one sucked up a zillion hours of me chasing apparitions.
I was having a problem with exporting a sequence to AME. PPro would freeze and I would have to force the program to close. This was on a project where I was just running out a bunch of interview clips for the director to look at. One of them had a audio effect (DeHummer) on it, and it was the one that was giving me troubles. I selected the audio and right clicked then "Render and Replace" then it would export to AME with no issue. Thank you for your well written response to this thread. While it may not have fixed the OP's issue, it did help with mine....
Thanks,
Phil

Media Encoder CS5 hangs during render

I've created a project in Premiere Pro CS5 (64-bit) on Windows 7 Pro x64. It's 28 minutes long. When I try to render it in Media Encoder CS5 (to YouTube Widescreen HD), it gets about 2/3 of the way through and then stops. It doesn't close, it just freezes. Not always at the same place (I've tried four times). If I click on Stop Queue, it asks if I'm sure and when I say Yes (click on "No," actually), it hangs and Windows presents its "Close the program?" dialog, followed by a dialog saying, "PProHeadless.exe has stropped working" and asking if I want to close that, too. I say yes and return to the desktop. I modified the render to VBR 2-pass from VBR 1-pass, to see if it would at least get through the first pass without hanging, but it didn't.
I've created dozens of projects with these tools, most shorter but some longer, and have never had this problem. Any suggestions? Thanks.

Hi Michael,
Sorry to hear you're having problems with Adobe Media Encoder. I'd like to get some more information about the problem so I can better understand your workflow, and potentially try to recreate the problem. For what it's worth, I often import files of different resolutions without any problem, so I want to find out what's different about how you're using AME.
Apologies for the long list of questions; the small details can be important.
-- After you import the first file, what else do you do in AME? Change the preset? Change the settings? Change the output destination?
-- What are the properties of the files that are causing the problem? You said it happens on "non-standard" files, but can you describe the specifications for one or more files that cause the problem? Please include file type, length, frame rate, frame dimensions, field order (if applicable), alpha mode (if applicable), and audio type and rate. If you know more the bitrate, both video and audio, that would be nice, too.
-- If any of the files are small enough, could you post a couple online that I could try on my machine?
-- How were these files generated? What application created them?
-- Where are the files stored? A local drive, a network drive, a removeable drive (USB or Firewire), etc.?
-- Which Adobe application or suite do you have installed? AME a limited set of options if you're using Flash or Web Premium compared to Master Collection, Production Premium, Premiere Pro, or After Effects.
-=TimK
-=Adobe Media Encoder QE

Media Encoder won't queue

I'm running the latest build of Premiere CC. I can export sequences without issue but if I try to 'Queue' and send to Media Encoder, it won't show up. Basically, Media Encoder will launch automatically as it should be no job actually get's added...It just sits there. I've waited close to 30 minutes with no success. The behaivor is identical to whenever I just launch Encoder on it's own. Thoughts?

I'm having a similar issue.
Essentially ever since upgrading my OS to Mavericks, Premiere CC can successfully "export", but it cannot "queue" into Media Encoder CC.
All that happens is Media Encoder launches and then it just sits there with a "Not currently encoding" status.
I've restarted, re-downloaded, and verified this issue on two separate machines running two seperate CC accounts.
This is becoming increasingly frustrating as it hinders our editing time, We used to be able to add sequences to the queue and keep on editing but now we must wait for each individual sequence to render.
Any recommendations?
iMac 27'' 2013
Mac OSX 10.9
3.5 GHz Intel Core i7
32 GB 1600 MHz DDR3
Adobe Premiere Pro CC
Version 7.1.0 (141)
Adobe Media Encoder CC
Version 7.1.0.174 (64-bit)

Premiere freezes when sending to Media Encoder Queue

Hey guys,
This issue is on all of our computers (Mac Pros and 27" iMacs) and happens on 40% of attempted exports through Media Encoder.
Here's our new workflow:
- Export TImeline (Command + M)
- Send to Media Encoder (Queue button)
- Media Encoder Opens and Premiere gets hung on "Preparing Data for Export" dialogue
- Force Quit Premiere and get a dialogue that "There has been a serious error and Premiere needs to close"
- Reopen Premiere and try again – usually get a clean export (or two on a good day) before it craps out again
We've sort of gotten used to it but I'm wondering – anyone else having this issue? It's getting annoying (and embarrassing when you're in a client session).
Doesn't matter what timeline setting or what's on the timeline. Also doesn't matter what version of either program.

I am having the same problem (see Premiere now freezes on Media Encoder Queue)
I am on 2014.1 of both programs (8.1.0 on premiere, 8.1.0.122 of AME). I know an update just came out today, but it seems to be just a RAW photo update.
Mine hangs when premiere is "Preparing Media for Export..." It launches AME and AME boots up fine... so from where I sit, it looks like a Premiere problem as it's compiling the project file to export.
Neither "import natively / non natively" or GPU acceleration help. However, I wouldn't expect them to, given this seems to be a premiere problem, not an AME problem.
That thread does not apply re: nView.
R

Media Encoder 2014.1 Will Not Que

Since the recent update to Media Encoder 2014.1 and Yosemite media encoder will not render premiere sequences. Here's what I'm doing.
Opening Media Encoder
Add Premiere Pro Sequence
Click Render
... Nothing happens, it gives me the option to stop, but never actually starts.
I can't quit the application. I must force quit.
When I export from premiere and choose to add to media encoder que nothing happens. Media encoder starts but I have to force quit.
Exporting from premiere works fine.

Ok, I let it run for about 6 hours. This is what it looked like the whole time:
It was working though. When finished:
So that's good, but why won't it show me the progression of the task? I like to know how much time I have remaining and see the preview at the bottom like I used to. I have "Show Que Elapsed Recording Time" checked in pref.
And finally, I still have to force quit.
Further help would be greatly appreciated.

AME CC 2014: "Adobe Media Encoder has encountered an unexpected error and cannot continue."

Adobe Media Encoder CC 2014 on MacPro "mid-2012" (MacPro5,1) running OSX 10.9.3 and getting this error when trying to launch Adobe Media Encoder CC 2014:
Adobe Media Encoder Error
Adobe Media Encoder has encountered an unexpected error and cannot continue.
Have uninstalled, reinstalled. Checked and fixed permissions numerous times. Tried removing all plugins and that didn't fix. Also tried editing the text listings within the .app for OpenGL and CUDA to remove all cards listed - that didn't fix anything either.
At this point it's uninstalled and "hopefully" everything will point to CC (non-2014 version). Adobe Media Encoder CC works fine. Adobe Media Encoder CS6 works fine.
Cannot find any other reports of this issue.

Progress in trying to fix. This workaround was NOT successful on previous attempts, but now appears to be working. Seems like the trick was to have AME CC 2014 started and open BEFORE doing any of this? As always, make sure all of your permissions are set properly - had done that numerous times previously. My issue was NOT directly permission related.
Navigate to the following folder:
You may see a file SHORTCUT that is invalid called "Presets":
Remove/delete this file. It's a broken shortcut.
Move a folder of .EPR files into the "8.0" folder. Call it anything except "Presets". Go to AME CC 2014 and quit. (I was greeted with another crash message.)
Open AME CC 2014 again. Your presets will not be loaded yet, but you should see an XML file that was created in your new folder like this:
Delete this file.
You should see a new folder also created by AME called "Presets". Move your .EPR files into this folder and delete the original folder. Quit AME CC 2014. (I was greeted with ANOTHER crash message.)
Open AME CC 2014. Your preset files should be there at the top under the preset browser:
Probably a good idea to keep a copy of those .EPR files elsewhere

Ae cc (2014) render queue vs media encoder

Similar Messages

Maybe you are looking for