Questions

So I tried exporting my project from after effects multiple times, probably over 20 times and it would start to queue but then a little over half way done then it fails. Now when I try to export it the project dosen't even show up when media encoder pops up. ive already unistalled both after effects and encoder. can anyone help?

I am trying to queue up two very long exports in media encoder. One at a high bitrate  (140Mbps) and the same video at a more reasonable bitrate (30Mbps). Media Encoder states that the same two files are offline for each export, but they are clearly online, available and playable.I did the 12 hour export, only to find the files replaced by the offline media graphic. How do I fix this issue, or do I just have to export these files one at a time in Premiere Pro? 

Hi guys, just a silly question, but why is media encoder NEVER ever working like it should?I installed the latest version on a brand new mac, and like always with latest versions: the app doesn't import projects from after effects, and when it does, it says "failed' when trying to render.It also randomly crashes, and it takes like 10 minutes to launch. I've had this for years, with every new version. Now and then it works for a while, but most of the time it's really buggy. Am I doing something wrong? Or isn't it meant to work with AE at all?  Also my entire Mac seems to freeze when working with the latest versions of the CC software. (not necessarily ME, but PS and AE)    I tried to launch ME with the shift key but without luck. Does AE CC2020 work with previous versions of ME? Cheers and sorry, a bit frustrated, that's all.Joost 

Please, help. I have some particular video clips (mp4s that I think were shot on a Galaxy S in 2010) that lock all the Adobe apps at particular time stamps. The Adobe apps become completely unresponsive and have to be terminated by OS brute force. For comparison, Windows Media Player plays the videos through without incident. I've tried processing the videos on each software, CUDA, and OpenCL rendering with the exact same results. It also locks in the older Premiere 2019 (did not test 2019 AE and ME). It also locks in Premiere on another computer with a different video card ("different" but both cards are made by NVIDIA in different generations of Dell laptops).Playing, scrubbing the playhead through, or exporting/encoding all cause the locking at the same point.I re-encoded one of the clips with Windows Photos video editor and then it worked in the Adobe products. But I have many(!) of these clips for this project. I am happy to provide one of the locking clips (the sma

Hello, I'm KazI use visual software "Ai" by Avorites, so I'd like to export movies to its orignal fomat(codec "AIM").I dawnloaded AIM bundle, following a tutorial in Avorites I pasted the bundle to application support>adobe>plug-ins>common>7.0>mediacore. but it didn't work.How can I do? Please help.   Title edited by Mod

I've started experiencing this after 2020 update. AME and Premier 2020 unexpectedly shut down the system completely off, while exporting. System:  i9-9980xe OC @ 4.3Hz ASUS SAGE X299 /10G 128gb DDR4 2xQuadro RTX 8000 / SLI enabled. 1300 Watt PSU  Custom waterloop 2x radiators and 8 fans.   I have run multiple stress tests on the system - longest at 5hrs. At 100% CPU and 100% GPU simultaneously temps are ~65-70C for CPU and ~60-70C for both GPU at 900-1050 watt max draw (I have UPS unit to tell the load).  So it is not Temps or PSU (power) issue.   The system works just fine rendering Vray scene in Maya at 100% load on CPU and GPU. The crash only happens when encoding in Adobe. Please help! Thank you!   Title edited by Mod

I recently upgraded my macbook pro (2010) to High Sierra and changed my internal hard drive. After editing a sequence in Premier Pro and exporting to Adobe Media Encoder, It's taking much much longer then prior to the update. A sequence that would take 1 hour or so is now taking 7-8 hours. Never this problem until the OS update. I tried encoding in all different codecs. I was using the video preset, Vimeo HD 1080p 29.97. Could the OS update being causing this issue? Thanks, Michael   Title edited by Mod  

I just updated to the 2020 versions and when I queue an export from Premiere Pro into Media Encoder, the export fails and I get the error message: "Could not read from the source. Please check if it has moved or been deleted." However, the source file is present in the directory listed and nothing is wrong with it.   I thought a potential workaround might be to open the Premiere Project directory in Media Encoder and select the sequence there. But when I do that, even though exporting seems to work, Media Encoder doesn't apply the audio filters I've used in Premiere!   Please help! Thanks.   Title edited by Mod

