AME CC 2014 Problems

I've got a couple of problems with the latest Media Encoder, build 8.1.0.122.
1) Nothing moves from the Queue to Encoding. If I click on the "play" button to start encoding files, nothing happens. A blue line under the button, but the files do not encode. I've found a workaround in ticking the "Preferences/General/Start queue automatically after:" box and letting the time run down until AME starts encoding, but that is a workaround...
2) Encodes hang - I've been trying to encode a DCP of a feature-length project. Original file is Quicktime ProRes 422HQ 24fps, 5.1 sound, 1998x1080 frame size, so it fits straight off for the DCP settings for 2K Flat. The encode can go through, I've been able to do it once from the same file, so I know it's not the file... Have also managed to get an encode of the 25fps version... but it has hanged many times before and has literally just done it again... It will hang - "Elapsed" and "Remaining" stop ticking on and the Output Preview stops moving on through the frames. This can be after 3 hours or half an hour, there's no rhyme or reason to it.
3) The application often won't quit - I have to use Force Quit to close it. Either that or it does quit and will then report that it crashed...
I am using a new Mac Pro, 8-core, 64GB RAM, D700 graphics cards, Mac Os 10.9.5.

I am having this same problem; have not found a solution from a web search yet. I see that it's not necessarily a hardware issue: I'm using a MBP with 8gb RAM and i7 dual core, but given your machine having the same issue I can rule out my machine being underpowered for the new version.

Similar Messages

AME CC 2014 C++ runtime error on startup.

First off I have followed all the known tutorials about deleting the preferences folder etc..but still have the same problem each time I run AME CC (2014)
I get the following:-
The program then runs in the background but as soon as I press ok on the above box it then crashes. if I continue to use the program
then it runs however it crashes shortly afterwards. My biggest problem is the fact that I don't have any admin rights on my works computer
so if there is a solution where I can fix this without having this then I will be happy to hear it. Any help on resolving this issue would be very much
appreciated.

The problem is now, fixed updating my graphics driver did the trick. Happy again

Cannot create new presets in AME CC 2014

Whenever I go into AME CC 2014 and try and create a new preset, this is what I see: Strange Adobe Media Encoder CC 2014 Bug - YouTube.
Also, whenever I quit AME, even when it's running idle, just sitting there not doing anything, I always get the unexpectedly quit error message: Screenshot on 2014-07-30 at 02:24:31.png • Droplr Every single time I quit AME I get that, no matter what – super strange.
I transcode my DSLR and AVCHD media via AME (well, I used to, that is) and now I'm kind of stuck. Without creating a preset first in AME, you can't choose ProRes or any other custom codec from Prelude's transcode codec drop-down menu as it pulls directly from AME.
Anyway, that's beside the point. Anyone know how to fix the issue I'm seeing demonstrated in the video screen grab above? I've tried clearing prefs, and fresh re-installing AME CC 2014 – all to no avail. Any help would be greatly appreciated – thanks!

Yes, AME was working properly before. It seems to have happened after I installed the very latest update to AMECC14, however. I'm not sure if that's what did it in though.
This is what I'm seeing – "Presets" isn't even a folder, it is an alias file. Could that be my problem? Will AME re-create those files if I just erase all of the "8.0" folder's contents and re-launch AME? I'm confused, because I assumed uninstalling AMECC14 and doing a fresh re-install would do the trick, but maybe not.
Here are my Adobe folder permissions, Adobe Media Encoder folder's permissions, and the 8.0 folder's permissions. I am seeing Read & Write permissions for my username, but for "everyone" it says "Read Only" – could that be an issue as well?
Thanks so much for your help MMeguro!

AME CC 2014 ver 8.2 missing codecs but 8.1 has them

