• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
44

P: Frame substitution attempt aborting error - .MXF Files Fixed in version 25

Explorer ,
Mar 03, 2024 Mar 03, 2024

Copy link to clipboard

Copied

UPDATE 10-14-24:  

MXF file frame substitution errors has been fixed in version 25 of Premiere Pro 

 

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

I've seen a number of posts about this, and am now running into the problem myself. Although there are a few differences I'd like to share that I'm hoping may shed more light on what appears to be a longstanding issue.

 

Specs: M3 Max Macbook Pro (64GB RAM), Sonoma 14.3.1, Premiere Pro 24.1.0

 

The .MXF files were shot XAVC-I from the Sony FX6 shot on a V90 card. I copied the entire memory card structure to my internal drive, and imported the clips using the media browser. The clips are 59.94 fps and 23.976 fps on a 23.976 timeline.

 

As I perform regular editing tasks (slowing 59.94 clips to 40%, adding clips to timeline, scrolling through), I get these error messages.

 

BUT, here's the kicker: I'm not actually seeing dropped frames yet. For one of the clips I received the error on, I decided to go to the source window and scroll through frame by frame. I didn't see any black frames, but scrolling through did create 9 new error messages at different frames.

 

Aside from the error popups being annoying, this is a project that many people are depending on. If these dropped frames actually do end up showing, I'll be in a bad spot. It seems as though with every new project, I have to factor in at least a day to deal with errors or bugs in Premiere. I shouldn't have to be constantly fighting with the tools that allow me to do my job. Moreover, the C70 and FX6 both shoot in .MXF and are fixtures of video production. Frankly, I'm taken aback that there hasn't been more meaningful support from Adobe on this.

 

I'm currently creating ProRes Proxies to see if that may solve the issue, but I'm concerned that this will only solve the problem in editing, and the error (dropped frames) may show up once exported.

 

Does anyone have thoughts on why this may be happening? Is it time to switch to Resolve like everyone seems to be saying, or could this be a workflow issue on my end?

 

Many thanks!

Bug Fixed
TOPICS
Editing and playback , Graphics , Import and ingest , Performance or Stability

Views

15.3K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
replies 385 Replies 385
385 Comments
Community Beginner ,
Jul 30, 2024 Jul 30, 2024

Copy link to clipboard

Copied

Forgot to mention, running on Windows 11.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 30, 2024 Jul 30, 2024

Copy link to clipboard

Copied

Hi @wildbill - We have been investigating this issue and are working on some theories as to why this may be happening.  It would be helpful if you could try some troubleshooting for us.  

Do you have any third party plugins installed?  

Can you hold down "SHIFT" while launching Premiere and check the boxes 

"Reset Plugin Cache" 

"Disable third-party plugins (one time only)" 

"Clear media cache files" 

Can you go to the wrench menu in the source and program monitor and change the playback and paused resolution to "Full"

 

Let us know if you can try any of these steps, thank you and apologies for the error messages.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 30, 2024 Jul 30, 2024

Copy link to clipboard

Copied

Hi Jamie,

 

I did as you suggested regarding startup options and setting source/program to full.  Unfortunately, no joy – still getting warnings.

The first two came quickly while assets were being loaded.

The second two came as I was adjusting my multi-camera timeline.

Premiere Pro Beta (startup options from support applied).jpg

 

BTW – I love the new ability to read LTC timecode from camaras that require TC to be written to an audio track.  I was able to multi-select the files and then right-click/Modify/Timecode/Linear Timecode (LTC) all in one quick operation.  Tremendous efficiency boost for doing multi-camera work!

 

/BILLW

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 30, 2024 Jul 30, 2024

Copy link to clipboard

Copied

Additional warnings after a few more minutes of editing.  Notice audio file read warnings too.

Premiere Pro Beta (additional warning messages).jpg

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 30, 2024 Jul 30, 2024

Copy link to clipboard

Copied

HI @wildbill - I'm glad you are using and liking the LTC feature!!  Do you use markers in your workflow?  There is a bug that when using markers you will encounter frame recursion errors.  We are tracking the audio not found,  Is your .WAV file multichannel and if so how many channels?  Would you be able to send me any of the files you are having issues with?  You can email me a link to jamiec@adobe.com 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 30, 2024 Jul 30, 2024

Copy link to clipboard

Copied

No, I'm not using markers.  

The .WAV file is 10 channel 32 bit float from a Sound Devices MixPre 10ii.  The MixPre has a 4gb file limit, so the original recording covered 2 files, and was subsequently combined into a single .WAV file using Adobe Audition.
I will send a link to your email.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 31, 2024 Jul 31, 2024

Copy link to clipboard

