Skip to main content
Participating Frequently
June 21, 2014
Answered

After Effects CC 2014 - removal of H.264, MPEG-2, WMV, FLV, F4V, and SWF exporters - WHY !?

  • June 21, 2014
  • 23 replies
  • 65624 views

While reading the features of AfterEffects CC2014, I noticed the following:

"removal of H.264, MPEG-2, WMV, FLV, F4V, and SWF exporters from After Effects"

THAT IS IS REDICULOUS!!

NO FLV !?!?
WHAT DO YOU EXPECT USERS TO IMPORT INTO FLASH ??
IF no FLV export is available under After Effects CC 2014, there is NO WAY to EMBED an flv into flash !! (Linking is NOT always what is wanted!!)


NO H264 !?!?!
HAVE YOU GONE CRAZY ?!!?!?

YOU BREAK WORKFLOWS!!!!!!!!!!!!!!!!!

THAT IS REDICULOUS!!!


Any chance of restoring such features so that it makes updating to it worthwhile ?

    This topic has been closed for replies.
    Correct answer Todd_Kopriva

    added my post to that thread as well...

    Hope there is an official response to this issue that would justify wether we should upgrade at all...


    See this for an explanation for the change regarding H.264, MPEG-2, and WMV and for the recommend workflow:

    using Adobe Media Encoder to create H.264, MPEG-2, and WMV videos from After Effects

    See this for an explanation for the change regarding FLV and F4V and for the recommended workflow:

    removal of FLV and F4V export features from Adobe Media Encoder, After Effects, and Premiere Pro

    23 replies

    Participant
    October 24, 2014

    So Adobe says that they are not supporting .flv anymore.... But what about importing a video into the Flash timeline? Flash is not giving me an option to import a different type of video onto the timeline.. Adobe, are you going to release an update to Flash so that users can embed other types of videos? Please Adobe, listen to your customers. What solution will you provide to embed videos on the flash timeline? If you aren't going to do so, then please.. just say it.

    Participant
    October 9, 2014

    Adobe recommend us to use MP4 instead of FLV?? but it doesnt allow transparency, and i cant improt it into Flash.

    This "update" makes no sense for us, the designers/developers and it is converting what used to be an easy workflow into a really complicated one....


    Not cool Adobe

    MyPattayaPlace
    Participant
    October 3, 2014

    Again, adobe never seems to keep user friendliness in mind. The logic in their products is hardly ever intuitive, making the learning curve for new users long and frustrating. Googling this problem has lead me here, where others seem to be having the same issues as I have. Since I have no idea what AME is, I'll have to go and find that out to comprehend what the answer to my question might be. All I wanted is to export a 15 second clip in h.264 or mp4 format to upload to youtube. Instead of having that done hours ago, I ended up rendering a useless 2 GB AVI file that doesn't even play properly.

    Why not make a selection-box in the render screen, where users can choose whether they want to use the new "AME" option, or a deprecated selection of export options.

    Michael Star - My Pattaya Place

    KramSurfer_
    Participant
    October 3, 2014

    It's official.. I now use AE 5.5 more than AE CC 2014. ( I sadly did not buy 6 )...  I've hundreds of files, things interlinked and dependent apon others and pathing is critical.  

    The removal of these formats from the render queue is unacceptable.

    LiisaBr
    Participant
    September 16, 2014

    I couldn' t agree more! Looks like adobe's idea of upgrading is moving backwards.

    - This is a copy of my opinion already posted on my Facebook page, Twitter and all forums in which I participate -

    Makes no sence to remove compatibility. Not to mention that all over the internet, thousands of people are against this idiotic decision and I think they deserve to be heard, because, after all, adobe is making software for them. AME does a better job, they say. This is telling us what software to use. What's next? The clothing we should be wearing? Well, I don't care if AME does a better job. I was very happy with AE results and I think the decision is mine to make.

    Well, if that's adobe's position on this, then I say: keep your software and use it yourself. You surely aren't making software for us. If you were, it would have what we need and want. It doesn't have what I need anymore so it became pretty useless to me. I'll look for other options, that meet my needs. Meanwhile, you keep caring about big clients' needs and wishes and ignoring others. That's the best way to make room for others to fill the empty spaces and shine.

    Goodbye, adobe.

    Participant
    August 12, 2014

    I agree to everyone... bring back h.264 modules!!! It's ridiculous that's AE CC 2014 it's worst than CC version.

    I also have a problem that Media Encoder doesn't open in my mac!!!! How should I work??

    Fredericopdg
    Participant
    February 10, 2015

    I have the same problem here...when i try to export as "they" (adobe) want us to export, nothing happens....

    on After effetcs cc 2014 AND premiere pro cc 2014....

    none of them can actually open media encoder to reder the comp....

    thanks adobe!

    jcthompson dc
    Participating Frequently
    July 23, 2014

    ADOBE might as well just say, "We don't care if you use it or need it, we're going to make it as complicated as possible for you to get your job done. We will create impossible workflows for you, lowly customer (e.g. create an animation or a movie in AfterEffects that you will have to jump through hoops and climb mountains before it is compatible for insertion in an Adobe Captivate project.)

    We will then route you through endless loops of sub-standard, low-quality tech support in India that will never be capable of finding a solution for you... because we're cheap. We want to have a huge profit margin and we don't want to pay for quality support.. but we'll gauge you for our product line anyway. Oh, and our competition just isn't there yet... so you're stuck. HA. Suckers. Did we mention that we're moving backward in the development of some of our products? Yeah."

    CC 2014: HORRIBLE UPGRADE. Same for Captivate 8. What a WASTE OF MONEY, since I can NO LONGER GET MY JOB DONE.

    October 27, 2014

    I'm also in the same boat.  Is there any workaround to getting an animation with transparency out of After Effects and into Captivate?  I've done the steps of exporting to Quicktime, importing video frames into Photoshop, export GIF sequence, but Captivate 8 crashes every time I import these GIFs as animations.  It seems like SWF is the only viable format, but how does one get a SWF file?

    shagsman
    Participant
    July 14, 2014

    This is the worst ADOBE upgrade i've ever seen. In every way. Adobe, if you don't know, Upgrade mean is '' to improve something so that it is of a higher quality or a newer model'' not ruin it. Congrats...

    DoTheMath
    Participant
    July 3, 2014

    I find this to be absolutely ridiculous as well. I don't see why we can't just ADD the AME export features to our existing workflow instead of forcing them on us. I am constantly exporting to H264 for review directly from AE in a clean and efficient manner, and this workflow is not that. Often times I have multiple comps that I have queued up in the Render Queue with all my settings ready. I only have to tick them on, check the filename, and hit render for a new iteration of all of my comps.

    As it stands now, I have to re-export to AME every time I make changes to my comp, which copies another aep to my project location to be queued for AME. Not exactly streamlined, IMO.

    Also, this means I can't use any 3rd party scripts (BG Render) for command line rendering unless I want to render to the much less useful approved list. I MUCH prefer BG Render or command line rendering in general, as it's faster and lighter with verbose rendering. It also provides post render actions, like text, email, shutdown, sounds, scripts, whatever, which I find EXTREMELY USEFUL.

    Additionally, there is no way I would want to render a lossless file for a watch folder for each iteration of a project. That's just insane. Especially if I'm working off of the "cloud".

    If I'm wrong about how any of this works, please feel free to correct me, but I am not happy at all with this forced workflow.

    Participating Frequently
    June 26, 2014

    I agree too. i always used h264 and flv. it's very very disappointed.

    Participant
    July 3, 2014

    I agree too. i always used h.264