The decoding feature will now be frequently confused with the new encoding feature.  For that matter, Adobe has always been purposefully vague about the system requirements for (and pathway to enable) Intel hardware acceleration in this regard, involving Quick Sync on select CPUs.  More here:  www.focuspulling.com/cc2018 ... View more

FocusPulling.com  wrote How does this function interact with/conflict with/overlap with the checkbox in Preferences under Media for "Enable accelerated Intel H.264 decoding"?  I have that unchecked, because I have generally understood it to ironically slow down exports when there's a powerful GPU anyway (I have a GTX 1060 6gb installed, with internal Intel HD Graphics 530 disabled at the BIOS level).  Adobe has done a poor job of distinguishing these two Intel acceleration features upon launch of the "new" April 2018 claim. Moreover, and back to the topic of this thread, I see the option grayed out on my system too, but I do have a listed CPU with QuickSync (Core i7 6700K).  So, are you sure it's as simple as your answer, Kulpreet? OK, so in the absence of a response -- thin skin, Adobe? -- I've gone ahead and written up a likely explanation of what's going on here: Adobe Premiere Pro April 2018 Update: 2x faster export! | FocusPulling (.com) ... View more

I think that this guidance I've just written up will help: Adobe Premiere Pro April 2018 Update: 2x faster export! | FocusPulling (.com) ... View more

How does this function interact with/conflict with/overlap with the checkbox in Preferences under Media for "Enable accelerated Intel H.264 decoding"?  I have that unchecked, because I have generally understood it to ironically slow down exports when there's a powerful GPU anyway (I have a GTX 1060 6gb installed, with internal Intel HD Graphics 530 disabled at the BIOS level).  Adobe has done a poor job of distinguishing these two Intel acceleration features upon launch of the "new" April 2018 claim. Moreover, and back to the topic of this thread, I see the option grayed out on my system too, but I do have a listed CPU with QuickSync (Core i7 6700K).  So, are you sure it's as simple as your answer, Kulpreet? ... View more

This is a known bug and Adobe shows no interest in fixing it.  Has been around for several versions with no resolution.  It makes the FX mute function . . . moot. ... View more

jdmathews17  wrote THANK YOU SO MUCH! You have fixed my problem! I kept receiving this error: Error compiling movie. Accelerated Renderer Error Unable to produce frame. Error code: -1609629695 I had this massive .png file (8334x8334) at the beginning of my video. I changed the size of that .png and it automatically started working! I can't thank you enough man! -Josh Glad you got things working after that, but the repeating theme in this thread is that Premiere's behavior is arbitrary, unpredictable, and simply broken.  It makes no sense at all that large still pictures can make a sequence crash during export, but not during playback from the timeline even at the Full resolution playback setting!  Adobe has no excuses for this but also clearly doesn't care after years and years of this being a severe product bug. ... View more

https://forums.adobe.com/people/Ann+Bens  wrote That feature has been around for quite some versions now. If you want to reveal a nest and have the cti in the same place use: ctrl+shift+F I haven't found the keyboard shortcut you advise to be at all necessary.  The default behavior when double-clicking into a nested sequence is that Premiere puts the time marker at the related match frame of the parent sequence. ... View more

Their answers will always be (to their demise):  1. if you're using a GPU, it's out of our control, but make sure you have their latest drivers; 2. if you're using a plug-in, that's probably why; and 3. Lumetri is still being developed and we're super excited about what it'll turn into someday! ... View more

Really disappointing that this feature doesn't do what it would be the most useful for:  snapping assets to the exact edges of the frame.  That still is one of the slowest and most frequent things in my workflow, such as scaling pictures to fit precisely, etc.  No excuse not to expand the feature to that... ... View more

eric_brb  wrote I thought about trying to workaround this problem by rendering an image sequence...but it still crashes ("Encoding Failed" as opposed to "Error code: -1609629695"). If only there was a way to easily continue from where Encoder crashes.  The image sequence always starts at frame 0 even if I start to render from a point later in the timeline.  Within ME, I have to calculate the frame number from the timecode...so I could easily skip a frame or two if I'm not careful.  I also have noticed that I get a little further each time I start an encode. Might be the larger, most unforgivable product flaw of Premiere, that any still picture past the HD or UHD range of resolution runs the risk of crashing an export, without specifying why, even though playback from the timeline doesn't.  Naturally any still picture from a camera is way past UHD resolution, and we are always zooming into them thus needing to retain that original resolution.  Premiere has no excuse for that feature limitation, but Adobe keeps advising us to downscale still pictures, vaguely admitting that they crash Premiere. ... View more