I use Animate and it would be a "feature" if ME would be able to output FLV. Any roadmap to introduce it?

It wont work, since the last 2020 update! difficult to open and once opened by luck it doesnt work. Must say I am getting incresingly tired of all hickups and glitchis!  and when you do this, filming and photography for a living its just impossible!   Title edited by Mod

Hello everyone, I tried asking this in another thread, but seeing as how that question hadn't been answered by anyone in a year I figured I would start a new thread.  I am trying to convert AVCHD in Adobe Media Encoder to .mov files. When I do, about 3 out of the 54 clips have audio all the way through, the rest either drop the audio after a few seconds or the audio is completely out of sync. With one, the audio is from a totally different clip altogether. I am intermediate user but this is beyond me and I am not as great with understanding codec's and the benefits/weaknesses or usage of each. I tried the clips back in the camera and they play with full audio, no drops, and no sync issues. So something is happening in the export process. I was following this tutorial that recommends exporting it with Apple ProRes 422 and I tried it with 422 HQ as well. The footage from my main camera is .mov so that is why I was converting it to be the same. 

So, I'm sittin' in front a Mac with High Sierra 10.13.6, using Media Encoder 13.1.5 (CC2019). GPU is a AMD Radeon Pro Vega 56. When I'm rendering a video, neither using GPU acceleration Metal nor GPU acceleration OpenCL seems to actually fire up the GPU. Shouldn't it be like cooking around at about a 100 %?... But the GPU activity window shows her almost idle, being bored to death... what wakes her up though (activity going up to very high) is e. g. opening a YouTube Video and watching it full screen.   So it seems like i can chose GPU acceleration... yet, it also seems like it doesn't actually use it. The only thing google shows me about this topic is people not beeing able to choose GPU acceleration at all, but that's not my problem.    Same problem when exporting from Premiere Pro directly.   Any Ideas?   Title edited by Mod

I have a lot of effects from Rampant Design, which in large part are short mov clips of the effect which had been filmed live on RED cameras. Since going to the latest CC release of PR & AME V14.0, AME is just struggling to render the Rampant mov effects. Sorry to dis Adobe, but man it's always something with these upgrades. Which is typically why I hardly ever work in a recent versions.   I'm guessing this has something to do with the recent dump of support for mov encoding - however, about 30 instances of Rampant mov effects rendered just fine, until the very last one in my hour timeline. I've tried toggling the Enable on the mov effect, then it renders fine. Here's the error, generated by just dragging the mov file into AME and starting a remder to mp4. Any ideas on a work around? These effects are yellow in the tinmeline, so no pre-rendering is available. And the below error, as I mentioned, happended by just dragging the 10 second mov effect into AME, but it also stalls w

Every time I download AME from Adobe CC (where I obviously logged in), AME asks my login and password, but other apps never ask because they are from the same Adobe CC account. It's annoying, but at the same time useless: never, never ever my before uploaded render settings had been downloaded to just installed AME. What's the point in separate login into one app? How to fix this problem with not working render settings synchronisation? PS My computer is iMac 2019, with clean installed system, no trash from my last computer.   Title edited by Mod 

I have been having a frustrating problem where when I load Adobe Media Encoder CC 2018, all thumbnails say "Media Pending" forever. It worked fine yesterday, no updates, but of course now that I have a deadline for CBS/ABC it stops working. I have the PC version. I cannot "Force Quit" like Mac users can. (A Mac user had this same problem and supposedly solved it by 'Force Quit', which Windows doesn't have.)   I have tried clearing the cache, both within the software and manually, and everything else but nothing works. I need certain options only CC 2018 has so I really need to have this working (not to mention I'm paying a monthly fee for this).   Can someone please tell me how to fix this? It won't let me do any encoding in the cue because of the 'Media Pending'. I am tearing my hair out.    titled edited by Mod

Hi. I'm working on  Imac-Pro Mojave 10.14.6. after installing Premier, When I'm trying to Export  (from After Effects) to media encoder that compatible with After Effects 2017 (version 14.2.1.34), I get this Error - 5027::12. How to solve this? 