Copied

In the wrench menu do you have "display first field", "display second field", or "display both fields" selected?  Are you connected to an external monitor?

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 31, 2024 Jul 31, 2024

Copy link to clipboard

Copied

I looked under the wrench menu for the Program monitor, and I don't see those options.

Yes, I am connected to an external monitor via HDMI.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 31, 2024 Jul 31, 2024

Copy link to clipboard

Copied

Sorry,  I just noticed that the "Field" options are in the wrench menu but they are greyed out on my multicam timeline.

Same thing from my sequence with all the individual clips stacked up that the multicam timeline is drawing from.

Wouldn't this be expected for 23.976p sequences?

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 31, 2024 Jul 31, 2024

Copy link to clipboard

Copied

Can you try unplugging your monitor and see if that helps?  Agree with you on the 23.976 sequence but there are cases with AVC long gop media where they can be shot with the same frame rate and be either Progressive or Interlaced.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 31, 2024 Jul 31, 2024

Copy link to clipboard

Copied

Ok, I turned off the "Video Stream" (under Preferences/Playback) for my external monitor.  Playing around with my multicam timeline for a few minutes has not resulted in any warnings for either .mxf or .WAV files.  I'll experiment for a bit longer and let you know if anything crops up.

BTW, the release version (24.5) is unuseable for me with this same project.  It frequently crashes completely after just 5-10mins of editing. I wonder if turning off the external monitor would help with this as well?  I've read on the forums that the cause for the crashes are related to .mxf files too, so maybe turning off external monitor may be a stopgap until a fix is out....

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 31, 2024 Jul 31, 2024

Copy link to clipboard

Copied

I appreciate your help and thank you again for troubleshooting.  We are investigating and do have some theories as to why this is happening as we try to implement a fix.  Please keep us updated!

Status Investigating

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 02, 2024 Aug 02, 2024

Copy link to clipboard

Copied

Hello,
I'm still encountering the same issue. Even with 1/4 resolution the playback is not fluid and MXF issue. Going back to CC2023 or thinking about cancelling my subscription, this is really anoying. Please found a solution..

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 02, 2024 Aug 02, 2024

Copy link to clipboard

Copied

Hi @Anaëlle R - I am sorry you are still experiencing these issues. Are you using an external monitor while editing?

Votes

Translate

Translate

Report

Report
New Here ,
Aug 03, 2024 Aug 03, 2024

Copy link to clipboard

Copied

Screenshot 2024-08-03 at 5.19.37 PM.png

 Why is this coming ? This is so much frustrating. Hav tried many different types of menthods to overcome this but nothing is working. I was editing a film having almost 5 TB of data. Tried deleting Cache, Tried changing the renderer but since new mac update it doesn't allow anymore. Tried switching it to internal storage than a HDD. Any specific solution than going to and fro for many other solutions.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 05, 2024 Aug 05, 2024

Copy link to clipboard

Copied

Hi @yogendras31 - Can you give some more information on your computer specs? Also, What version of Premiere are you using?  Do you have any plugins installed?  Are you using an external monitor?  Can you right click on one of your clips and select "Media File Properties" then post a screenshot.  Thank you.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 05, 2024 Aug 05, 2024

Copy link to clipboard

Copied

The status of this bug report has been updated.

Status Needs More Info

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 05, 2024 Aug 05, 2024

Copy link to clipboard

Copied

Hello, I have such a problem that Premiere pro version - 24.5.0 build 57, constantly crashes without errors when working with MXF containers, in any case, shot on sony pwx-z90. There is a computer next to it with the Premiere pro version of 23 years old and the program (premiere) works perfectly with the same files.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 05, 2024 Aug 05, 2024

Copy link to clipboard

Copied

J ‘ai exactement les mêmes problèmes avec les fichiers MXF De canon xf605

Envoyé de mon iPad

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 06, 2024 Aug 06, 2024

Copy link to clipboard

Copied

Hi @Никита5E27 and @reboussier - Please see the pinned post and provide additional inofrmation.  Thank you.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 06, 2024 Aug 06, 2024

Copy link to clipboard

Copied

My pc - AMD Ryzen 7 2700, Motherboard - B450 pro4, Memory DDR4 32Gbytes dual channel, GTX 1660 6 gb.  My plagins for the Premiere pro(24.5.0 build 57). ATOM-X, Red gigant all plugins.I use two monitors for my PC, no external one

Media file info SONY PXW-Z90