OneSlip  wrote I can confirm that after upgrading from GTX770 to GTX1080Ti problem has disappeared. I render with Lume and couple of other effects on top including warp stabilization. I have been testing it for a month now and besides the occasional crash and freezing during edit it is hassle free on rendering. Glad to know it for your sake -- but that's not an escape clause for Adobe, that everyone should upgrade their GPUs (even as Adobe is strategically silent on the whole issue and saying nothing).  One common denominator that does associate with newer GPUs like yours, though, is an inevitable higher amount of VRAM.  Adobe says we should have 2gb at minimum; you have 8gb.  The GTX 1060 usually has 3gb, and that is just as new -- but it crashes with this error often. One very vague plague in the Premiere work environment is something called a "memory leak" and there, once again, Adobe has been strategically vague.  But I think it's related to this.  Whenever we run CPU-Z and GPU-Z and watch how much our hardware is getting pushed, it's always never even close to the memory and processing limits.  Adobe's sloppy coding makes the whole program crap out even when usage levels are at, say, 30%.  This is Adobe's problem and they haven't made a move toward fixing it. It's a laughable situation when one of their official diagnoses is that still pictures should be at HD resolution, even if we're zooming into them.  Premiere notoriously freaks out with large still pictures, unlike any other video editing program.  Yet it only happens during export:  not during full-resolution timeline playback! Another example of amazing incompetence at the software team.  But don't forget:  Adobe announces record-breaking $1.84 billion in revenue for Q3: Digital Photography Review ... View more

The simple problem with this issue -- and why Adobe has refused to invest energy into fixing it -- is because it generally (but not always) involves the interaction between Nvidia/AMD GPUs, and Premiere.  So, Adobe's scripted talking point is:  not our fault! It's an incredibly short-sighted attitude, of course, and will lead to Premiere's demise as the rest of the industry (who cares about their customers) catches up, working with the GPU industry to keep things compatible. The crazy thing is, the GPU industry is hardly fragmented:  there's just two strands, and within that, just a handful of closely related GPU models.  It would be so easy for Adobe to take control of the situation, if the corporation weren't run by accountants. ... View more

https://forums.adobe.com/people/kulpreet+singh  wrote Hey Neils, I have the exact same problem. Sorry to hear that, did you try all of the above mentioned steps? Please click on the "I have the same question" tab at the top. Thanks, Kulpreet Singh This thread should not have been marked as "answered."  Not even close.  That Adobe has a severe bug crashing Premiere upon simply initiating the prompt to enter a new filename/location, is not resolved by the suggestion to severely downgrade the Premiere application's functionality, to software-only rendering.  That has nothing to do with Adobe's bug (obviously).  And yes, I've cleared my preferences, which did nothing to solve this ongoing problem. Just because you don't see it in frequently in these forums, doesn't mean the problem isn't a huge nuisance.  We have to force-close Premiere and start over, but sometimes it causes loss of the most recent version since auto-save. This problem ​needs to be fixed. ... View more

thibaultz66217265  wrote +1, 24h wasted... No solution yet Adobe's incentive to fix these severe errors is still awaiting a correction, and it's not looking good: Adobe Reports Record Revenue in the Third Quarter ... View more

I'm so disgusted by this error and like everyone else it has consumed dozens of hours of my wasted work trying to fix it.  It's clear that Adobe's posture is, if it's a GPU error, we don't manufacture GPUs, so it's their problem.  That's like selling a car that's flawed in its fuel intake system, then when the car doesn't work, Adobe says, contact the "gasoline manufacturer."  It's like, who doesn't use a GPU who's serious about video editing?  Premiere lives or dies by its interaction with GPUs.  And the GPU industry is slimmed down to just two standards, so there's no excuse. To give another example of Adobe's arrogance:  their advice on crashes includes the demand that we keep all still images in our timelines down to HD resolution -- that's even if we need to zoom in and thus require more resolution for that.  Yet when you play back in real time from the timeline, with the playback resolution setting to "Full," it never crashes!  So it only crashes during slower rendering when it actually has latitude to throttle resources.  Adobe's demand that we scale down our stills to tiny pictures not only sacrifices quality, but it makes no sense at all. Another boilerplate position by Adobe:  they claim they don't have any idea what we're saying in these forums.  Occasionally paid delegates show up and almost always just do damage control, defending Adobe.  So basically, you can expect everything in this forum is ignored, and the bug report system has no transparency or accountability. I can't wait until the day when real competition kicks Adobe to the curb.  Until then, our creativity is dramatically compromised (and wasted).  The program continues to bloat with gimmick features to stay fashionable at trade shows.  It's never crashed as much as now.  Karma's a real thing. ... View more

Adding to this with important advice:  Make sure, when using this technique, to create a few spillover tracks (both video and audio) as well as activating them, so that all content is brought in.  If you don't, and if your sequence has more tracks than the destination, Premiere just dumps what it can and leaves out the rest! ... View more