Hi Everyone, I am trying to convert AVCHD files(*.MTS) into .MOV before editing them in Premiere Pro.However, CC2017,2018, 2019 versions of Media Encoder drop the audio when I do this.I know the audio is there because if I convert the AVCHD files to *.mov files with EditReady I can now seed the audio and edit in Premiere Pro.I am on a Mac with Mojave with OS 10.14.2 which I think should have the DolbyCodec support.Any idea why EditReady can do this but not MediaEncoder?

Why does AME automatically queue up the previous queue and set the items to Ready when launching for the first time? Since I automatically launch AME upon boot, it will render my previous render from the day before as if it doesn't know it finished yesterday. How do I prohibit this from happening?

Hi,   Updated 2019 to 2020 and noticed that any files above the HD frame size, you need to change the video rendering setting under pref/general to Mecury Playback Engine Software Only.   Anyone know why?  On 2019 I left it on the recomeneded option, which is the GPU Acceleraton (metal)option and Files above HD frame size rendered fine.  However in 2020, the recomended option gives it a pinkish haze on files above HD frame size, whether I'm down converting or keeping the frame size as source.   What's the difference between these options under pre/general/rendering ?     Is the new vsn of ME compatible for making HEVC Rec2020 files? without shifting colour? (ACES colour management)   Thanks in advance   [Moderator moved the thread to the correct forum]

Hello to everyone,I have multiple sequences in Premiere (P), and i need to export all theese in Media Encoder (ME), with the same folder path.In ME if i drag one file and set folder, other multiple files dragged take the same folder. Ad it is good...But if i do the same thing from P, export first seq, set folder, then export others sequences, the folder for theese are not the same! but are take by (probably) precedents works. Other thing (or solution) is, i can set in ME, first to export seq from P, a default folder for all exports?I tried this in ME preferences but less results... I hope I was clear in my explanation..  Thk!Massimo

Hi all, I know this topic has been broached many times, but I've pretty much tried everything that I can to try and fix this but nothing seems to work. I'm running Mojave 10.14.6 while using the 2020 (v14.0) Adobe apps. Things I've tried: - uninstall Media Encoder and reinstalling it - uninstalling every Adobe app and then reinstall them with Creative Cloud - uninstall everything (including Creative Cloud) with Adobe Creative Cloud Cleaner Tool Please see the screenshots below. Both my Premiere and Media Encoder are running the same versions and multiple reinstalls just aren't making it work. Everything was fine until I updated my Premiere Pro a few days ago. Thanks for reading and for any assistance provided. Greg     Title edited by Mod

Hi! I very sad with the latest updates of Adobe AE and AME: I make simple video in AE and send it to Encoder, but it unable to encode. It just stop on "Connect to Dynamic Link" and that's all, it freezes. Any ideas how to make it work again?

I had some mp4 videos I had shot on my phone that I wanted to edit in Premiere. For whatever reason I wasn't able to play them back in Premiere (though I could view them on my phone and on my computer in regular media players), so I thought I'd throw them into the Media Encoder to make sure Premiere would be able to play them back. There were 121 of them, so I left it running. When I came back I saw there were some errors with 56 of them. I gave up on editing them, but I thought I'd try again today after I installed a new software update. After reopening the program, I tried adding the 56 files for encoding, but they were in an "unsupported compression type." I couldn't play them back anymore on my computer either. They are all 0kb, and each has a corresponding 6kb xmp file. What can I do to reverse this? How can I get my files back to the way they were? 

Hello Everyone,   I am frustrated with Media Encoder as it consistently crashes my iMac when I am trying to compress a .mov file to H.264 (mp4) for my customer proofing. I tried all the combinations, source at an external drive to internal drive and same for output also but the results are the same.  Any help will be greatly appreciated.  Error are anywhere from SEGFAULT to filesystem issues.. Please advise.. If need to collect logs, I can send it and I need help to resolve this immediately. ThanksSatish

I use the Name Overlay effect on my render preset when sending drafts to clients, normally with a prefix like "Preview Only:" and the Output File Name (Without Extension). However, instead of the actual filename I've selected, it inserts the temporary filename provided by AME and/or Windows during render. Which means, a filename of "Video_Draft" becomes "~$Video_Draft" and that's what's displayed on screen throughout the render. This doesn't look as professional as I'd like. I've tried this on a Mac environment without any hitches, it only seems to happen on Windows. Has anyone run into this before, and are there any workarounds, besides moving my files to another computer to render? Thanks all!