General
Format : MXF
Format version : 1.3
Format profile : OP-1a
Format settings : Closed / Complete
File size : 149 MiB
Duration : 25 s 526 ms
Overall bit rate mode : Variable
Overall bit rate : 49.0 Mb/s
Frame rate : 29.970 FPS
Encoded date : 2024-08-05 03:27:10.000
Writing application : Sony Mem 2.00

Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High 4:2:2@L4.1
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference : 2 frames
Format settings, wrapping m : Frame
Format settings, Slice coun : 4 slices per frame
Codec ID : 0D01030102106001-0401020201316001
Duration : 25 s 526 ms
Bit rate mode : Variable
Bit rate : 44.4 Mb/s
Maximum bit rate : 50.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.714
Stream size : 135 MiB (91%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio #1
ID : 3
Format : PCM
Format settings : Little
Format settings, wrapping m : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 25 s 526 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 29.970 FPS (1601.6 SPF)
Bit depth : 24 bits
Stream size : 3.51 MiB (2%)
Locked : Yes

Audio #2
ID : 4
Format : PCM
Format settings : Little
Format settings, wrapping m : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 25 s 526 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 29.970 FPS (1601.6 SPF)
Bit depth : 24 bits
Stream size : 3.51 MiB (2%)
Locked : Yes

Audio #3
ID : 5
Format : PCM
Format settings : Little
Format settings, wrapping m : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 25 s 526 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 29.970 FPS (1601.6 SPF)
Bit depth : 24 bits
Stream size : 3.51 MiB (2%)
Locked : Yes

Audio #4
ID : 6
Format : PCM
Format settings : Little
Format settings, wrapping m : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 25 s 526 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 29.970 FPS (1601.6 SPF)
Bit depth : 24 bits
Stream size : 3.51 MiB (2%)
Locked : Yes

Other #1
ID : 1-Material
Type : Time code
Format : MXF TC
Frame rate : 29.970 (30000/1001) FPS
Time code of first frame : 07:30:28;13
Time code of last frame : 07:30:53;27
Time code settings : Material Package
Time code, stripped : Yes

Other #2
ID : 1-Source
Type : Time code
Format : MXF TC
Frame rate : 29.970 (30000/1001) FPS
Time code of first frame : 07:30:28;13
Time code of last frame : 07:30:53;27
Time code settings : Source Package
Time code, stripped : Yes

Other #3
ID : 7
Format : Acquisition Metadata
Muxing mode : Ancillary data / RDD 18
Codec ID : 0D010301020E0000
Duration : 25 s 526 ms
Frame rate : 29.970 FPS
TransferCharacteristics_Fir : 0E06040101010601
ColorPrimaries_FirstFrame : BT.709
MatrixCoefficients_FirstFra : BT.709
IrisFNumber_FirstFrame : 3.399925
FocusPositionFromImagePlane : 15.000 m
AutoExposureMode_FirstFrame : Manual
AutoFocusSensingAreaSetting : Center Sensitive Auto
CaptureFrameRate_FirstFrame : 29.970 fps
ShutterSpeed_Time_FirstFram : 1/3000 s
CameraMasterGainAdjustment_ : 652.36 dB
ISOSensitivity_FirstFrame : 160
ElectricalExtenderMagnifica : 100%
AutoWhiteBalanceMode_FirstF : Automatic
ExposureIndexofPhotoMeter_F : 160

Other #4
Type : Time code
Format : SMPTE TC
Muxing mode : SDTI
Frame rate : 29.970 (30000/1001) FPS
Time code of first frame : 07:30:28;13

 




Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 06, 2024 Aug 06, 2024

Copy link to clipboard

Copied

Hi @Никита5E27 - 

Can you try holding down "SHIFT" while launching Premiere and check the boxes 

"Reset Plugin Cache" 

"Disable third-party plugins (one time only)" 

"Clear media cache files" 

 

I'm thinking you are hitting a media cache issue, please let us know if any of these help you,

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 06, 2024 Aug 06, 2024

Copy link to clipboard

Copied

There is some problem with the plugin cache, disabling them and reloading the cache helps premiere work, can you tell me how to determine which one is causing the crash?

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 06, 2024 Aug 06, 2024

Copy link to clipboard

Copied

UPD. If you disable plugins and their cache along with them, it crashes. It seems to help if you enable all three checkboxes - disabling plugins, their cache, and media file cache, then it seems to work. Then I don’t understand what is the reason for the program failure

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 06, 2024 Aug 06, 2024

Copy link to clipboard

Copied

Hi @Никита5E27 - It seems like one of your plugins needs to be updated as it is causing Premiere to crash.  You can either uninstall all of them until you figure out which one is causing the problems, or if you click the hamburger menu in the effects control panel you can select "manage video effects" and enable/disable each one.  Please let us know which plugin is causing the error.  Thank You!

Votes

Translate

Translate

Report

Report