P: Morph cut - Analyzing in Background never completes

[mbpm]

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.

[Joshua31740381vi4n]

Hi,

When I look for the "convert to master clip" tick box, there's one that says "convert to source clip", but I can't tick or untick it. Is there another way?
Thanks,

Josh 

[R Neil Haugen]

They removed "master" from their lexicon for "modern" reasoning. It's now all "source", which if you think about it, in the use it gets, is more accurate.

[abstuffit]

I literaly have it in 2024. 

[ilucris]

HTH

If you apply morph cut only to one transition, wait to analyze, it does it's job, very very very slow (20-60 seconds on a mac m1), but it does it's job.

If you apply it to multiple clip at once, it will analyze the last one added and all the rest will remain at analyzing in background.

It will get stuck if you other things so the only way it works for me is one by one and wait for it to analyze.

The feature is broken and won't probably get any fixing since it's over a decade old. 

This is why people switch to resolve!

[Corniger]

I also found sometimes, it just takes really, really long. I left my workstation out of frustration and upon my return, the morph was done.
I don't understand why this seems unimportant. An excellent tool to make interview cuts less obvious.

[AndrewTheGreat]

Well, the only way to settle this in 24 is to make the clips shorter by cutting them before and after the part you put the transition on. Morph cut somehow tries to analyse the whole clip so if you have two 10-minutes clips you wanna morph, Morph cut will analyse twice as 10 minutes...

[AndrewTheGreat]

Well, can't say this helps too. Got a 4 and a 7 secs clips and they have been analyzed by the morph cut transition for 17 minutes already... The Morph Cut transition DOES NOT WORK...

[AndrewTheGreat]

Premiere Pro 24.1 built-in transition Morph Cut seems to have stopped being usefull at all since it never finishes analysing in the background with my videos.

My workflow 1 - create a sequence with the settings below, import the footage, cut it, place the morph cut between the clips, colorgrade and use effects afterwards.

My workflow 2 - same except that I cut 2-3 seconds at the end of the first clip and 2-3 seconds at the beginning of the second and in between those secondary parts I place the morph cut transition. 

