Quantcast
Channel: Adobe Community : Popular Discussions - Adobe Media Encoder (AME)
Viewing all articles
Browse latest Browse all 7030

AME Encoding is Rubbish

$
0
0

I have not gotten an satisfactory explanation on why AME CC2014 is absolute rubbish at encoding a ProRes422 files that is 58 minutes in duration. I was on another forum thread, however the fix works for Windows but NOT Mac.

 

In CC it takes between 10 and 15 minutes. Right now in CC 2014 the EXACT SAME FILE is at 16 plus hours. This is the same whether I encode form Premiere Pro or from Media Encoder. The clips in the timeline are ProRes422 files with NO transitions, effects, generators, After Effects comps. It is a software render. If I choose OpenGL it makes absolutely no difference.

 

Macintosh

Processor 2x2.4 GHZ Quad Core Intel Xeon

12 GB ram

ARI Radeon HD 5770 1024md

OSX 10.9.3

 

Since the project is in Premiere Pro CC2014 I'm stuck. I tried to copy my sequences and put them in Premiere Pro CC but that doesn't work. I have deadlines and this glitch or whatever is costing me money. Since I pay every month for a service I expect it to bloody work.

 

Is Adobe going to reimburse me for the extra time and energy I have to spend dealing with ridiculous issues that should have been dealt with in a Beta version before being released onto paying customers who are having clients breath down their necks because of deadlines not being met? Do you really think a client cares that a software glitch from Adobe is costing them money by not being able to have their show ready for broadcast?

 

I want a bloody fix or answer to this problem. If there is now then tell me how to get the few projects I have in CC2014 back to CC. Because right now I see no reason to be paying every month for software that DOES NOT WORK.

 

Hear is a screen capture of the ridiculous encoding time and my Activity Monitor.

 

SG-01a.jpg

SG-02a.jpg


Viewing all articles
Browse latest Browse all 7030

Trending Articles



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