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.

Similar Messages

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder? Thanks! bedrijfsfilm Companyfilms

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder?

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
Anyone else got that too with Premiere Pro CC and the new Media encoder?
Lack of detailed info makes your question impossible for anyone to answer you!
eg. ...."Doctor it hurts...anyone else got something that hurts?"

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.

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.

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.

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

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...

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

Why is render much darker in media encoder

When I render direct to Media Encoder from After Effects, the results is much darker than the original.
If, however, I render from After Effects alone then it's faithful to the original.
Anybody else come across this?
It's annoying as I'd like to avoid a two stage render process.

Also, do you have color management enabled for your project in After Effects?

Using Premiere CC and Media Encoder CC at the same time

Is this possible? Doesn't seem to be. Media Encoder bails on every job as soon as you try to render anything in Premiere. I guess they don't play nice together, which is surprising. I was hoping that Media Encoder would pause and wait for Premiere to finish a render. Instead it dies on every render job, creating 0 size video files... while making a sheep bleating sound.
Is this a GPU issue? I have 2 nVidia cards, a 770GTX and 560GTX. (Windows 8.1, 16gb RAM, 3770k CPU)

As soon as I initiate a render in Premiere, Media Encoder bleats, and all subsequent render jobs bleat and produce 0 size video output files... even if I quit the Premiere render before Media Encoder reaches some of those render jobs.
I suspect this is a GPU sharing issue.... but can't be certain.
What do you mean by new install? Did I install it (AME or Premiere) recently? No. I've had Creative Cloud on my machine for almost a year, and both Premiere and Media Encoder have been updated periodically.
To my knowledge they have never worked together, but I only started using the queue feature within Premiere recently, so I haven't used AME until recently.

Premiere Pro CS4 Export fails with Media Encoder CS4 "Encoding Failed"," Could Not Read From Source.

There has never been a history of Adobe CS3 installation on the brand new MAC Pro I am using prior to installing Master Collection CS4, despite other posts claiming that chief cause of this issue is a previous CS3, Beta or trial installations of previous versions. I simply had a straightforward installation of CS4 and have had trouble since day 1.
I have uninstalled and reinstalled Master CS4 three times, two times with the action script cleaner for CS4. I tried changing Adobe Cache folder locations to alternative drives. I ran shift start many times to correct any inconsistencies and corrected for permissions using disk utilities repeatedly. All updates have been installed and I am still getting the same error when exporting my timeline to Media Encoder CS4, be it a large High Definition project or a small one consisting of few stills.
No matter what presets I chose, the job appears as one of the items in the render qeuee of Media Encoder CS4 and sits there with the status WAITING until i hit Start Queue. When I do, it still says WAITING under Status and at the bottom corner of the window it reads : Loading "project name.prproj" and after an average of about 6 minutes, a yellow caution sign appears. No render whatsoever takes place. When I click on the yellow caution sign, it reads a log of all errors in connection with each job, including the ones that have gone before it. Here is one:
Start of the Error Paste
- Source File:/users/myname/Library/Caches/TemporaryItems/test.prproj
- Output File:/ users/my name/Documetns/Adobe/Premiere Pro/4.0/Sequence 01.mov
- Preset used :NTSC DV
- Video:
- Audio:
- Bitrate:
0 Encoding Time: 00:33:01
Sat Mar 21 17:12:25 2009 : Encoding failed
Could not read from the source. Please check if it has moved or been deleted.
END OF ERROR Paste
Please any gurus out there know how to troubleshoot this damn thing on Mac, I really appreciate it. I have not yet encountered any posts of Mac owners with no previous CS3 installation having this issue. I am in the middle of 3 projects with tight deadlines and need your urgent help. THANK YOU!

Hello There,
I resolved the issue through a simple process of elimination. So simple in fact I wonder how I missed it. Since there has been no history of prior CS3 installation on this machine and every conceivable trick was applied to resolve the problem (refer to my original post earlier in the thread) ending in frustration, the problem had to reside in a factor or series of factors that were only present in this machine. Of the two remaining causes different in compare to other machines, I had to look into the possibility of any hardware and/or software conflicts. After all, this very same installation works perfectly fine on my colleague's Apple Macbook Pro and several Windows machines.
It turns out that I had installed Pro Tools on this machine that comes with all kinds of optional plug-ins in the so called ignition pack. One of these optional plug-ins is called IZOTOPE (three varieties include Spectron, Trash and another one that escapes my mind). They were all lite version licenses that would automatically pop up on their own when you would start a program where they had been residing. One such program where an association existed was indeed the Premiere. An annoying dialogue box directing you to buy the full version when you would start the premiere would refuse to go away. Sometimes it would even start on its own culminating in a a permanent dialogue box.
The cause of the problem was right before my eyes and I had overlooked it. Once uninstalled using IZOTOPE clean uninstaller on step 4, the problem was resolved. Projects are now loading very fast into the AME and encoding begins in earnest. I have never had any issues ever since.
Long story short, if you have any plug-ins specially the ones that are loading upon the start of any program or the ones that reside inside the premiere or the ones that start on their own independently, they could be one of the highly probable causes of this error. I have seen other similar posts complaining of plug in folders inside premiere that needed to be moved to resolve the issue for instance the ones that needed to be moved to AE folders. If you are a plug-in admirer, I would suggest to look into them seriously.
On the side note, many combination and causes may lead to the same error. I am not claiming that this is the solution for everyone.
It must also be noted that I applied the trick of creating a shortcut of Premiere (and naming it exactly as such) and dropped it into the Adobe Dynamic LInk folder (even though this was suggested for windows)and have changed the adobe Cache locations to an alternative folder on a separate drive. I haven't been able to establish conclusively if the latter steps are also essential in fixing the error on MAC but I can confirm that since the latter steps were taken before the uninstalling of Izotope plug-ins and i still had issues, probably uninstalling those plug ins or finding a way to move them to a place where they don't interfere (if you absolutely need to keep them) is the one essential step that solved the problem.
Hope this helps.

