Skip to main content
Known Participant
October 19, 2022
Question

MXF files drop frames after premiere pro 2023 update

  • October 19, 2022
  • 19 replies
  • 18614 views

This latest update still has massive drop frames and black frames when editing with MXF files. This has been occurring since April's update. Adobe closed my case without addressing the bug. I originally thought it was my processor 3.3 GHz 12-Core Intel Xeon W.

For reference I shoot with C300 mark iii and the c70. I am a professional filmmaker and have been in this industry for 25 years. The reason I left Final Cut in 2008 was because of major program errors like these. We need a stable program and tech support that listens. 

This topic has been closed for replies.

19 replies

Participating Frequently
March 24, 2024

I had this same issue and it was horrible to deal with. I ended up building a new PC and buying top of line Components. Just to find out it was Adobe and MFX Long GOP. I have to shoot All intra to use on any PC.... I literrally have wasted thousands of dollars and wasted SO much Time. Just make proxies? just update premiere? Use beta? Its crazy how many fan boys will fight for ADOBE OR CANON. The MXF was working fine for me until an update. 

Participant
January 22, 2024

I am still having the problem. Especially when i export a video which includes AE projects with mxf files from my C70. Same AE project in the same PP timeline with ATOMOS NINJA Flame files are no problem...

Participant
March 6, 2024

Just coming across this issue after I updated Prem Pro 24.2.1 (Build 2). Have been using Pro now for a number of years and the Sony has been my standard old one.  Just working on a regular project and keep getting error messages.  

Participating Frequently
October 11, 2023

I'm glad I'm not the only one providing very helpful feedback to Adobe, yet disapointing they still ignore them.

Or perhaps they simply can't technically fix it?

For me the issue is very easy to recreate (and have let Fergus Hammond know) it's when I use the Slip Tool (Y) on 4K footage.

Premiere Pro slip the first few frames and then freezes making it impossible to then see which start and end frames to pick.

Participating Frequently
October 11, 2023

In December 2022 I spent a considerable amount of time with my colleague including a zoom call with Fergus Hammond from Adobe explaining this issue with MXF files in 4K.

I even specifically created and uploaded a project with large files to demonstrate this issue.

So Adobe please stop asking us to share our problem with you as you know perfectly well what it is.

I updated from the FS7 to the FX6 this year and was hoping it would fix this issue but got even worst.

So every time you release an update I'm hoping you will have finally fixed it but I'm always disappointed.

I enjoy using Adobe products but this is becoming a huge deal breaker as it makes editing so difficult and time consuming often having to guess what I do rather than seen it on the screen!

And even when spending time to try help you understand the isdue (with no offer to be compensated for our time) nothing has happened.

Very disappointing and currently reluctantly looking at other options.

Known Participant
October 11, 2023

Oh wow! The exact same thing happened to me. I sent them a huge amount of my raw footage and a project file. They told me that they cant recreate the problem. I think it happens most when I'm ingesting footage. If you try to do anything in the program when it's ingesting it looses its mind. So I usually give it an hour to load everything properly. It's still super slow no matter what I do though. 

Richard Alderson
Participating Frequently
September 15, 2023

This issue seems to have got worse in the 2023 version. Just updated to 23.6.0 and a large MXF timeline is almost unplayable. I created medium resolution ProRes proxies overnight, but switching to proxies in the timeline was no better. I then donwloaded the current Beta version of Premiere, and opened a copy of my project. The MXF sequence appears to play seamlessly. But do I want to risk editing a large project in a Beta version, knowing there could be other unforseen issues? I am tempted to try the edit in Beta, and then possibly export XML back to v 23.6 for the grade.

 

The project I am working on has 2.5TB of media, and roughly consists of 6 x 2 hour rough assemblies to be cut down to around 30 mins each. There are 3 cameras, 4 tracks of video and 8 Wav audio tracks for each sequence. The playback issue in 23.6 persists irrespective of my sequence settings (have tried ProRes 422, AVC Intra, DNX and more...)

 

Richard Alderson
Participating Frequently
September 17, 2023

A further update on this issue...

 

When I started to work on my project in the Beta version, non of my user settings had activated, so I started switching on settings in the timeline 'spanner' menu. Suddenly everything became very very slow again. I the reversed the process, turning options off one by one, and it turned out to be 'Show Duplicate Frame Markers' that was causing the issue.

 

This project has a very high amount amount of dupliacetd footage, as it consists of three different studio setups, filmed over three differnent days, of participants watching the same material. The studio footage is all MXF, but the dupliacte material being watched is all ProRes, and my timeline is set to ProRes as well.

 

Now I know the isssue I can work without Duplicate Frae Markers, but it would be better to have this active for my workflow.

 

I have edited this type of project on older versions of Premiere without issue. It is onlt happeneing on the 2023 version. Is anyone else experienceing this issue?

Inspiring
October 11, 2023

I too have observed that duplicate frame slowdown system.

For me another posiible factor for slowing down is too many markers. I have 1 hour multicam project and when a make scene detect and put marker on scene change...navigation on timeline start to be very laggy. If I delete all scene marker timeline response is perfect again.

Community Manager
June 19, 2023

Hi All,


Sorry for this issue. If you are still facing this issue in the latest Premiere Pro version, please share some problematic media/project files https://helpx.adobe.com/creative-cloud/help/share.html . We will check it at our end and report back.


Thanks, Mayjain 

Known Participant
March 29, 2023

I have simmilar problem. All Sony fs7 mxf files has a terrible lag make it unable to work with. It was getting worse and worse since 22.63 update. I need to transcode all footage to ProRes and than start editing. Files specs are the following:

 

My PC spec is:

Participating Frequently
June 7, 2023

Having the same problems here with my pc. No other footage has these problems! Mxf files have serious lag times, also take forever to import, and when I choose "create proxies" and try either a quick time low res, or h.264, each proxy is taking 2 hours! For each 10 GB file that's only about a minute of footage! Makes no sense. It's basically made my entire film unusable

Cybersoft Creative
Participant
January 29, 2023

Use DaVinci Resolve

Participant
March 2, 2023

Same issue here on AE 2023.  Not happened before and worked worked with this actual footage no issue on same computer AE 2022.

3.8 GHz 8-Core Intel Core i7

AMD Radeon Pro 5700 8 GB

64 GB 2133 MHz DDR4

Version 13.2.1 (22D68)

 

Can't tell details of footage as client supplied same.

SpaceCherryFilms
Inspiring
December 11, 2022

I just installed the newest version today 23.1 and now everything plays back fine with no frame substitution 

Participant
December 11, 2022
SpaceCherryFilms
Inspiring
December 13, 2022

Sorry for the delay, here's my specs

 

WINDOWS 11 22H2, 22621.900

AMD Ryzen 9, 3900x

96GB Ram

4TB Samsung 980 Pro m.2 SSD

GTX 1080 TI

 

Participating Frequently
November 30, 2022

Adobe are you reading this? Are you working on it? Can you tell us if and when it will be fixed?

I'm also seriously considering moving onto another editing platform as this problem with MXF files makes Premiere Pro unusable.

Known Participant
December 1, 2022

They are not listening. Just move to resolve, you'll be so much happier.