If updating graphics or BIOS drivers resolves a problem for any of you, that's fantastic. We're certainly glad to hear it. That said, there's little if any doubt that we have a bug in the PPRO/AME code base that's causing the hang that some of you are seeing. Our main CUDA/GPU developer has identified some problems and is working on fixing them. This is really complicated code, so he has to proceed very carefully to not only yield a solid fix for the problems he found but also to avoid introducing new issues.
As GPZ Productions and others noted, the various people who have posted on this thread are likely dealing with different bugs that all manifest the same general symptom: encoding hangs. In fact, strike the "likely"--I know of at least three distinct issues:
- an occasional random hang encoding with GPU acceleration enabled in PPRO, which started in CS5.5. This represents the majority of those active on this thread.
- a hang in CS4.We don't have enough information on this one to characterize it more precisely.
- a regular hang that apparently resulted from RAM usage getting maxed out.
It's also entirely possible that the following could factor in for some of you:
- particulars about the source: if AME hangs at about the same place every time with a given sequence, then a likely culprit is an asset or effect, or combination of assets or effects, near the point of the hang. For instance, I recently documented a hang that resulted from a combination of an opacity effect set to Dissolve and a 3D motion effect on the same clip. Encoding hung several seconds beyond that point in the sequence, with the exact frame where it hung varying by more than a second.
- Heat. If the position of the hang is random, and if shutting off the computer for several minutes results in successful encodes, then the CPU or some other component may be overheating.
- Your particular CUDA card--either the make & model, or a defect in the card. For example, we have been able to reproduce a hang on one test system with a particular CUDA card, but when we run exactly the same test on the same system with a different graphics card installed: no hang. We do not yet have enough evidence to determine whether the first card is defective or if the issue is endemic to that make/model.
Regardless of what exactly is causing AME to hang for each of you, we regret the great inconvenience to you. While we may not have been as involved in this thread as we should have been, I assure you we have been following the thread closely and, more importantly, we have spent considerable time investigating--in particular trying to reproduce the issue internally. Since we finally isolated a repro case several weeks ago, the main developer in this area finally has some leads to follow. Fixing this bug--specifically the GPU issue introduced in CS5.5--is a high priority for him. When he has a fix, we may contact some of you to give it a workout and see if it resolves your hang.
Thanks Mark for the detailed reply,
I have rendered more items since yesterday, still working ok!
However, you are right about the bug, I know of other colleagues that still have the exact same problem (an occasional random hang encoding with GPU acceleration enabled in PPRO, which started in CS5.5)
I hope we have a solution soon.
In CS 4, I spent a lot of time trying to determine if the hang up occured at the same time in a sequence while encoding. I can tell you that it did not. I did see a dependency on the length of the sequence. If I cut the sequence to around two minutes it would make it through. So I suspected heat. I monitored the CPU and Motherboard temperatures during encoding and they were well within safe margins. I examened the time line in minute detail and could see nothing wrong.
I really think my problem developed when trying to render a sequence with a dynamic link to an AE comp in the sequence. Regardless, wiping the system drive and re-install the OS, along with updating the BIOS and some drivers, fixed the problem. In my case AME worked flawlessly since May when I first built this Intel I7 system. It only malfunctioned, and stayed messed up, in the middle of this wedding project that I was doing. Something triggered the malfunction and I found this thread while researching a cure for this issue. It seems most of the people on this thread are using PPro5.5 though.
I also experienced other glitches such as my still pictures in a sequence would turn black and/or the video would be interlaced with green screen during playback. Rebooting almost always made this go away for a while, but the AME always crashed reboot or not.
Thanks for chiming in on this. I hope you guys are sucessfull in solving the issue.
P.S. When is CS6 coming out??
@ GPZ: thanks for the additional info re: the hang you ran into w/ AME CS4.
I'm afraid we're never at liberty to discuss release dates, new features that are coming, etc. Company policy. In fact, if you re-read my earlier post, you'll find that the two refs to the next version number have been expunged as that was dancing too close to the edge. Everybody please delete the earlier email with the original draft so that I don't get in trouble ;-)
I'm new to Adobe CS5.5 and am facing a similar frustrating problem of sitting for days waiting for a short and simple 7 minute photo montage using after effects to render but it seems to hang at about 2/3 during the render. It does not specifically mentions that it hangs but the Elapsed time and Estimate remaining time hangs there. There is no way to save the painful last 2 days of rendering and I am forced to cancel and re-render again. Tried a few times but it seems only short renders (by short I mean less than 24 hours...) seem to have a higher chance of a successful render. Its like playing roulette with CS5.5 and you never know if you'll get a successful render after sitting at the pc for days and realising it hangs halfway yet again.
My Specs are:
GTX 560i (Have obtained latest driver updates)
AMD phenom 1100 - 6cores
No heat problem, sufficient power wattage
I'm just surprised a 7 minute photo montage with only 1 simple particle effect and some clouds effect could take days to render, but the render is never completed as it hangs halfway or 2/3 way. The much hyped mercury engine doesn't seem to work as fast as advertised- With Open GL enabled or disabled, my rendering speeds and ram preview speeds are horribly slow.
Am i doing something wrong as a newbie or is there something seriously wrong with CS5.5's rendering programme? I just want to render out to a HDTV widescreen and I believe rendering a 7 minute photo montage shouldnt take days... Would appreciate any advice on which settings I should use to ensure good quality on screen without leaving the PC on for days trying to render a short 7 minute photo montage.
Hi Metta Xu,
Sorry to hear you're having problems. You mention "using After Effects to render" (that's "AE") but make no specific reference to Adobe Media Encoder (AME), which is the topic of this thread. Please clarify which program is hanging.
Regardless, I suggest trying three tests: render once with the particle effect removed, once with the cloud effects removed, and once with both effects out of the equation. This will determine if either effect, or the combination of them, is causing encoding to be so slow and to hang.
Posted about a week ago on similar problems with Media Encoder stalling and in my case eventually not working at all.
I've got Premiere Pro and media encoder Production CS5.5 working now.
My solution was to new install Windows 7 operating system (after serious crash), load and update all drivers and only install CS5.5 Production Premium (not CS5). The computer has been working well since. The only times it has failed is when encoding a slideshow with some oversize images. I was able to view media encoder viewer and determine which slide it had stalled on (4000 X 2500 image), after resizing 2000X1300 media encoder completed work on next pass. It would appear that AME gags on large files with transitions requiring GPU graphics acceleration.
This episode shook my confidence in Adobe as previous CS versions have worked so well.
However, those versions didn't have a GPU acceleration feature and another piece of hardware that Adobe CS5.5 has to play nice with.
And now that I've noted the need for more uniform file sizes and planned workflow accordingly it appears the software/hardware works very well.
Asus Z68 V Pro Motherboard
i7 2600K CPU clock 3.4 ghz
16 GB Corsair Ram
GTX 570 video
Lucid logic turned on / Intel Rapid Storage turned on
Win 7 Home Premium on 120 GB SSD
Render Export Drive/ Rapid Storage - 120 GB SSD
2 - Western Digital 1TB Drives
1 - Seagate 1TB Drive
Adobe Production Premium CS5.5
Quicktime 7.7 something
Pass this along as a success story on this issue, and hope others have success with the "graphics acceleration" and get their systems working.
Sad to report here also, that after a week of bliss, and rendering a dozen items without problems, I'm back to the same problem again...(hang encoding with GPU acceleration enabled in PPRO, which started in CS5.5.)
Disabling MPE works ok but it's so damn sloooowww.
No software was added or removed during this period.
I too have a similar problem to those reported here.
One hour 20 minute video comprising only two clips. Plays perfectly in PremierePro, and can export to tape back to camera.
In PremierePro, export media, select settings, and select Queue. AME loads, click on start button, and encoding begins. Estimated time is around 8 minutes - after about 1 and a half minutes, encoding sudenly stops - no error messages, machine has not hung, task manager showing very low CPU usage. On attempting to exit AME, sometimes does so, sometimes gives "not responding" and have to crash out. Moved entire project to another hard drive in case drive is the problem. Tried encoding only the second half of the video (in case there is a fault in the source material in the first half) - behaviour is the same - hangs at between one/two minutes.
Machine is Intel i7, Windows 7 Ultimate, 12Gb memory, OCX-Vertex2 Solid State drive for System and Apps, Western Digital Caviar Black 6Gbps drive for data, Seagate Barracuda 3Gbps drive for backup. NVidia GeForce 210 video card (so rendering using software only).
Adobe Production Premium 5.5, all latest updates downloaded and applied.
OS fully updated.
I bought all new hardware and the latest version of Adobe production Suite to try and eliminate the problems I was having with my aging Premiere Pro 2 system - very frustarting that things are worse than before! At least with my creaky old system I was able to get video encoded out of it!
Any suggestions on how tests to carry out most welcome!
I firmly believe that something triggers this malfunction while editing. As I had said my system was functioning just fine and the WHAM! Re-installing the OS has cured it, for the time being. I hope it does not return as it has for you.
Again, I am using CS 4.0 and not 5.5 like the rest of you and I do not have the MPE function.
Sorry to hear that you are back in the soup again. I really hope Adobe does something about this but I am afraid that the code is too convoluted for them to figure it out.
I am having the same problem. I have updated my (nvidia) video drivers to the latest version, and also the computer bios (It's Dell Precision workstation T3400), and it is no help. I'm trying to use AME to encode about 30 SWF videos to H.264 mp4 files, using a queue in ME, and it reaches a certain point (it varies on each video) and hangs. I have only been able to successfully encode about 1/10 of the videos.
How can I get a "downgrade" to the CS5 version so I can get some work done? I used AE CS5.5 to create these comps. Can I encode those in CS5? If not, I need a downgrade to AE as well. I just purchased an upgrade to the master suite for this project as I had the web suite before?
BTW, the same comps render perfectly, with no issues using the same settings as above in AE directly.
We have not abandoned you. This thread represents couple of different bugs based on various reports. The one that most people are reporting has to do with exporting out of PPro to AME and app hanging at some point (Cuda card in system). Or just starting AME, loading PPro project and trying to encode (Cuda card in system). This bug has the highest priority and is still open to be fixed. And I bring this up almost weekly with our development team.
Unfortunately this is also not a bug that can be fixed in AME. So a patch to AME won't solve this issue from what I have been told by development team that’s working on this issue. I have been working closely with Premiere Pro development team and they assure me that is one of their top bugs to resolve.
Perhaps I have posted this in the wrong place then. My problem is with loading After Effects projects directly into AME and having them never complete rendering, even though the program does not seem to be locked up. The same projects render fine if I render them in AE directly. If you can direct me to a better place to post this, I will be happy to go there.
Well, it may not be the wrong post. Do you have a Cuda card in your system. If that answer is yes, this is likely the same issue. Easy way to test this is by disabling cuda in AE and on the project. Save the AE project (with cuda disabled), then bring it to AME. Do you still have this issue? There are instructions on earlier posts on how to do this in PPro. I'm not sure of the steps to disable cuda in AE and AE Project.
Martin - please start a new thread in the forum for the problem you're experiencing with AE. Thanks.
AE doesn't use CUDA. What you describe is different enough behavior from the problems other people described in this thread that we should troubleshoot it separately, and also give it better visibility as a new thread.
Thanks for your posting that we're not forgotten. We often wonder when there's no reply for a while.
I am suffering this same problem, AME freezing. It does seem to have some specific triggers, but can also happen at random in some projects.
t's amazing how much slower performance is without CUDA. I'll be glad when it is all working right. In the meantime...
Are there differences in CUDA performance and stability in Adobe Media Encoder and Premiere Pro? There's a big difference in supported board prices. If I knew a $1,000 board would make my AME stable, I'd get one today.
Thanks again for the help.
I used to be able to reproduce this freezing bug pretty consistently but then I downloaded the latest driver for Quadro FX4800 and now I can't repro.
Can somebody confirm that this bug is gone after the newest Quadro FX 4800 driver is installed? http://www.nvidia.com/object/quadro-tesla-win7-winvista-64bit-276.42-whql-driver.html
The problem - mine anyway - is not A Premiere Pro Project. It is many of them. I have a number of projects that need to be rendered out - each will take in excess of 12-15 minutes or so, so I wanted to stack them up, or batch them in AME. It usually gets through the first one or two, but then hangs up - usually in the beginning of a project. It does not seem to matter what format I am rendering to, or the size - it just does not handle multiple 'batched' files. In my case, each file consists of pretty much the same content. They begin with a 30 second WMV file, followed by a nested sequence, followed by a simple title and another nested sequence. In whole, the projects are about 18 to 25 minutes in length. To get this work done, I have to render from Premiere Pro - so I sit here and watch it render - then I'll get the next one started. . . and wait again.
Yeah that's a real pain. If you do that over and over again like I do for a living then I'd strogly consider an EVGA GTX570. I was experiencing the same problem until I bought one of those and then downloaded the most current driver for it from the EVGA site (not the disc that it came with). With most video editors time is money so you don't want to be rendering while you watch, doing 8 hrs at night, or while your running errands is going to be way more convieniant.
I recently upgraded from cs3. Very unhappy, as while there were some issues with Sony and Canon materials, I found work arounds. Now stuck trying to output.
It's as if my new version of Word would not allow printing.
Anyway, what should I do, as my AME intermittantly hangs. I have major projects going on, need to fix this. Call? Email?
Whats your systems stats? when you jump up to CS5.5 and editing multilayer HD you really need a lot of horsepower. The minimum requirements are a guideline that doesn't really encompass other ware or draws on system resources. If you write back and say you have an i7 with 12 gigs of ram I'd say start one by one updating the drivers for your video card which out of date drivers on Nvidia cards seems to be the main culprit for system lock ups.
It's a slow machine - I'm planning to upgrade soon. However, if I miss deadline on my current job, will not have money, so no new hardware.
Really regretting the upgrade. At least I could do my simple cuts and burn DVDs and export MPGs.
It's a HP p6110f, E5300 CPU, 64 bit Vista, 8MB memory, RAID0 drive.
I just need to output my current job. To get a new machine, reinstall, move everything over ... that's DAYS of unbillable work!!!! Seems like each version of Premiere requires several hundred hours of set up and trouble shooting. All I want is a stable machine to do relatively simple work. Cuts, fades, some color correction.
I was able to at least export up to this morning - my final output for current project is MPEG2 files. Today, it's hanging on the "Encoding Sequence 01" at 0%. This worked fine earlier today.
No changes since this morning. In fact, i had 5 edits queued, it bombed in the middle of #3.
Very very disappointed. I've been on Premiere for over 15 years ( I'm a video artist). Looks like FCP is only solution if I need to expend more $.
I think the e5300 is a quad core right? and you meant 8 gigs of ram. I'm guessing with it being HP and that older of a computer you're probably don't have an approved Nvida card, so you're doing all software rendering rather than Cuda. That's a lot of pull on a system resources, rendering HD is easily 4x's as taxing as SD video just because the math says it's 4x's the pixels.
The one best work around if you just need to ge things done and upgrade hardware later is to render directly out of Premiere, rather than Queuing it to render out of Adobe Media Encoder. Also if you have a lot of rendering, several hours of video in many different clips, just do one, do the math on time length of video vs how long it takes to render, and see if you're going to meet your deadline, if not then I'd upgrade to an i7 with 12gigs or more and an Nvidia GTX video card. You can buy laptops off ebay spec'd like that in the $900 range, workstations in the $600 range. Sometimes you have to bite the bullet and just upgrade and put it on a credit card. I usually upgrade every 2 years. My last system was an 8 gig i7 920 with an nvidia gt 8800 (no premeire approved). Luckily when the i7 980 Hexicores came out I was able to still use my motherboard. Ram is rediculously cheap now, The cheaper i7's are cheap now as well, under $230s. The GTX 580s are a little pricing, $400 range, but the Nvidia GTX 400's cards are way cheaper. Here's a link that explains what cards can be used:
Mainly you want an Nvidia GTX with over 1gig of DDR5 ram. The brand I'm using is an EVGA and I had to update the driver from their site rather than the disc included in the retail box.