In both cases morph cut keeps analysing the material for eternity. It does sometimes work (rarely and I didn't catch the pattern) but most of the time it goes into this analysing phase and never finishes.

- nesting does not help

- rendering and replacing to some other format does not help

- flushing cache does not help

- changing the sequence settings does not help

- didn't check other video formats since my current client gives me only footage from one and the same camera

- MERCURY RENDERER immediatelly helps BUT makes it next to impossible to work further. Switching back to CUDA brings back the endless analysis. 

The footage I use:

Type: MPEG Movie
Image Size: 1920 x 1080
Frame Rate: 59,94
Source Audio Format: 48000 Hz - 16-bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Pixel Aspect Ratio: 1,0
Color Space: xvYCC709 (IEC61966_2_4)
Color Space Override: Off
Input LUT: None
Video Codec Type: MP4/MOV H.264 4:2:0

My PC:

Core-i7 13700 KF, RTX 4080, 64 Gb Ram, 7000\6000 speed SSD. Latest Win10 updates, latest drivers for all the PC parts. The current Nvidia driver is 546.65.

I REALLY need this transition to work since there is no alternative for Premiere pro and Morph cut is the only way to conceal cuts in a talking-head footage in a way noone will notice. Please, Adobe, the new audio workspace is a good thing but do not forget your old features.

[Ann Bens]

Set sequence to 59.94 framerate

Turn off max render and quality and linear color and try again.

[AndrewTheGreat]

Unfortunatelly nothing helped. The transition sometimes worked though, but at the same time it sometimes did not. Such an inconsistency is not acceptable in my pipeline

[Tom34127479bu9o]

Morph cut is great when it works.  More than half the times I try to use it the program fails to analyze.  

[AndrewTheGreat]

Ladies and gentlemen, those suffering this issue, please name your processors. I have a suspicion that Morph cut refuses to work only on intel index F or AMD processors, and those having an integrated iGPU do not have such a problem

[spamwich]

Not an expert here, but after many failed attempts, I ran the clip through Handbrake---changing the encoding to H.264 and setting the FPS to match my sequence (24). Working now.

NOTE: For really stubborn clips, I play the clip in a separate player and record that playback using Windows video capture (Win-Alt-R). That has always worked...assuming I can accept the quality of the capture.

[Hiddenpictures Ltd]

It's not working  (just analyses in background forever) as of Match 1st 2024- so that's at least eight years now. I don't mind things not working actually - it's complex, but for Christ's sake tell us it doesn't work and not to bother with it and then we won't waste time on it ever. 

[František222715252jw3]

The sequence needs to exactly match the source video, otherwise it might cause problems. It can be pretty annoying but it works - at least for me.

[Glenda29038675honx]

Same here.  Issues seem to have resolved for me with the latest updates. I don't have to nest sequences anymore with the latest versions.  I know it says "analyzing in background" but I now always wait with the playhead over the morph until its done analyzing, because I don't quite trust it yet. 😄   But it only takes like 30 seconds to a minute. 

[Josh32581006mhd1]

I just read one comment in here that said it might be and Issue with file size and/or being a render issue sice the morph cut was being applied to the 'same clip' (thats the point - haha)....BUT they did suggest, essntially doing a render and replace of the clips on the timline and then re-aplying the morph cut. Which is a solid idea, however, I was having the same issues as you, I was about to 'render and replace' but I had to FLATTEN the clips cause they were in a multi-cam sequence!!! I flattend, applied the morph cut and it worked as we've all come to expect....so...yeah....doesnt seem to work on multi-cam/nested clips.  -Peace

[Tom34127479bu9o]

Thanks for the reply.

My typical use of it is during an interview to cut out stumbles or remove asides and it isn't in a place where I would normally cover with b-roll. So very little changes in frame. And I won't even try if the person's head isn't essentially in the same position. So it's the perfect way to use Morph Cut, in my estimation.

While I feel I've tried all sorts of methods to kick the Morph Analyzer into action to no avail, there is good news. I sort of dread updating my Premiere, but I did... it sort of did it without my permission. In any case, Morph is now working better for me than it ever has. So maybe they're trying to address the concerns.

Thanks for reaching out.
Tom

[Peru Bob]

I sort of dread updating my Premiere, but I did... it sort of did it without my permission.

By @Tom34127479bu9o 

You can turn that off in the Creative Cloud app.

[crollur]

well i'm using premiere pro 2024 [version 203.0 (build 59)] and still have to uses every tsingle tip in this thread to get it to work. and sometimes it still doesn't and i have to use some other meathod of transition. so it's clearlyt still buggy and not fixed

[Michael Grenadier]

this is an enormous thread and I don't have the time to review the entire conversation, but...  I'd suggest transcoding your source clips for the morph cut to an all iframe format like the appropriate flavor of prores rather if the original clips are an mpeg format like mp4 where each frame is not discreet...  Happy to go into more detail of my thinking on this if anyone's interested.  I almost always transcode my source material to prores or at least create prores proxies...  and never see this problem..

[Bennett5FA1]

It's been 6 years and this is still the only workaround that worked. Thank you!

[angusa83618842]

Nest the top clips you want to apply the morph cut to, inside the nested clip apply the morph cut - this is a workaround that shouldnt need to be made - Adobe have had almost a decade to fix this and they haven't - why are we paying so much when they don't iron out bugs like this a decade later?

[Kevin-Monahan]

Hello mbpm, and community,

I'm Kevin from support, one of the moderators here. Thanks for the bug report.

I apologize for the issues this effect sometimes causes. A product team member would be better at explaining this, but in my own experience using it, it's not a new effect and was created when certain workflows didn't exist yet. Reading through here, nesting can assist with legacy scaling issues, and transcoding can help with other unforeseen issues. The thread contains some other really great advice.

I highly advise you to read the documentation:

See this blog post: https://adobe.ly/3SfBDiD

See also the user guide: https://adobe.ly/3SfBWtN

This thread really lacks details about people's systems, media, and workflows. If you are experiencing trouble with the effect, please provide full details about your system, the media, and the workflow you use so that the team, Adobe Experts, and other community members can better assist you.

I hope that a product team member can chime in with more details.

Thanks,
Kevin

[Kevin-Monahan]

The team needs more info about your system and media to assist with morph-cut issues.

Feel free to create a feature request for an updated effect here.

Thanks,
Kevin