Skip to main content
Participant
Jul 31, 2013 2:27 AM UTC
Answered

Adobe Media Encoder pausing rendering while working in Premiere Pro

Hello everyone,

So I am redering a video in Adobe Media Encoder and at the same time I am editing a new one in Premiere Pro.

I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.

I have no clue why it does that because the Premiere Pro window has the focus, not the AME one.

Has anyone ever seen that?

I use Windows 8 and Adobe CC.

RickBRockCorrect answer
Participant
Jul 31, 2019 3:02 PM UTC

Here is your answer...

in PremierePro Preferences (I'm using CC v12.1.1)

Preferences

Playback

uncheck "pause Media Encoder queue during playback"

click <OK>

enjoy your extra beer money caused by double efficiency

30 replies

RickBRockCorrect answer
Participant
Jul 31, 2019 3:02 PM UTC

Here is your answer...

in PremierePro Preferences (I'm using CC v12.1.1)

Preferences

Playback

uncheck "pause Media Encoder queue during playback"

click <OK>

enjoy your extra beer money caused by double efficiency

Translate
Participant
Sep 18, 2019 10:55 PM UTC
Wow. Bless you.
Translate
Inspiring
Jun 29, 2016 6:46 PM UTC

Is there a work around for this? I mean, isn't a major benefit of Media Encoder the ability to continue working while exporting? It's impossible to work in premier while using Media encoder if the pause buttons are linked.

Translate
Legend
Jun 29, 2016 7:39 PM UTC

AME uses a lot of system resources.  So does PP.  Adobe correctly assumes that PP is the more important program, that AME should give up the resources it's using so PP can use them when it needs to.

Practically speaking, you can't "work around" limited resources.  Even if you get more resources (better hardware), there is still a finite amount of power available.

Impractically speaking, you could build a "super-computer" with twice the power that either program alone would be capable of using.  That might do the trick.

Translate
Inspiring
Jun 29, 2016 7:44 PM UTC

hmm.. I get it but I'm working on a new Mac Pro with 8 cores. I know I have enough power for both to run fine. Seems silly I still cant utilize my computer even with the new update.

Translate
Known Participant
Jul 30, 2015 3:59 AM UTC

I vote for ANNOYING! But at least now I know what the heck is happening.

Translate
Participant
Aug 14, 2015 7:24 PM UTC

Hi - I was having the same trouble with mysterious encoder pausing - Running PP on an iMac with 16gb RAM, NVIDIA GeForce GTX 675MX 1024 MB, 3.4 GHz Intel Core i7 & I had been encoding on AME while editing hour-long projects with no trouble, then this started happening. 

Quitting PP and letting the encoder work, then restarting Premiere seems to work.

Translate
Known Participant
Aug 14, 2015 8:44 PM UTC

It's simpler than that. It's hitting the space bar while you're editing. What I wish they would fix is EVERYTIME an Apple update comes out Cuda drivers get disabled and have to be reinstalled!!!!

Sent from my iPhone

Translate
Alex_-_DV411
Participating Frequently
May 17, 2014 7:38 AM UTC

I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.

Wondering if there have been any developments with that. My facility is contemplating switching to Pr (from FCP7) and the ability to export while still editing is a significant factor.

One suggestion is to start AME and then close / reopen Pr. Can anyone confirm this works consistently with no side effects?

Thanks!

Translate
Participating Frequently
May 17, 2014 8:59 AM UTC

I stumbled across this thread because right now I'm doing exactly that. Rendering out a sequence in AME and working on another in PP.

I closed PP to one screen and put AME on another to test. Hitting the spacebar on the PP side had no effect on AME. It soldiered through.

However, with both open, AME will just pause for some reason and I'm away from the computer.  I don't know the reason but it doesn't seem to be the spacebar.

These are one hour timelines, effect heavy, so it shows about 5 hours to render so time may be factor. Maybe it just get's bored. Other than that everything working flawlessly, with no mixed codecs though - all ProRes.

Specs - Mac 8 core, 40gb Ram.

Translate
Alex_-_DV411
Participating Frequently
May 20, 2014 7:43 AM UTC

Thank you, very helpful. If you have a chance to test that (AME getting bored) on shorter / simpler timelines, that'd be great.

Translate
Participant
Jul 31, 2013 1:56 PM UTC

You say your CPU/HDDs are underutilized - I find that hard to believe while encoding. Does encoding only use 10% of your cpu resources and not touch your GPU at all?  What are your system specs?  I'm fairly certain that most people would not expect to be able to work on much while encoding since it typically consumes a lot of system resources to get the job done.

For example...at work my workstation is an i7 2600k (4core/8thread - 3.4ghz), 16gb ram, 5 seperate hdds and a GTX670.  If I encode (h.264) and try to do anything else on my machine...the other tasks crawl.  Just look at your performance tab in task manager (if on windows) when encoding.

Translate
Inspiring
Jul 31, 2013 4:43 PM UTC

Hi jthebes

I have an i7 3930k 3.20Ghz which has 12 cores.  Encoding 2560x1600 HD is utilising between 35 and 40% of overall availability, the task is split with some cores running at 100% and others not.  Also my GPU is a GTX680 with 2GB of memory.

When I am encoding, I can play Mass Effect 3 multiplayer in full resolution and record at 60fps at full size with no impact on performance.  The only time I experience any kind of slow down is when the disk is becoming full but otherwise excellent.

I put my machine about average compared to some of the specs you see available for editing.

Translate
Inspiring
Jul 31, 2013 5:32 PM UTC

btw the reason you're not at 100% load is because AME can't render the raw frames fast enough to keep up with the encoder. If you used an encoder like x264pro which has some uber-intestive compression choices for better quality output it would peg to 100% on all cores.

One thing that makes running AME and PPro concurrently difficult is that the CUDA driver from nVidia has a horrible time time slicing the two actions. I'm really surprised that when you're playing ME3 that background AME rendering doesn't make it stutter. That comment is gated on the assumption that you're even using the GPU in AME - which can only happen if you Queue a sequence from PPro and it has resizing and/or filters that have GPU acceleration.

Translate
Inspiring
Jul 31, 2013 3:24 AM UTC

That is as designed.

There is a feature request to have them run concurrently but there are major technical hurdles.

Translate
dsfsdsdfsdffdsf
Inspiring
Jul 31, 2013 8:46 AM UTC

Argh, that 'feature' is soo annoying! Given one can simply unpause the AME render WHILST playing the Premiere timeline without issue I'm not sure what the technical hurdles are exactly, but I'd love it to be addressed. Most of us are using CPU's and HDD's that sit underutilised a lot of the time. When cutting and encoding longform jobs it's particularly annoying since I usually end up just tabbing constantly between the two programs to keep them both working when I know they can coexist perfectly happily together..

Now cutting in Premiere whilst After Effects is rendering is another story..

Translate
Inspiring
Jul 31, 2013 11:51 AM UTC

This was a feature that I hoped would be addressed in CC.  Sadly it hasn't so I guess we will have to put up with it. 

As you say PaulM, I am not sure why this cannot be changed.  I suspect something within the Dynamic Link Server gets confused as to where the space command is being sent.  I have noticed that the behaviour doesn't seem to happen straightaway, or not on my system anyway.  It usually manifests within an hour of working within it and then happens constantly.

Oh well, hopefully it will  be sorted out at a later date.

Translate