Skip to main content
Participating Frequently
October 28, 2025

Interpret Footage no longer working correctly

  • October 28, 2025
  • 13 replies
  • 426 views

Dear Adobe Support Team,

 

i think we detected a critial bug in Premiere Pro. Please see below:

 

=== Issue ===

"interpret Footage" no longer works as expected in more ways than one.
Leading to the following workflow breaking issues:


1. Exporting material takes infinite hours instead of minutes. (CRITICAL)
2. Making it no longer possible to do pull-down (25fps --> 24fps) or pull-up 24fps --> 25fps operations
without making it necessary to close and reopen the current project. (INCONVINENCE)

 

 

=== Steps to reproduce ===
For issue 1)

Import any ProRes 422HQ file with a PsF Field order. i.e. a 25PsF with upper field first.
Right click said ProRes 422HQ File and choose "Modify Clip" --> "Interpret Footage" --> under "Field Order" choose "Conform To" and select "No Fields (Progressive-Scan)"

Create a progressive timeline 25fps --> drop the clip into the timeline --> export the clip as ProRes 422HQ progressive.
Sending the Job to Media Encoder or directly export from Premiere makes no differece. The same problem occurs.

The "time remaining" time jumps up to 18 hours or more and keeps on counting up. A file gets created but is tiny in size compared to the time rendered. A feature film will probably take several days...


For issue 2)

take any ProRes file and change the framerate under "Modify Clip" --> "Interpret Footage" --> "Frame Rate" --> "Assume this frame rate" --> For instance 24fps ProRes and do a speedup to 25fps. Correct file length of the clip after frame rate change only becomes active after closing and reopening the project.


=== Expected result ===
For 1) File gets exported in less then 10 Minutes

For 2) Clip length immeditalty gets changed to the corresponding frame rate chosen without the need
of closing and reopening the project.


=== Adobe Premiere Pro version ===
Version 25.5.0 (Build 13)


=== Operating system ===
macOS Sequoia 15.7.1 Mac Studio M4 Max (base config)
macOS Sequoia 15.7.1 Mac Studio M3 Ulta (base config)

Also tested on a windows 10 machine with the exact same Premiere Pro Version mentioned above.
Same issue under the Windows Version.


=== Comparative information helps us understand more about when the issue occurs: ===
Does it affect all projects - YES


=== When did the problem begin? ===
Version 25.5.0 is our guess

 

Abobe mentioned issue leads us to believe that a critical bug was introduced with the "Interpret Footage" function overall.

 

13 replies

R Neil Haugen
Legend
October 29, 2025

I caught that. It was pretty clear.

 

But neither process, as I understand the technical stuff, involves a full pull-down.

 

I had a requirement to take 23.976p, 24p, and 29.97p to 29.97i, for potential broadcast. I asked a group of experienced b-cast editors (I've done so little I don't count myself 'there') about how to do it, thinking that going to Ae might be suggested.

 

They all said just make a 59.94 upper-field first sequence (29.97i) and drop the other clips on it, see if there's a problem. The potential problems to look for they said were slight changes in length and/or a bit of audio drift, both easily fixable.

 

At my surprise they said that's what they do first, and only do other things like run to Ae if there's clearly a major problem.

 

It worked. Which is no guarantee, but it's a quick thing to try. Takes about ten minutes to create the sequence and drop clips on, check playback, do a test export.

Everyone's mileage always varies ...
Participating Frequently
October 29, 2025

Hi Neil,

 

these are really two different scenarios. Sorry if this didnt come across correctly.

 

In one scenario we are interpreting PsF (picture segmented Frame) files that are inherently progressive.

Thats the case for digitized material from HDCAM-SR 25fps for example.

 

In the other case we are changing speeds from 24fps (cinema) to 25fps (DVD/german TV).

 

Hope this clears things up a bit. 

R Neil Haugen
Legend
October 28, 2025

Have you tried simply putting the clips on a sequence of the correct settings? That is what a whole group of b-cast editors told me to do, to get even 24p set on a b-cast type 29.97i sequence. As the most reliable method.

 

So with a 25i-fps upper-first just putting that on a 24p sequence ... how does that work?

 

Interpret Footage I've been told is really meant for more of a 3:2 pull-down, which you don't actually have that I can see.

Everyone's mileage always varies ...