Decision is understandable - after all, you can export to AME render where you will find all the possible formats and codecs.
These formats are disappearing from the Render Queue but you can render fo them in AME using Composition/Add to Adobe Media Encoder Queue...
Sorry. In AME CC 2014 you can't export to flv and f4v so if you wish to render from After Effects to flv you have to use previous version of AME (AME CC).
Excuse me to say but that is REDICULOUS!!
If that was ment to change workflow and user Media Encoder, that would just be fine (even awkward but at least it would work..)
NOT being able to render out to FLV from AE CC 2014 at all, provides NO reason of updating...
There is NO format left to be used to EMBED video INTO FLASH!!!!
If one updates to new version, demanding of still keeping the old one is simply REDICULOUS!!!
WHY on earth this was decided? WHAT weird mind thought of this !!?!?
That is REDICULOUS!!
It's already started to gather some momentum and it would be good for you to voice your opinion in there to try and keep it going.
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:
See this for an explanation for the change regarding FLV and F4V and for the recommended workflow:
At my company, we still make flash banners. Lots of them, every week. I use the feature of creating text animation in After Effects. It has bundles of great presets for text animation, that can be used and exported as SWF. First, Adobe removes the functionality to import SWF into Flash CC. So I have to use Flash CS6 as well. Still need both though, cause I need to import Illustrator documents too (Flash CS6 doesn't support the latest version). And now with After Effects CC 2014, they remove SWF export all together...
At my job, there is someone employed doing kerning for text in Photoshop. For me to keep that perfect kerning for the Flash banner, I have to import the PSD to After Effects and then export the text layers as SWF to get that kerning preserved. I noticed it was possible to import PSD into the new Flash CC 2014, but the kerning was messed up on import.
Come on, Flash is not dead damnit! Why are you removing features that we rely on?
Adobe rage today...
I agree, back to 12.2 for me. I don't give a **** how Adobe says I should do my workflow.
I agree too. i always used h264 and flv. it's very very disappointed.
I agree too. i always used h.264
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.
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...
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.
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??
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.
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.
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
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
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.
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?
For transparency wouldn't you guys just use a png sequences? I'm somewhat surprised to even hear that people still use flash at all but as far back as 2008 I had developers telling me to avoid flv or f4v files at all costs and to instead use png files.
I think there's a lot of people who encode straight to h.264 from AE and a bunch of people using FLV. I can't understand that you, Adobe, took these encode option away from AE and justify this by saying "we didn't have time for it". You can see by the view count of this thread how many people this has affected and not in a good way.
I really don't like the fact that I have to encode to an intermediate format which takes space and time to sort out afterwards, when doing previews for clients.I don't like the roundabout to the goal. I would prefer to get the result I was after the first time. This is totally inconvenient for me. I put out tens of previews a day and this is really hurting my turnover time.
And I really don't like the fact that now if I ever need to use FLV video in some project, well... I can't. Did AME really change that much internally from the last version that you HAD to take FLV export away, or was there another reason? I don't get it.
Please add the h.264 render option back to AE. And you should really keep some form of FLV export somewhere in the package, or you risk losing some customers.
To date I've primarily been a Photoshop user and have dealt with years of mystifying UX and workflow changes, features that are useless to me added, and critical ones taken away (I'm looking at you Bridge, you worthless piece of garbage). Then, to add insult to injury, Adobe forum mods telling me I'm doing it wrong and should be jumping through more hoops to achieve the same results. Now, with AE becoming a bigger part of my work, I am sad to find, that the same culture of disconnected arrogance and myopia prevails on the AE dev team.
"Oh um user, you really want to be going through AME, because um technically speaking there have been many problems with the H.264 and MPEG-2 exporters in After Effects"
Oh really? Tell me more about my job. Tell me about my experiences exporting these formats directly from AE. Tell me how my client views my content, is it on a Mac, or a PC? Maybe it's on his phone, or her iPad. What kind of phone is it though? Tell me at what point in my process it's ideal to render. Tell me about other tasks I'm performing. Tell me about the resolution and the bit-rate my files should play at. Tell me the final application I will be using the footage. Probably broadcast right? Or is it web? Or is it PowerPoint? Wait, what if there is no final output? What if it's just pre-vis for some other application?
Tell me how to win over my clients; what's the correct method of presentation to engage them most impactfully? Tell me about how much time I have to render massive video files. Is it more time efficient due to the nature of my composite to render once because my file is super shallow and will render quickly or is it more efficient to render twice because my file is extremely complex with hundreds of layers?
That the deprecated formats were hidden away in the preferences menu is dumb and annoying. That this same preference would then be removed is despicable and petty and is further confirmation that Adobe has contempt for me as a user.
There is a way to do this... Render as MOV, Using Quicktime settings: H264, Audio AAC, Quality 10, limite the KB/s as you wish... Once rendered, rename the file from MOV to MP4, will still work on gadgets, smartphones, etc...
Cool, Thanks w3r! I'll have to try this. I'll still miss the WMV format though since PowerPoint doesn't support Quicktime . For all the perplexing and awful decisions Microsoft makes, WMV is actually a great format - tiny file sizes, looks almost loss-less, and widely supported - at least in the media spaces I need in my work.
I agree with the OP,
The problem is Adobe Media Encoder doesn't even work for H.264 in relation to exported AE comps! That is the real annoying and frustrating thing. When I export my after effects comp to render in AME (because I can no longer do H.264 properly in AE now) AME does not even export the videos correctly every time. And no, it is not my pc causing the issue or some weird settings, AME is just broke. It can't get the audio tracks correct and mutes stuff it shouldn't. It's a known bug with AME and it's very frustrating having to jump loopholes to try and get a simple MP4 video rendered when AE was perfectly capable of doing it in CS3, CS4, CS5, CS6, and so on.
I KNOW it's a AME+AE issue because if I import the raw 2 hour+ video and encode it to mp4 it has audio, but if I want to do any effects in after effects and use a comp to render to AME audio is muted. The real kicker is if I use the depreciated quicktime codecs in AE CC the audio is quite fine. So why should I be forced to use AME when it can't even import my AE comps correctly?
N7R, I'm not sure what is going on with your system but I encode H.264 every day from AE comps. I have been using AME for 95% of my rendering since Dynamic Link made this possible. It chugs away while I continue to work on AE so I'm spending very little of my day waiting for renders. I have never had the AME not add audio to a clip.
Make sure you look at the encoding settings. Make sure you review the documentation so that you are using the proper workflow.
The problem I have found is AME cannot render correctly when an AE comp is over an hour long. The audio begins to get cut off. If I have video shorter than an hour it's ok but anything longer this issue persists. I've found a lot of similar threads on this topic as well and it's the same exact issue I have with AME. So basically I cannot use AME at all for any video longer than an hour or I lose part of the audio unfortunately. Hopefully this bug in AME is fixed eventually, it really makes workflow hard when I have to find workarounds because I program can't render correctly.
Here is one of the threads describing the AME issue: Large video encode - only one hour of audio
Hour long AE projects??? Sounds like you are using AE as an editor and not as a tool to create short sequences and shots. I can't remember the last AE project that was more than 10 minutes. Most are just a few seconds, then the program is edited in Premiere Pro. The workflow and the rendering is far more efficient.
I'm not saying that an AE project over an hour should not correctly render the audio and it appears that there is a bug there. I'm saying that maybe an hour long AE project is not the most efficient workflow. Personally I can't imagine a single effects shot that is over an hour long and I'm not nearly a good enough editor to work on a project that I don't revise at least once. Changing the timing of a cut in the middle of an hour long AE project would be a nightmare unless there was only a few layers. The AE project I'm working on right now is a composite that is 9 seconds long with 42 layers and I'll probably trim that to 4 or 5 seconds in the final edit. While it is entirely plausible to cut the 15 shots in the sequence I'm working on into a sequence in AE I can't imagine trying to retime an edit in the middle of a project with hundreds of layers.
Render using mov h264 and change the .mov to .mp4... It works on mobiles and etc
@ Rick Gerard
I've been rendering my completed nested compositions in after effects for years. The intensive graphics and such I simply render as image sequences and then re-import back into AE and it woks like a charm making any heavy effects non-existent in the render process due to the fact I've got it all as image sequences. I see no reason I need to change my workflow now. AME just doesn't do what it should be and since they've stripped features of what AE used to have it forces me to change my workflow that I've been using for years. I've been able to render in the past my hour+ long pieces within a few hours and have it up and ready on youtube in the same day. I have no desire to use premiere pro when I never needed to use it before. I like having to only use one program to do the whole process. AME just needs to fix the hour long composition audio bug and things will be much better.
The new after effects CC quicktime plugin is outdated and not very efficient in filesize as say After effects CS5 and CS6 were. Changing the .mov to a .mp4 isn't even the issue here. It the compression size it now offers.
Point is, I'm not here to defend my workflow lol since that is off-topic from the OP's post and I'm not here to deter attention for this underlying issue: AME. I'm here to report AME has a bug and if Adobe wants to force us AE users to use an external encoder more I happily will if they make it so it can actually work with composition over an hour long. Also this issue isn't just related to AE, Premiere pro users have also reported similar issues so blaming my 'workflow' isn't the issue at hand. Sounds like it comes down to AME having problems at times unfortunately.
The quicktime plugin is way better than the simple mp4... You maybe dont
know all the settings.... You can fix the average bitrate and quality of
compress... Just put 10 on quality and change the maximum bitrate using
h264 and use acc ...
2014-12-27 21:41 GMT-02:00 N7R <firstname.lastname@example.org>:
After Effects CC 2014 - removal of H.264, MPEG-2, WMV, FLV, F4V, and
SWF exporters - WHY !? created by N7R
<https://forums.adobe.com/people/N7R> in After Effects - View the full
Agree - this is horrible. On a tight deadline on a new project using Flash, go to export FLV - cant. Yeah, thats helping my workflow.
And now, I have launched the previous version of AME - with FLV, and I can't import the comp into its render queue. Blood boiling.
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....
Dear members of the ADOBE,
I am deaf, I am from Brazil.
I ask you, who has respect for we want to use are H.264, MPEG-2, WMV, FLV and F4V. Because these are the best sizes.
I did not like who (Adobe organizers) take the flv, H.264, f4v, wmv.
Will be updated as before the version for MAC and Windows ...
I wait for your answer.
Thank you for your attention,
Fernando "HougHzinhuuu" Ferreira
Awful idea Adobe. I too send off mp4 reviews constantly.
Media Encoder is sluggish and isn't providing me with a fast streamline way to export files out quickly. Please help
I am a new hire at my company and FLV conversion is integral to the workflow that they have set. It is the penultimate step before publication and archiving. Adobe's recommendation for this quagmire is -
"If you do still have a need to create FLV or F4V files for some legacy workflows, then we recommend that you keep the previous versions—Adobe Media Encoder CC (7.2) and After Effects CC (12.2.1)–installed alongside the current versions."
My brand new machine (Macbook Pro OSX 10.10.4) never had the previous version installed, so this is not an option for me. Can you, at the very least, make the previous version available, warts and all?
> Can you, at the very least, make the previous version available
You can install all versions from CS6 forward through Creative Cloud.
If you have a creative cloud subscription then you have access to CS6, CC, CS14 and CS15. You just have to use the Creative Cloud app to find them and download them. Look under the second bar that says find additional apps, then move right and click the All Apps link to reveal View Previous Versions. That's all there is to it.