Optical Flow Ghosting Bug in PPro but not AE

Hi, @reuko Can you give me a link to your video to test it out? I tried to reproduce the issue in Pr 24.5 and Ae 24.5 with a stock footage and failed. I imported the file in Premiere Pro, slowed it down by 75% and then sent its copy to Ae via the Dynamic Link, then applied the interpolation in both the programms - same result in Premiere and Ae.

Hello @reuko,

Thanks for the message. It’s been a while since you filed this bug. Are you still having this issue? Let us know. I've asked a product team member to look at this issue.
 
Thanks,

Kevin

Hey! I was wondering if there was any updates or confirmation of this issue with the developers? This is a pretty serious blocker for my project at the moment and it would be helpful to know if this is being looked at.

Thanks!

I apprecaite the care and attention to this issue! If there was some way to use the After Effects version of Optical Flow in Premiere Pro, that would be a perfect fix for this.

Is it possible to track the status of this bug? This is a blocking bug for the project I'm working on so I'm happy to offer help with testing new beta versions once a fix has been pushed.

Thanks!

OK, @reuko.

Sorry for the mix-up. You said, "I have seen this same bug/weird result in earlier versions of Premiere Pro as well." So, I thought you may have already filed a bug on the issue. It would be my mistake if that were not the case.

Thanks for confirming your observations and the difference between the fixed bug and your bug. The developers will appreciate that. I'll continue to advocate for a fix for this problem. Sorry for the frustration here.

Thanks,
Kevin

@Kevin-Monahan I'm sorry I'm not sure I understand. This is my first bug report on this issue, and the issue in the link is not the same problem because that is specific to the M1 Mac, and this issue is present on Windows as well as Mac. Also there is no visual example of the Optical Flow issue in that thread, so I cannot confirm it is the same.

I will look for your previous bug report and read it. Is it the same bug? Let me know. It would be great to combine these entries so that the team can be focused on the issue. If so, I will try to find your bug report and join it here. Please let me know. I appreciate your cooperation and help.

I looked for your previous bug report but could not locate it. Do you have a URL, please? That would be great.

Thank You,
Kevin

Hi @reuko,

A bug in a previous version was fixed along these lines (23.2). Can you read the last report bug here to see if this might also be your issue? It's always possible that the bug might be recurring.

I will look for your previous bug report and read it. Is it the same bug? Let me know. It would be great to combine these entries so that the team can be focused on the issue. If so, I will try to find your bug report and join it here. Please let me know. I appreciate your cooperation and help. I would like to see a fix for this issue as soon as possible. Proper speed effects are critical to any video editor.

Thanks,
Kevin

Hi! @Kevin-Monahan  I'll gladly clarify that I initially reported this issue being present in Premiere Pro 2023.5, but have also tested this in the latest release Premiere Pro 2024.2.1 and the latest Beta Premiere Pro 2024.4 with the same issue. All versions of After Effects I have tried this with do not have this issue with Optical Flow / Pixel Motion.

Let me know if you need further clarification or details!

Good day, @reuko,

I hope you had a good weekend. Thank you so much for providing the added info. That will be very helpful for the team to reproduce the issue.

In re-eading the original info more carefully, I was able to note that you are filing a bug on a previous version. Bugs from previous versions are not considered unless they persist in the current version. Is that the case? The developers would prefer that you test the issue with the most current version of the application and report back with the results. In the meantime, I'll check to see if the current version has the bug fix. I hope so! Thanks for your cooperation and patience.

Cheers,

Kevin