I have two systems.
One system with Adobe Media Encoder CC 2014 8.2.0.54 got after the latest update to CC.
This system can no longer do MPEG-2 DVD encode. The presets are there, but my earlier custom presents no longer work. When I dupe a MPEG-2 preset and go to preset settings and try to change the format, I cannot set MPEG2 as an option.
Adobe Media Encoder CC 2014 8.2.0.54 has DVD presets, but.
there's no MPEG-2 in them.
On my other system I haven’t run the latest CC updater. So here I have AME CC 2014 ver 8.1.0.122. And in that I can do MPEG-2.
AME CC 2014 ver 8.1.0.122 the previous version also has the same DVD presets,
but there's an MPEG-2 format which seems to have been made unavailable in ver 8.2
On both systems I also have the CS6 AME ver 6.0.2 on both. In AME CS6 too I cannot do MPEG-2 in the first system.
So basically, in AME ver 8.2.0.54 some codecs are missing and cannot be used. MPEG-2 is one of them. So in AME ver CC 2014 8.2 how can I get back these presets. Can I download the ver 8.1.0 standalone installer from somewhere?
Neil Sadwelkar

I am having this same problem; have not found a solution from a web search yet. I see that it's not necessarily a hardware issue: I'm using a MBP with 8gb RAM and i7 dual core, but given your machine having the same issue I can rule out my machine being underpowered for the new version.

MP4 encodes fail when output size is greater than 4GB, AME CC 2014.2 (8.2.054)

I have a jpeg image sequence about 45 min long at 30fps.
Using AME CC (7.2.2.29) I can successfully encode to MP4, CBR at 18 Mbps. File size is about 5.53 GB.
Using AME CC 2014.2 (8.2.054), with the identical preset (migrated directly from previous AME), the resulting file is unplayable.
AME CC 2014 gives following warning at the end of the encode:
- Source File: /Volumes/LS-GRAID-8TB-1/DDL_video/Output/1_Frames/2_Current/102-204-C01-CallanderVeryGold _16bit/102-204-C01-CallanderVeryGold_16bit_[00000-82441].jpg
- Output File: /Volumes/LS-GRAID-8TB-1/DDL_video/Output/2_Encode/1_Review/102-204-C01-CallanderVeryGold_ 16bit.mp4
- Preset Used: DDL-MP4-CBR18
- Video: 1920x1080 (1.0), 30 fps, Progressive, 00:45:48:02
- Audio:
- Bitrate: CBR, Target 18.00 Mbps
- Encoding Time: 00:55:28
01/19/2015 03:33:17 PM : File Encoded with warning
Adobe Media Encoder
Could not write XMP data in output file.
When I either reduce the bit rate OR reduce the work area, so that the final output file is under 4GB (or more specifically, under approximately 4,096,000,000 bytes), I do not get the XMP warning, and the final file is playable.
Again, please note that the previous version of AME CC does not have this problem when using an identical preset on identical source, so it does not seem to be a problem with the source frames or the output format chosen, it seems to be an issue with the current build of AME.
Is there a solution to this issue?
thanks

I have had the exact same problem, I am now trying to encode with audio. ( I also did not need audio ).
My file size and bit rate is a little higher . and using VBR not CBR but it is a mp4 encode and exact same problem, unplayable.
I am now trying an encode with audio on at lowest possible rate, to see if it assembles the video correctly.
I can confirm the work around, With AUDIO on, the export works.
BTW: also tried the sequence directly in Premiere 2014.2 and same error.
-----:LOG:-----
03/06/2015 08:19:46 AM : Queue Started
- Source File:Adobe Premier Edit_1.prproj
- Output File: FullRez1080_59.94fps_VBR10-50_noAudio.mp4
- Preset Used: Custom
- Video: 1920x1080 (1.0), 59.94 fps, Progressive, 02;53;33;46
- Audio:
- Bitrate: VBR, 1 pass, Target 10.00 Mbps, Max 50.00 Mbps
- Encoding Time: 03:40:33
03/06/2015 12:00:19 PM : File Encoded with warning
Adobe Media Encoder
Could not write XMP data in output file.
03/06/2015 10:12:51 PM : Queue Started
- Source File: Adobe Premier Edit_6.prproj
- Output File:FullRez1080_59.94fps_VBR_20-50.mp4
- Preset Used: Custom
- Video: 1920x1080 (1.0), 59.94 fps, Progressive, 02;53;33;14
- Audio: AAC, 16 kbps, 8 kHz, Mono
- Bitrate: VBR, 1 pass, Target 20.00 Mbps, Max 50.00 Mbps
- Encoding Time: 05:11:45
03/07/2015 03:24:36 AM : File Successfully Encoded
Machine:
Mac Pro 6,1
12-Core Intel Xeon E5
64GB RAM

