P: Morph cut - Analyzing in Background never completes

Fool's errand, man.  Ask yourself if it's worth the opportunity costs.  At the end of the effort chances are you're not going to have a consistant answer to the bug.

This is a calculus that needs to be considered when using Premiere.

Good luck, but my best advice is to throw in the towel and just not use the "feature"

@Michael Grenadier 

I'm on

1. a Wndows 10 machine, or several of those,
2. both 128 GB RAM,
3. all M2 key disks,
4. one with an i7 9850 and a Quadro RTX 3000,
5. one with 2 Xeon e5-2667 v5 with a Quadro M5000.
6. Footage is ProRes 4:2:2, FHD.

Happens on both computers, also with h.264 footage, also with transcoded h264 footage. It is mostly from a DSLR HDMI output to an external Atomos recorder. Maybe we can narrow this down after all!

Actually there's a logic here.  We're trying to reduce the workload on the computer.  in an mpeg format like mp4, each frame does not exist completely in the original file ((except for the occasional i-frames)  , but rather a relationship between the previous frames and the next frames.  So Premiere needs to decode each frame, calculate the morph cut and reincode (unless you've chosen a all i-frame format like prores as your preview format).  I'm sorry if I'm not making this clear, but understanding how different codecs work is useful knowledge.  Post back with any questions, and perhaps I can attempt to explain or someone can point you towards a better explanation.  The fact is that I rarely if ever have an issue with applying a morphcut.  It may because I'm working on the mac (not a particularly high powered one - a 2022 macstudio with 32 gigs of RAM).  and on certain pieces I use a lot of morph cuts.   And yeah, we maybe just lucky.  

Maybe other people who are NOT having problems with applying a morphcut can describe their system specs and perhaps we'll see a pattern.

Yes, I feel that those who are suggesting re-encoding with a different codec are just getting lucky. Like many here, I have the same footage, from the same camera, same day, same setup on the same tripod, and it's entirely random whether or not PPro decides if the morph cut will work. Sometimes changing its duration from maybe 6 frames to perhaps 4 frames works (and it still takes AGES to calculate just those 4 frames on my reasonably high-spec PC! Although, if I look at the activity monitor, it shows only 1 of my 16 cores being used for the morph cut to possibly process).

And also yes - ditch the AI stuff and focus on fixing the broken stuff, please!

I'll try out Resolve as well - PP is working really well in most cases, but like with Photoshop, Adobe seems to care more about implementing AI, which is a 50:50 shot at wasting lots of time, instead of giving a real time preview for Radial Blur, for example. AI is by no means production ready, it's a nice toy.
Just a shame because of all the plugins, assets etc. I purchased for PP.

@Michael Grenadier  The Material is ProRes 422HQ.

In later clips, Morph Cut worked again - so it just decided to not work with some of those clips. All clips came from the same camera, same recorder, same settings, same day. "Record" and "Stop"

started using Premiere (certainly wasn't "Pro" back then!) in the early 90s - obviously it was absolutely hopeless for any serious work, so graduated (skyrocketed?) to Quantel Editbox & Henry. Then FCP and hardware that could actually handle video came along...and then Apple destroyed FCP with iMovie Pro or whatever, so back to PPro. The time has probably come to move on again.

Same journey here.  I originally liked what Premiere was doing because if you were deliberate with those early versions you could actually kick out stuff on par with super expensive gear.  Remember, most video production was hardware/tape based.

Anyway, Adobe just has a business model that would rather exploit than assist it's customers.  So, moving on...  As before as again.

After many, many failed (and some successful) PPro morph cuts, I was planning to take my current project to Resolve and use its excellent Smooth Cut (which just works - usually in real-time, like this example here: https://www.youtube.com/watch?v=cyFOH9HZGkw), but the free version doesn't recognise 10-bit H.264 footage, which is what my source material is. I should have just stumped up the relatively small amount to buy the full version, but I thought I'd just cover the cuts with B-roll instead in PPro.

The next time I get a job like this, I will absolutely jump to Resolve - I will try to set aside some time to learn it thoroughly, and begin the transition away from PPro - and I'm saying that as someone who is very keen on PPro and AE - when they work, they're great bits of software - as they should be for the price. I started using Premiere (certainly wasn't "Pro" back then!) in the early 90s - obviously it was absolutely hopeless for any serious work, so graduated (skyrocketed?) to Quantel Editbox & Henry. Then FCP and hardware that could actually handle video came along...and then Apple destroyed FCP with iMovie Pro or whatever, so back to PPro. The time has probably come to move on again.

I gave up on Morph Cut a long time ago, but always read these announcements when they come up. There doesn't seem to be a consisten formual for when it does or doesn't work. Now that jump cuts are "fashionable" I just live with that if covering the edit with B-roll isn't an option. Much like AE's Roto Brush, Morph Cut was so appealing yet consistently disappointing.

Utterly primitive single track talking heads sequence - Morph Cut just decides to stop working in the middle of the project. "can't access clips", after reboot not even that. I tried adding cuts before and after the desired morph, restarting PP, rebooting, shutting down & rebooting. Latest recommended NVidia driver, Win 10