Media Encoder stalls when using a 2-pass BlueRay H.264

Hello,
This has happened twice, I send the PP timeline to Media Encoder, select a 2-pass encoding, BluRay H.264, and the encoding process starts and runs fine. Three quarters of the way through a 3 hour squence, encoder stops encoding / stalls, and the timer for how long it has left to go, now starts to add time. Before the 'stall', my CPU was working hard, all 8 cores, when Media Encoder stalls, the CPU workload is nil.
If I take the exact same PP squence and setup just a 1-pass encoding using the H.264 Blue Ray codec, all is well, Media Encoder completes the job.
Any idea why the 2-pass encoding doesn't work? I am using CS6 with all updates installed.

I know there WAS a bug http://forums.adobe.com/thread/944584 so it may be that bug was not 100% fixed in CS6

Media Encoder renders test pattern

CC 2014 - latest build. When I choose to render with Adobe Media Encoder from AE, the Media Encoder renders a test pattern, not the video in the project. The files are on an external drive (TIFF sequence), but the timing for the project is correctly shown in the Media Encoder so I can see that that is correct. What s going on here? Same thing happens with any/all project(s).
Thanks for the help.
-dm

Try adding your image sequence to a Premiere Pro sequence and use the default dissolve to add the fade in and fade out there. Send that to the AME or render from Premiere and see if that works.
If it does then try just putting one of your images from the tiff sequence in a new AE comp and see if that will open in the AME. If that doesn't work let us know. You may have found a bug. I just tried it with my system and tiff sequences come into the AME just fine.
Are you sure that both the AME and AE are up to date.

Problems rendering Every-line Composer texts with Adobe Media Encoder

I find the text paragraph setting "Adobe Every-line Composer" a huge time saver when dealing with large amounts of text in after effects. I rarely have to do any manual tracking or line breaks to make it look good, as opposed to working with the standard Single-line Composer.
The problem is that when I render through Adobe Media Encoder (which I'm forced to do since they removed H264-mp4 support from AE:s internal renderer) the text is treated like single-line composed text. So the final render doesn't look like my AE project.
I've found two solutions to this problem:
1. Render a lossless video file in the AE renderer and then compress it with Media Encoder. This takes more time and HDD space, and it doesn't allow me to continue working in AE while rendering.
2. Only use Single-line composed text and make all adjustments manually, the old school way. This would not be a problem if I had not already used, and fallen in love with, the Every-line option.
Is there anyone that can think of a third, and preferably better, solution?
I use the CC 2014 versions of AE and AMC.

No, the text doesn't animate at all. It's just a normal static text box. The text part is extremely simple. All animations are done in other layers and pre-comps, combined with pre-rendered 3D graphics from Cinema 4D, rendered as image sequences. My problem is a bug, plain and simple. Or perhaps you could call it a "lack of feature support" or an "incompatibility between AE and Adobe Media Encoder".
My problem appears only when my AE project has text boxes with the "Every-line Composer" option enabled (press the menu button in the Paragraph window to find it), AND the project is rendered through Adobe Media Encoder, no matter which output format I use. I have no problems what so ever inside of after effects, or when rendering Single-line Composer text in AMC.
So, the problem is that Media Encoder doesn't recognize Every-line composed text. Instead it changes it to Single-line composed text, messing up text tracking and line breaks.
To clarify: the Adobe Every-line Composer is analyzing the entire text box instead of only the current line. That way it can automatically change the tracking of individual lines to better distribute the line breaks and build a better whole, avoiding those stray words on the last line for example. Extremely handy, if you could only render it.
I never wrote anything about animating text or that the codec is related to the text problems in any way. AMC is the problem. The codec is only a secondary problem since its the lack of mp4 H264 support that forces me to use Media Encoder in the first place, instead of using the AE render queue as I did in previous versions of AE. I like many things about rendering through AMC, like being able to continue working in AE while rendering, but there are still way too many glitches. And of course, there's the inability to render flv-files in AMC CC 2014, and Adobe's inability to provide a solution other than "Use an older version of AMC". Flv is their own damn format for christ's sake.
Well, enough rambling.
To put it simple:
Has anyone had a problem with "Every-line Composer" in combination with Adobe Media Encoder? Did you find a solution other than the two less-than-perfect ones in my first message?
Thanks!

AE projects export Media Encoder = instant meltdown

System
Late 2013 iMac.
3.5 ghz iCore 7, 32 Gigs Ram
NVIDIA GeForce GTX 780M 4096 MB
Adobe CC - All up to date
Red Giant Plugins - latest
ME 7.2.0.43 64 bit
AE 12.2.1.5
From AE, send a simple Comp to Media encoder
Boom....Screen Flashes to black - mac has to be hard restarted.
There is no 3.
I have cleared ME prefrences.
Check Permission on Adobe Prefs Folder
This happens very time
Adobe. Please help.
Anyone else confrm this?
Thank you

There was a Red Giant bug in the Magic Bullet suite that caused problems with AME. Make sure you've fixed that.
Try a simple comp that is just a solid layer with no effects or animation and nothing else in the composition. If that works then give us all the details on your comp or try eliminating one effect at a time until you find the problem.

Send a render job to Media Encoder on another system?

Similar Messages

Maybe you are looking for