AME CC 2014 Rendering with only One Core

This seems to have just begun recently (within the past month) where AME CC 2014 is only using 1 core (out of 12) to render video. No, this is not the CPU Parking issue - I have made the regedit tweaks and also changed my Power option to Performance, all with no difference in AME. Premiere Pro CC 2014 renders the same video just fine using all 12 cores, so it seems this problem lies not with Windows software, nor Premiere Pro, but just AME CC 2014. Was there a recent AME update that might have included this bug?
Adobe, please look into this and resolve it ASAP. Not being able to queue up video renders is killing my productivity.

I just installed Premiere Pro CC 2014 this week and had the same problem, my media encoding time tripled (3 times longer).
The same sequence in Premiere Pro CC (Old Media Encoder ) still encoded at its normal fast speed.
Only one of my eight cores was running during encoding in Premiere Pro CC 2014.
After making the registry changes (below) all eight cores were running and Premiere Pro CC 2014 Encoder was back to normal speed.
Read Below:
I did a search and found this link below.
Go to this link below and read.
https://forums.adobe.com/thread/1506298
After you have read the Adobe Forum link above, go to this link below.
This registry change is for Windows 7, I'm not sure about Windows 8
The registry link may be different but you can still look.
Than call Adobe and have their tech go to this link below.
Than have them suggest what to do.
I did call Adobe back and told them it fixed my problem and they were appreciative and said they would pass it on to all their techs.
http://ultimatecomputers.net/forum/viewtopic.php?f=7&t=3644
Just a note,
I was in touch with Adobe earlier this week with this same problem.
I gave them control of my computer (from India) and after an hour the tech concluded it must be my video card causing the problem.
I am using a Nvidia GTX 560Ti, which is not a certified card. I preformed the card hack.
After getting off the phone with them I did some additional test and found that my old AME rendered my sequences with all eight cores.
The new AME CC 2014 was only using one core.
This registry change above keeps all the cores running.
After I made the change all the cores were running during encoding and the speed was back to normal.
Hope this helps,
The Video Guy

Pro Res for AME CC 2014

I had issues with AME CC – the app would open but wouldn't start the encoding on my imported media. After some frustration I installed the AME CC 2014 app. Now I don't have any pro res or dnx presets.
Where can I find these? How come AME CC 2014 didn't automatically recognize the presets previously installed?
Thanks very much.

I just installed Premiere Pro CC 2014 this week and had the same problem, my media encoding time tripled (3 times longer).
The same sequence in Premiere Pro CC (Old Media Encoder ) still encoded at its normal fast speed.
Only one of my eight cores was running during encoding in Premiere Pro CC 2014.
After making the registry changes (below) all eight cores were running and Premiere Pro CC 2014 Encoder was back to normal speed.
Read Below:
I did a search and found this link below.
Go to this link below and read.
https://forums.adobe.com/thread/1506298
After you have read the Adobe Forum link above, go to this link below.
This registry change is for Windows 7, I'm not sure about Windows 8
The registry link may be different but you can still look.
Than call Adobe and have their tech go to this link below.
Than have them suggest what to do.
I did call Adobe back and told them it fixed my problem and they were appreciative and said they would pass it on to all their techs.
http://ultimatecomputers.net/forum/viewtopic.php?f=7&t=3644
Just a note,
I was in touch with Adobe earlier this week with this same problem.
I gave them control of my computer (from India) and after an hour the tech concluded it must be my video card causing the problem.
I am using a Nvidia GTX 560Ti, which is not a certified card. I preformed the card hack.
After getting off the phone with them I did some additional test and found that my old AME rendered my sequences with all eight cores.
The new AME CC 2014 was only using one core.
This registry change above keeps all the cores running.
After I made the change all the cores were running during encoding and the speed was back to normal.
Hope this helps,
The Video Guy

Can't export to MPEG2 with AME CC 2014

It seems AME CC 2014 doesn't like me. When trying to export a project from Premiere CC 2014 to MPEG2, I get "Cannot create movie. Unknown error". Switching to AME I get the same thing, but AVI seems to work. Previous versions of AME and PPro seem to be fine, it's just 2014. Anyone else run into this yet? I really need to be able to export MPEG2 files.

