I have the same problem here. Encoder crashes when exporting from Premiere since the last update.
What can we do?#
ESTV Østerbo wrote:
Can I roll back the last update for premiere? Our system became unstable after the last update
Did you have any success in getting it going?
If you ever need to revert an update or restore any Creative Cloud app back to the previous version, you can follow the steps in the CC Version Control Guide.
We are starting to have the same issues after having a full Creative Cloud license for a total of 3 days. C'mon Adobe! From what I have read online this is an ongoing issue.
Most of your demographic base doesn't have the time to figure out Adobe's bugs by giving you tons of detailed information. Whether this is an Adobe / Apple / or Graphics cards manufacturer problem this should be fixed in a timely fashion. After our initial install exporting video from Premeire to AME was working and the Que did not freeze up. That being said an update may have made some changes but I am not about to go through the long process of the Adobe cleaner after only having this installed for 3 days. I have work to do and this is really unacceptable. Maybe I should look at going to another software.
You might note that John doesn't have a "Staff" appellation under his avatar? He's no more Adobe employee than I am ... just another user trying to help. This is primarily a user-to-user forum, with most staff posting here actually doing so on their own time.
The reason he asked the rather basic question of needing some data on your setup is that this sort of problem is actually not that common ... most users are not experiencing it all the time. But some users get nailed by it. And it is one of the "typical" problems that most commonly comes down to either a combo of the OS/technical gear issues (whether there's a conflict or something has been updated and now doesn't work with a different component) or there's a footage codec/sequence-setting/effects-combo glitch in the mix. Or ... there's a plug-in that is fritzing some effect used on the second Tuesday but only in this project.
In order for us to help, we need to know some things. We're neither clairvoyant nor omniscient.
>tons of detailed information
You have not even provided the BASIC information of saying Mac or Windows, and the operating system version
There are some specific problems with Mac 10.9.3 and 10.9.4 which MAY, or may not, have to do with your problems
Or, as mentioned, a specific plugin may be the problem... with no information, nobody here knows
Let me try to answer this to the best of my abilities then.
- What version of Premiere Pro? Include the minor version number (Premiere Pro CC 8.0.1 (21) Build AME 184.108.40.206).
- Have you installed the recent updates? (I have all of the updates)
- What operating system? This should include specific minor version numbers, like "Mac OSX v10.9.4
- What kind(s) of source footage? Quicktime Apple Pro Res 422 HQ Linear PCM 1280x720 other files have cased this as well. such as H.264 Linear PCM 1920x1080
- If you are getting error message. I am getting a series error message from Premiere Upon Export to AME but it dissapperas before I can read the whole thing.
- What were you doing when the problem occurred? Exporting the file to the QUE in AME
- Has this ever worked before? It worked on initial install of CC
- What other software are you running? None
- Do you have any third-party effects or codecs installed? No
- Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU). AJA Lhi Kona Card
- Are you using Mercury Playback Engine GPU Acceleration? Yes but the same happens when I go to software only.
- Does the problem only happen with your final output, with previews, or both? both.
JUST FOR MAC USERS - Some 10.9.x links
-next link says After Effects, but check YOUR permissions !!!
-Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
Some 10.9.3 links that may still help
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
And some other Mac links
External speakers stop playback http://forums.adobe.com/thread/1370072?tstart=0
Just an FYI. My playback in Premiere seems just fine. It is only when I go to export my file to AME and I send the file to the AME Que is when the lockup happens. If I export the video file out of AP to my desktop and then import it into AME the program seems to run fine and I can export as many flavors to the Que I want without a freeze.
That's intriguing. There's something in the pass-off PrPr->AME that's burping, it would seem.
Engineer speak but I get the Jist.
That would SEEM to be the point of the last link I posted
Hi John, I went through some of those links you sent but I did not see anything that specifically addressed my issue.
So ... you're in PrPro ... you hit "Export -> Media" and Export dialog box comes up ... you check your settings there, and then click "Queue" ... and then it locks up, correct?
If so, it might be useful to see a screen grab of the whole export dialog box ... also, recheck where it's putting the output. We had one similar ish go for quite a few posts once before we the OP caught that the queued file was being sent, not where he thought it would go, but to a drive that was near-full, and the same drive was also being used for cache/previews. It was pretty simple of fix, but we'd looked through every corncob in Iowa before it was "found".
I doubt it is an issue of A near Full drive since the output is being directed to a thunderbolt Lacie with 2.5TB left on it. However when trying to duplicate the problem this time I was able to get the spot into the Que and not until after I created my 4 different versions did it lock up with the spinning beach ball. So it seems sometimes upon the export from Premiere or once I hit the play button in AME. Attached is a screen grab but obviously it won't tell much except that I did not turn off GPU acceleration. I tried that before but it still locked up.
I can't get that screen grab up big enough on my monitor to see what it says. See, I NEED a 52" full-broadcast monitor here ... ;-)
My comment about the earlier situation wasn't to suggest the same thing here in the particulars but in the "general" ... there was one small little setting that caused the whole mess, and on figuring out what that one "itch" was the whole thing stopped scratching and just ... worked.
PrPro can export your project if done without queuing AME. AME can process your project to other codecs if not queued from PrPro. And, AME can take something of your project in a queue without burping, but too much and the Spinning Beach Ball Of Eternity comes to call.
We've had numerous cases where it was finally figured out that a specific clip or effect on a few seconds of a clip caused something similar, and when that bit was cut out & replaced everything worked fine. BUT ... that caused problems most any way the op's went about trying to export. So ... though there might be some glitch that's gotten into a clip that gets cleaned out when processed directly out of PrPro, I'm thinking this is more likely a settings issue somehow. Or doing it from PrPro to desktop to AME somehow avoids triggering some incompatibility between something in your system, as it does a slightly different utilization of system parts or something. Now, I can "logic" that sort of thing to this point, but ... from about here, it may take a bit more of a back-end type or REAL heavy experienced user to take this farther. Too bad shooternz, Steven, Fuzzy, or some of those haven't been in on this.
I have tried to export the clip to the desktop and then import it into AME and when I create my different flavors it locks up with the spinning beach ball as well. Sorry about the large screen grab but the dual monitors are setup that way. In any case there is not much to see just a timeline with a few clips and some basic text.
Well I might have a measured amount of success. I was using a timeline that was up converted to AP CC form AP CS5. I created a new timeline and it seems to work fine. Stay tuned I will see if I get anymore issues after using the new timeline a bit.
Ah, nice catch Nick - it's great when people report stuff like that that no-one can see without having been part of your workflow.