Quantcast
Channel: Adobe Community: Message List
Viewing all articles
Browse latest Browse all 80307

Media Encoder Slows Everything Else Down

$
0
0

Hello,

 

I'm a happy new user of CC 2014 for the most part, I'm just having one pesky issue so far.  Whenever I transcode with AME CC 2014, everything else on my CPU becomes unbearably slow.  Most of my searches for this issue have turned up complaints about AME itself being too slow.  I'm having the opposite problem.  AME is ripping through transcodes like no one's business, and I'm very satisfied with its vastly improved performance from Compressor and other older software, but I need to be able to do other things while I'm transcoding!  (NOTE: I was not experiencing this issue with AME CS 6)

 

Based on some advice I got, I made sure that my Renderer was set to Mercury Playback Engine Software Only and not Mercury Playback Engine GPU Acceleration (OpenCL).  Unfortunately, I notice no change between the two options.  I tried changing the Memory allocation in Preferences as well.  Here is a screenshot of my CPU's memory usage across two test transcodes.  The first hump shows ~96% CPU usage by AME when I allocate 10 GB to AME and 6 GB to other software.  The second hump, also ~96%, is from allocating 1 GB to AME and 15 GB to other software.  No improvement noticed when tweaking Memory allocation settings.

Screen Shot 2015-01-16 at 10.35.43 AM.png

 

When AME is transcoding, my Wacom tablet (USB) slows down until the cursor is moving through sludge, appearing and reappearing constantly.  Interestingly, my bluetooth mouse does not experience the same decrease in responsiveness, but basically all other software becomes unusably glitchy and slow.

 

I like the new AME render speeds, I just want to strike a balance between fast rendering and multitasking in other video software.  Any ideas of how to fix this problem?


Viewing all articles
Browse latest Browse all 80307

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>