Skip to main content
DrStrik9
DrStrik9
Inspiring
July 5, 2017
Answered

Media Encoder CC 2017 FAILS when exporting from AE.

  • July 5, 2017
  • 2 replies
  • 1542 views

I have an AE file containing multiple layers of text, which render fine in ME, but the several VIDEO portions just render the dreaded COLOR BARS, but ONLY when EXPORTING the AE file to ME.

Booting ME first, then manually IMPORTING the AE file takes several minutes, but it eventually DOES open, and ALL the parts are rendered properly, although EXTREMELY SLOWLY. But using the IMPORT method, I can get the final video.

TWO QUESTIONS:

1. What can I do to get ME to work properly when EXPORTING from AE?

2. Are there some AE and/or ME Preferences settings I need to set to get ME to actually work when exporting from AE?

Any help would be GREATLY appreciated!

Thanks!

--

MacPro, MacOSX 10.10.5, 32 MB RAM, 10+ TB disk space, AE v. 14.2.1.34 (25% used of 32.0 GB), ME build 11.1.2.35

--

This topic has been closed for replies.
Correct answer DrStrik9

Well, the file never did import last night. I gave it the entire night, with no success.

WHY?


I finally chatted with Adobe Support in India. It seems that "some" dpx files fail to import from AE to AME. This seems strange to me, because ALL of the dpx files in my AE project come from the same source. In other words, they are all coded exactly the same, but only SOME of them show up in an AE export to AME.

This is a major BUG in AME. And it won't be easy to fix, because of the inconsistencies in how AME deals with dpx.

I finally got AME to render this AE file properly by first rendering a multi-GB H264 version from AE, then manually importing that file into AME and doing the final render there.

Live and learn.

One clue to solving this dpx bug in AME might be to look at how both AE and Photoshop handle dpx. Neither of them have ANY problems with ALL of these dpx files. A second clue to solving the bug might be the visible SIZE of the dpx files. ALL dpx originals in this video are rendered from the same source at 1920x1080, but only the ones reduced in size in AE are acceptable to AME. AME is not able to import 1920x1080 dpx frames which are displayed in AE at 1920x1080.

2 replies

R
rab2638
Participant
January 2, 2020

Can you provide more details on how you resolved this issue by first rendering in AE? 

DrStrik9
DrStrik9Author
Inspiring
July 6, 2017

Should I look elsewhere in this forum to get a good answer to this question about AE>ME export fails?

Is it just me? Is it a bug or am I just doing something stupid?

Thanks for any intelligence.

DrStrik9
DrStrik9Author
Inspiring
July 6, 2017

When importing a slightly shorter AE file into Media Encoder (similar content with a different sound track), so far it's taken over 30 minutes just to import! But I only THINK it's importing! The progress bar has said 100% the entire time. This is seriously counter-productive. Why is it so difficult (time-consuming) to get Media Encoder to do its job?

Total import time for one 3.5 minute video = I gave up after half an hour

Should it take this long? Someone please give me a hint.

Here are a few helpful tips for Adobe:

1. Give us some kind of working ME Import progress bar, to let us know things are still working (this progress bar has shown 100% for the entire import time of 30+ minutes).

2. Fix AE Export to ME!

3. Respond with helpful info to problems like this one in the forums.

DrStrik9
DrStrik9Author
Inspiring
July 6, 2017

So after giving up before, I decided to just let ME do its thing with a manual import from AE, even if it takes all afternoon and night.

Along the way, I finally opened up OSX's Activity Monitor, and ME does indeed appear to be "doing something." So I won't give up this time. It's just an unsettling mystery as to why it would take so LONG just to import a short video file.

A closer look at Activity Monitor reveals that ME is using a TINY fraction of 1% of CPU power (like .01% to .03% average, sometimes jumping up to a whopping HALF a percent!). This might be a hint as to why this "simple" import is taking so long ...

I'll report here how long this simple import finally took, IF it ever finishes ...

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices