Participating Frequently

Interpret Footage no longer working correctly

Forum|Forum|3 months ago
October 28, 2025
13 replies
425 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.

R Neil Haugen

Legend

I'm still curious about understanding your total workflow. You add the Psf clips to an interlaced timeline because ... perhaps you're starting with interlaced media?

Everyone's mileage always varies ...

M

Matthias23510098g8eyAuthor

Participating Frequently

@Rach McIntire

We can confirm that the issue persists in version 25.6.1 (Build 2)!

Would you be so kind and at leaset acknowledge the problem!

Thank You.

M

Matthias23510098g8eyAuthor

Participating Frequently

Hi @Rach McIntire

Were you able to re-create the issue at Adobe's end?

Is there maybe a better way to report this bug, because the forum kind of feels like screaming into the void...

Best

R Neil Haugen

Legend

Ah, now I think I understand your workflow issue. And yea, that's a thorny one. As you're telling Premiere to do different things at export by reading the file's 'native' state, not the Sequence state. I can see where that would hang.

Everyone's mileage always varies ...

M

Matthias23510098g8eyAuthor

Participating Frequently

Hi Neil,

i know you are trying to help. But what you have been told by experienced b-cast editors only applies to native interlaced footage.

When dropping PsF material (which is inherently progressive) onto an interlaced timeline and choose progressive during export you are basically de-interlacing progressive material. Which leads to lack of sharpness and jaggies. i have attached 2 screenshot zoomed in that show the difference. Not Sure if the image quaility comes across in this forum.

We flagg this issue all the time during QC because alot of editors dont seem to know the difference between interlaced and PsF.

As for you trying to recreate the issue. Please follow the steps i described.

But most of all i would like to hear from Adobe.

R Neil Haugen

Legend

So as a test just now, in PremierePro 25.5.0 (b13) ... as of this moment, the current shipping build ... I:

1) Selected a section of a 24fps progressive BRAW clip on a 24fps progressive sequence;

2) Exported this as ProRes 4444 clip in 29.97i, upper field first;

3) Checked the file in MediaInfo, file data: 29.97i upper field first;

4) Checked the auto-reimported exported file in Premiere's Media Properties, shown as 29.97i upper first.

Then I created a 23.97 progressive sequence in Premiere, and dropped that 29.97i clip onto that sequence. At the prompt, I selected do not change sequence settings.

Then I exported the clip, as 23.976p, and in MediaInfo, the resulting file shows as 23.976p.

And plays back just fine. A correct, 23.976 progressive file.

Note: no "interpret settings" dialog use whatsoever.

Everyone's mileage always varies ...

R Neil Haugen

Legend

The one thing you don't show having tested is the one thing that the very broadcast experienced users working for major b-cast companies said to do.

Take the interlaced ProRes file, and simply drop it on a progressive sequence set to the proper fps for the export. See what happens. Shouldn't take a minute to do.

It worked perfectly in my testing and use. As it normally does apparently for many standard b-cast workers.

Everyone's mileage always varies ...

M

Matthias23510098g8eyAuthor

Participating Frequently

Hi again,

we did a little more testing and it seems to be a gerneral ProRes issue and has nothing to do with old archive files.

How to re-create the issue:

1. Create a progressive 25fps timeline

2. Drop in any 25fps footage (progressive). For simplicity sake use the color bars generated by premiere.

3. Export as any ProRes Codec (we tested 4444 / 422HQ // Proxy) with upper field first. creating a 25PsF file.

4. Re-Import the newly created clip into Premiere. Modify the clip --> interpret as "no fileds progressive".

5. Drop modified clip into a progressive timeline.

6. Try to export the clip as any ProRes Coded with no fileds progressive.

7. Watch it encode for an eternity

Hope Adobe gets this fixed ASAP.

M

Matthias23510098g8eyAuthor

Participating Frequently

Hi Rach,

we not working with proxies.

These are finished archive masters of feature films or TV series.

I Just tested an MXF file and they export fine after modyfing them to progressive.

Rolling back to 25.3.0 (Build 84) did not resolve the issue!

Following please find the output from MediaInfo of an example file. Hope this might help narrow it down some more:

General

PA_20182002_1135_Rampage_2_Feature_20EN_20190115.mov

Format : MPEG-4

Format profile : QuickTime

Codec ID : qt 2005.03 (qt )

File size : 113 GiB

Duration : 1 h 29 min

Overall bit rate mode : Variable

Overall bit rate : 181 Mb/s

Frame rate : 25.000 FPS

Encoded date : 2019-01-15 12:06:08 UTC

Tagged date : 2019-01-15 13:27:57 UTC

Writing library : Apple QuickTime

Video

ID : 1

Format : ProRes

Format version : Version 0

Format profile : 422 HQ

Codec ID : apch

Duration : 1 h 29 min

Bit rate mode : Variable

Bit rate : 179 Mb/s

Width : 1 920 pixels

Height : 1 080 pixels

Display aspect ratio : 16:9

Frame rate mode : Constant

Frame rate : 25.000 FPS

Color space : YUV

Chroma subsampling : 4:2:2

Scan type : Interlaced

Scan type, store method : Interleaved fields

Scan order : Top Field First

Bits/(Pixel*Frame) : 3.452

Stream size : 112 GiB (99%)

Writing library : Apple

Language : English

Encoded date : 2019-01-15 12:06:08 UTC

Tagged date : 2019-01-15 13:27:57 UTC

Matrix coefficients : BT.709

Audio #1

ID : 2

Format : PCM

Format settings : Little / Signed

Codec ID : in24

Duration : 1 h 29 min

Bit rate mode : Constant

Bit rate : 1 152 kb/s

Channel(s) : 1 channel

Channel layout : C

Sampling rate : 48.0 kHz

Bit depth : 24 bits

Stream size : 736 MiB (1%)

Language : English

Encoded date : 2019-01-15 13:23:04 UTC

Tagged date : 2019-01-15 13:27:56 UTC

Audio #2

ID : 3

Format : PCM

Format settings : Little / Signed

Codec ID : in24

Duration : 1 h 29 min

Bit rate mode : Constant

Bit rate : 1 152 kb/s

Channel(s) : 1 channel

Channel layout : C

Sampling rate : 48.0 kHz

Bit depth : 24 bits

Stream size : 736 MiB (1%)

Language : English

Encoded date : 2019-01-15 13:23:04 UTC

Tagged date : 2019-01-15 13:27:56 UTC

Other

ID : 4

Type : Time code

Format : QuickTime TC

Duration : 1 h 29 min

Frame rate : 25.000 FPS

Time code of first frame : 00:00:00:00

Time code of last frame : 01:29:17:01

Time code, stripped : Yes

Language : English

Encoded date : 2019-01-15 13:27:56 UTC

Tagged date : 2019-01-15 13:27:56 UTC

R

Rach McIntire

Community Manager

Hi @Matthias23510098g8ey,

Thanks for the detailed bug report. Are you working with proxies at all? Is ProRes 422HQ the only codec you're using? Could you give more details about the video format? Does rolling back to 25.3 resolve the issue?

Sorry for the frustration and thanks for reaching out.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded