Skip to main content
Participant
October 10, 2015

P: Morph cut - Analyzing in Background never completes

  • October 10, 2015
  • 186 replies
  • 144268 views

I have a simple headshot cutting to the same head, same everything a few seconds later.

All other transitions work find. I try morph cut and see 'Analyzing in background.' Never see sign of progress - should I see it chewing through frames somehow?

I have gone to project settings. Tried both rendering settings. One thing - When I do GPU acceleration my still frames look like garbage - example:

http://www.screencast.com/t/rPiWL6yL

Software acceleration looks fine. No idea if these items are related.

Have run through all preferences. Don't see anything that might be turned off. BTW - working with MBP 15" late 2013. Latest OS.

186 replies

imcaleb
Inspiring
December 6, 2017

Hi, I've been having this problem for a few months now and couldn't find any solutions.

I've been working on a fairly large project within the last few months consisting of 21 final sequences in total. I've applied multiple morph cuts to the final edits and they look fine in Premiere, but when I export them (either using AME or straight out of Premiere) the "Analyzing in Background" banner is burned into the export. It's incredibly inconsistent so I don't know how to troubleshoot it. Sometimes it burns into the file, but then I'll re-export it using the exact same settings, and it works fine.

I can say that I've had more success exporting straight out of Premiere rather than using AME but again, it's super inconsistent and I have to double check everything and often re-export.

Given the scope of this project and the fact that these sequences need to go through multiple revisions, this issue is becoming unnecessarily time consuming (especially when I can't use a render queue). I was curious if this is a known bug, or if there are work-arounds via project settings or something that I can use to fix this issue.

I've done a couple of similar projects earlier this year, and late last year and didn't have this issue at all.

I'm using the latest and greatest in terms of Premiere versions (v12.0)- I just upgraded yesterday in hopes of this being fixed / solved but was sadly disappointed.

Here are my computer specs if it helps at all:

MacBook Pro (Retina, 15-inch, Mid 2014)

macOS Version 10.12.6

Processor: 2.5 GHz Intel Core i7

Memory: 16 GB 1600 MHz DDR3

Graphics: NVIDIA GeForce GT 750M 2048 MB

                 Intel Iris Pro 1536 MB

brian704
Inspiring
December 6, 2017

I've not had the problem but - you could try setting your preview codec to be the same as your render codec and clicking the "use Preview" box on render. This will speed up your renders as well.

imcaleb
Inspiring
December 6, 2017

This definitely works, but it seems more like a band-aid rather than an actual fix. The previews that Premiere generates are great for viewing edits in real-time, but I'd rather have the final exports for these projects in full resolution.

Trickooo
Known Participant
June 12, 2017

Hi. After applying a morph cut transition on two videos and exporting, there is still the line in the middle. I don´t know why, but I have to get rid of that as soon as possible.

This is a first time I have a problem with a morph cut transition like this. Thanks for replies.

Kevin J. Monahan Jr.
Legend
June 12, 2017

Hi Trickooo,

It might be the kanji character behind the head. You want a very simple background, that artwork makes it not so simple.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Trickooo
Known Participant
June 14, 2017

But the camera is static so I hoped the morph cut can render that. Nah, thanks for reply

Participant
October 19, 2016

I had that same issue.

To most effectively use morph cut you literally have to :

Export the first clip to morph, export the second clip to morph, import the 2 new separate files and apply morph cut.

Adobe Premiere should do this automatically, however it runs into one of two issues.

Issue 1: The source file is too large. (my source files are 500mb - 25gb)

Issue 2: The MORPH CUT is being applied to the same clip, which causes the ANALYZING IN BACKGROUND error.

The best way to solve it is to reduce the source file size, export and reimport your clips, and morph between two different source files.

Adobe should do this automatically, but until then this is what we have to do. It's inefficient and redundant - I'm using a Morph Cut between two cuts, I should not have to cut before and after the morph cut in extreme attempts to reduce my source file size.

Michael James Webb

310 Digital Sales And Service

Participant
January 5, 2018

This seems to have been the source of my problem, but I inserted a cut on both sides of the transition and it analyzed within seconds.

Thanks!

-- Dan Dunbar

Participant
October 18, 2016

Hello,

Morph cut on Premiere is not working, it analyzes in the background indefinitely. Has anyone else experienced this issue? If so, how did you resolve this error?

Thanks.

J

petergaraway
Participating Frequently
October 18, 2016

Hey Jonathan,

A few things to try:

  1. Modifying the duration of the morph cut transition

  2. Clear your caches/preferences.

  3. Create a new project and  import the old project into that.

Let us know how that goes.

Peter Garaway

Markus Scheibenbauer
Participating Frequently
May 29, 2019

This is so frustrating. The problem seems to persist, even after several updates. Workarounds like nesting, trimming and joggling everything around are ok for the moment... but in the end workarounds are NOT the solution. Is petergaraway Adobe actually adressing this problem?

Known Participant
February 23, 2016

I have same issue. Can someone solve this?

Ann Bens
Community Expert
Community Expert
October 10, 2015

For the red stripes: turn off MPE hardware (ist a know issue with El Capitan)

For the Morph cut you might want to read this: Adobe Premiere Pro Help | Troubleshooting the Morph Cut transition in Premiere Pro

mbpmAuthor
Participant
October 10, 2015

Stripes - As mentioned, I figured that one out.

Troubleshooting doc - thanks saw it. Mine really is a talking head. My two shots are just truncating a locked off camera. The problem is not that it takes a long time to complete. It doesn't seem to start. Am looking for some evidence that this analysis actually happens.

Thanks tho.