I wasn't, but after some tinkering I've found a couple of issues. After reverting back to the NTSC DV preset and modifying from there, it'll generate the error when I try to set it for a CBR of 15 Mbps. Anything below that is fine. Also when trying to use MATCH SOURCE, it errors out until you uncheck Profile and Level. The video playback server I send clips to is rather picky, so I try to give it as easy of a file as possible.. CBR and 1 GOP seems to make it rather happy. All of those work, except the 15 Mbps CBR. It's an annoyance but one I can work around for now.
I'll submit a bug report to Adobe and see what they say.

AME CC 2014: "Adobe Media Encoder has encountered an unexpected error and cannot continue."

Adobe Media Encoder CC 2014 on MacPro "mid-2012" (MacPro5,1) running OSX 10.9.3 and getting this error when trying to launch Adobe Media Encoder CC 2014:
Adobe Media Encoder Error
Adobe Media Encoder has encountered an unexpected error and cannot continue.
Have uninstalled, reinstalled. Checked and fixed permissions numerous times. Tried removing all plugins and that didn't fix. Also tried editing the text listings within the .app for OpenGL and CUDA to remove all cards listed - that didn't fix anything either.
At this point it's uninstalled and "hopefully" everything will point to CC (non-2014 version). Adobe Media Encoder CC works fine. Adobe Media Encoder CS6 works fine.
Cannot find any other reports of this issue.

Progress in trying to fix. This workaround was NOT successful on previous attempts, but now appears to be working. Seems like the trick was to have AME CC 2014 started and open BEFORE doing any of this? As always, make sure all of your permissions are set properly - had done that numerous times previously. My issue was NOT directly permission related.
Navigate to the following folder:
You may see a file SHORTCUT that is invalid called "Presets":
Remove/delete this file. It's a broken shortcut.
Move a folder of .EPR files into the "8.0" folder. Call it anything except "Presets". Go to AME CC 2014 and quit. (I was greeted with another crash message.)
Open AME CC 2014 again. Your presets will not be loaded yet, but you should see an XML file that was created in your new folder like this:
Delete this file.
You should see a new folder also created by AME called "Presets". Move your .EPR files into this folder and delete the original folder. Quit AME CC 2014. (I was greeted with ANOTHER crash message.)
Open AME CC 2014. Your preset files should be there at the top under the preset browser:
Probably a good idea to keep a copy of those .EPR files elsewhere

Taking forever to send comps to AME CC 2014

Hello, for the last week or so I've having difficulties using AME CC 2014 to render AE CC 2014 comps. I click 'add to Media Encoder cue' and nothing happens. Sometimes 10-15 min later the comp shows up in the AME cue, other time it will appear after starting other encoding jobs. There's no indication that anything is going on during this time (no excessive save times). This issue does not seem to extend to Pr. I am attempting to render very large comps (~6000x720 px). I recently installed the latest round of updates, but I don't believe this issue started immediately after.
Has anyone else been experiencing this or have a fix? This is incredibly frustrating. So far it seems that CC has only sped up how fast bugs are rolled out, not fixes!
Some tech details:
Mac Pro 8-core Xeon E5
64gb ram
OS X 10.9.5
Working off of and rendering to a Pegasus 2 R6
P.S. I've also been having lots of issues with multi-frame rendering, but that's been causing me issues off and on for 3+ years, so I don't believe they are connected.

Hi Szalam, thanks for responding!
As a test I just made a new project with a 720p comp and a single solid with a text layer. It cued up in AME without issues, both saved locally and on the RAID.
I then made a very basic 7000px wide comp and that cued properly as well.
These projects I'm working on that are having issues are fairly complex with lots of footage, AI files, and precomps. Is there any reason that would make it take 10-15min to cue? It doesn't really make sense when saving the project file only takes 2-3 seconds.
I have been rendering to an intermediary in the mean time, it just really slows down my progress since multi-frame rendering hasn't been working in AE. I guess I'll have to dig up my old BG render script.
Thanks for the help!

AME CC 2014

I have the latest version of AME CC 2014.
I often keep my PC on for many days, editing and rendering clips.
I've noticed with the new version of AME CC 2014, that after my PC has been up for a bit - the render slows down. A 15 minute clip will take 1.5 hours to render; whereas, normally the same clip will take 25 minutes to render using the Mercury Playback engine GPU Acceleration.
I then need to reboot my whole PC, and AME will render in full speed again.
Any suggestions on why this maybe happening?
Regards,
Joe