RProeis  wrote Work-around/solution is quite simple. Make sure the bitrate is the same on your audio, for instance 24 bit. In your audio render settings, make sure you export with 24bit audio. Uncompressed. Then no audio render whatsoever. Straight to encoding video. That is a limited rather than universal work-around, despite the way that you characterize it.  The solution is for Adobe to actually address this issue after years of willfully ignoring it.  What you claim is quite simple ​did not result in any change​ on several projects of mine. ... View more

Adobe's refusal to fix this years-long bug is anti-consumer. My entire project's many hours of audio files go through cyclical "processing" that takes 95% of my export render time for a single sequence with ONE audio clip. The arrogance of Adobe to refuse to fix this elementary bug is a signal for everyone to bail on Premiere. All that the Adobe employees do here is defend Adobe. ... View more

DamnThemaps  wrote Creating a whole new Microsoft account is not a fix. It is a workaround until Adobe repair the obvious bug. If i create a new user account, Windows 10 and all associated stuff pertaining to my Microsoft account like office 365, my network, business and attached computers will all become my new problem... and a problem far bigger, expensive and more time consuming than missing Mask handles on Premiere. I'm not mad at Adobe at all. My first post was to help users with my workaround that worked for me where the above workarounds and fixes didn't work. Also to help Adobe so that they can see that the above is not a FIX for everyone. Thought it might help someone but already I'm just wasting time defending myself on forums. Well, bugs are upsetting, so there's nothing to apologize for.  I'm really discouraged by this bug myself, finding no solution, and clearly Adobe needs to publicly acknowledge their bug, confirm that it's on their agenda to fix, then get back to us when it's fixed.  That's standard industry practice as well as a minimum level of customer service. ... View more

https://forums.adobe.com/people/Ann+Bens  wrote Did you ever Contact Customer Care - Premiere Pro chat and asked for a video queue? Yes. And yet that totally doesn't matter, when one case gets resolved (or in my case, totally doesn't).  This is a known bug and the most Adobe has said on the matter -- besides making any effort to fix it -- is to say, perhaps you imported a sequence from a prior version of Premiere.  With the regular cycles of Creative Cloud updates, who doesn't?  It's not acceptable, obviously, for every single minor software update to bring with it tons of excused bugs.  Adobe is either servicing its customers as a priority before adding new doodads, or not. ... View more

This is still an appalling, workflow-halting bug, no matter what Adobe cheerleader Jim Simon Says. I'm having the same problem that dates back a half-decade from today, that buzzing during playback upon the insertion of a Constant Power crossfade.  No solution, ever. I'm on the very latest 2017 update. Adobe:  do you care? ... View more

jon lawson wrote: This may sound a bit crazy, but.. If you are exporting an FCPXML, you can open this up in Davinci Resolve Lite [free color correction software from BlackMagic] Open new project, import fcpxml, render out to an AAF file (yes, AVID I know) and Premiere CC should be able to open it. Just make sure your bin files don't change at all from the export of the fcpxml from FCPX through the creation of the AAF. It's tricky but doable. From FCPX: Export XML / **(For 2015 updated users, select version 1.4 as Resolve will not recognize the latest version 1.5) Open Resolve Lite: - Import XML - Render and Export as AAF (You will have to select AAF in file export settings or it will just revert to fcpxml again) Then open Premiere CS6 - or - CC: Open new project, import fcpxml, render out to an AAF file (yes, AVID I know) and Premiere CC should be able to open it. Just make sure your bin files don't change at all from the export of the fcpxml from FCPX through the creation of the AAF. It's tricky but doable and I have had some issues. Some ranging from title settings being dropped to totally non-migratable but there has been some successes. Worth a shot before spending $50 on Xto7, a program made to make new hardware back-compatible and communicable with other NLE systems. This sounds really promising, thanks! ... View more

jstrawn wrote: Thank you for sending in your crash logs. The case of morph cut crashing with CUDA rendering is not a ubiquitous problem, so the logs and any other specific steps you can provide with a bug report will be needed to determine why it may be crashing in your system. Strongly disagree that it is "not a ubiquitous problem." Morph Cut persistently crashes and the Interwebs are drenched with confirming reports.  The latest 2015.2 failed to address the problem.  It is simply not an available feature valid for advertisement until it is actually fixed.  Adobe has been aware of the bug for quite a while by now. ... View more

Reg Santo Tomas wrote: It would be very helpful if people can list a step by step scenario of how they are running into this crash from a new project. 1. I add it. 2. Crash. ... View more

Henrivo1 wrote: it's a bit late to reply to this, but anyways I was having trouble with morph cut as well when I was trying it for the first time, it would crash my premiere and every time I tried to delete it by selecting it after re-opening the project it would crash again anyway. everytime. so the way I worked around this was I selected one of the cut clips and separated it from the previous cut clip and the transition would automatically delete it self that way without needing me to select the transition and therefore causing the crash. If it's anything I learnt from this, is to not use morph cut. at least not for the time being. This happened to me too, and the alternate approach is to drop another video transition onto the placed Morph Cut which makes the problem go away. ... View more