Check your RAM usage. It is possible that you're running in to a situation where RAM isn't being freed up properly. If that is the case, please do let us know.

AE CC 2014/AME CC 2014 Render Problem

I've been having a strange problem with Media Encoder CC 2014 & After Effects CC 2014. If I try to export a comp either through Media Encoder or directly from the After Effects Render Queue then it only exports audio. If I bring the AE Comp into Premiere and export from there either by sending it to Media Encoder or exporting it directly from Premiere then it exports fine and gives me audio and video.
Windows 7 64
i7 950 @ 3.07GHz
24GB Ram
Quadro 4000

dear rick,
of course you are right. for the actual masters i use motionpng or motionjpg . sometimes cineform. for shorter clips tiff-sequences.
but this does not answer my question. in the current case i have to have "master-like" files (for re-encoding) that are still playable in most players and on most devices. therfore h264.
but actually my question is not about which codec to use for different purposes (had long research- and discussion-sessions about that already).
the question is: why do the seemingly same encoders in ae and ame (quicktime with h264 with qualityslider 0-100) deliver so much different results?
i'm trying to figure out, whats the difference between ae-rendering and ame-rendering. how do i deal with rendersettings (effects, proxies etc) in ame? which one is better to use? and why the fudge is there a difference of 1:10 with the same settings in the different solutions????
thx...

Wrator DCP problems in AME CC 2014

DCP rendering fro AME is great, but I am having some problems:
1. Wrator DCP informs a fixed bitrate convertion of 250Mbps, but I am geting final DCPs with variable and very low bitrates, as 38Mkps or even lower.
EDITED: It seams that is not a problem at all. QuVIS claims to use a Quality Priority Encoding method, so encoding bitrates are variables up to 250Mbps aiming to a studio quality standard, and not fixed as I thought. Good indeed.
2. NeoDCP player won't play some DCP due to unmatched frame numbers form audio and video MXF
3. Render crashes sometimes with no apparent reason.
PS: I am using the new recomended update from QuVIS site: DCP Packaging for Adobe Media Encoder 8 | QuVIS

The problem of some players not playing (some) DCP correctly is related do unmatched number of frames not correctly informed in CPL files.
Some times Wraptor DCP produces a MFX sound 1 frame bigger than MXF video. I think it is related to original sound bit depth conversion (not sure).
One solution is (in the case of problems) to edit CPL XML file and change IntrinsicDuration parameter to correct represent audio MXF duration.
        <MainSound>
          <Id>urn:uuid:9d1b0299-0282-498d-bb29-849f8fee8af8</Id>
          <AnnotationText>DSC_5845_dcp_9d1b0299-0282-498d-bb29-849f8fee8af8_audio.mxf</AnnotationTe xt>
          <EditRate>24 1</EditRate>
         <IntrinsicDuration>1015</IntrinsicDuration>
          <EntryPoint>0</EntryPoint>
          <Duration>1015</Duration>
        </MainSound>
OR, even batter, use OpenDCP to repack audio and video MFX files in a new DCP, with a lot more.

Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
Maruf

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Transition issues when rendering in AME CC 2014?

I have a project from Premiere Pro CC 2014. It uses standard transitions on still clips and everything looks good in the preview window, but when I send to AME the blending changes somehow and the images seem to pop on or off, and sometimes darken over the previous image in strange ways. I am rendering using the software Mercury engine in both applications. Any suggestions? Thanks.

I was having the same problem, and couldn't find a fix. It was also screwing up certain effects, particularly warp stabilizer every time I rendered or exported. Finally, I tried changing the renderer from Mercury Playback Engine GPU Acceleration (Open CL) to Mercury Playback Engine Software Only, and it worked like a charm. Go to File -> Project Settings -> General and select the renderer from the dropdown menu. Make sure to also change the renderer when you export. Using Adobe Media Encoder, be sure to select "Mercury Playback Engine Software Only" in the dropdown menu next to "Renderer" before you export.
This has completely eliminated the problem for me.

AME CC 2014 Problems

Similar Messages

Maybe you are looking for