Copy link to clipboard
Copied
Hi, my problem was that Premiere Pro would crash when reading MXF-files. After a long search, I found a (painfully simple) workaround! I figured my case might help people who experience the same problem and maybe even help Adobe to fix this.
My case: I got a new pc with an NVIDIA graphics card and Windows 11 and Premiere Pro 2023 kept crashing when trying to open Premiere Pro 23.2-projects. As it turned out, whenever I started a project with MXF-video files, it couldn't load them (either blackscreen or media pending-screen in the program-window) and stopped responding after a few seconds. In a new project I couldn't import MXF-files (it just loaded endlessly without any progress, then crashed when trying to cancel) – I used the drag and drop-method directly from the Windows Explorer when trying to import. Here's the thing: When I deactivated the NVIDIA driver, those issues didn't occur! With files such as MP4, the issue didn't occur either, even with the NVIDIA driver activated. Funnily enough, with my old laptop with Windows 10, Premiere Pro 23.2 and the same files/projects, I never had this problem!
Workaround: I found this video and its proposed solution was so simple. Import your MXF files/projects with already imported MXF files not per drag and drop or via 'File' and 'Import', but find the files in the Media-Browser and then drag and drop them from there.
I hope this helps some of you 🙂
Here's a few specs:
Here's what I'd tried before finding the workaround:
Copy link to clipboard
Copied
Premiere Pro 23.2 seems to be crashing on loading a project with MXF files located in media bins as well, also on Windows 11 with nVidia drivers. This was fine in 23.0 and just started a week ago with the 23.2 update...
Process: Adobe Premiere Pro.exe [10072]
Path: C:\Program Files\Adobe\Adobe Premiere Pro 2023\Adobe Premiere Pro.exe
Product Version: 23.2.0.69
File Version: 23.2.0.69
Code Type: x64
Parent Process: explorer.exe [9620]
Date/Time: 2023-02-22 18:52:54 Pacific Standard Time
OS Version: 10.0.22621.1194
Report ID: 88b993e5-0673-4d8e-abf3-fbd975774e4e
Crashed thread: 42 [2348] THREAD_PRIORITY_NORMAL
Exception Code: 0xc0000374
Exception Parameters: 0x7ffba85d1860
Exception Message: 3221226356 A heap has been corrupted.
Application Specific Information:
C:\Windows\SYSTEM32\ntdll.dll
A brand new clean project and just dragging one in OR navigating to their location in the media browser will cause this crash.
If it helps here is the mediainfo dump of the MXF files
Format : MXF
Format version : Version 1.2
Format profile : OP-1a
Format settings : Closed / Complete
File size : 2.07 GiB
Duration : 39 s 289 ms
Overall bit rate : 452 Mb/s
Package name : Source Package
Encoded date : 2022-07-29 01:40:26.984
Writing application : Adobe Systems Incorporated Premiere Pro 1.0.0.0.1
Writing library : win32 4.5.13.0.3
Video
ID : 512
Format : VC-3
Format version : Version 1
Format profile : HD
Format level : HQ
Format settings, wrapping : Frame
Codec ID : 0D01030102110100-0401020271040000
Duration : 39 s 289 ms
Bit rate mode : Constant
Bit rate : 440 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 59.940 FPS
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 3.540
Stream size : 2.01 GiB (97%)
Audio
ID : 768
Format : PCM
Format settings : Little
Format settings, wrapping : Frame (BWF)
Codec ID : 0D01030102060100
Duration : 39 s 289 ms
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Frame rate : 59.940 (60000/1001) FPS (800.8 SPF)
Bit depth : 16 bits
Stream size : 7.19 MiB (0%)
Locked : Yes
Other #1
ID : 0-Material
Type : Time code
Format : MXF TC
Frame rate : 59.940 FPS
Time code of first frame : 00:00:00;00
Time code of last frame : 00:00:39;14
Time code settings : Material Package
Time code, stripped : Yes
Title : Timecode
Other #2
ID : 0-Source
Type : Time code
Format : MXF TC
Frame rate : 59.940 FPS
Time code of first frame : 00:00:00;00
Time code of last frame : 00:00:39;14
Time code settings : Source Package
Time code, stripped : Yes
Other #3
Type : Time code
Format : SMPTE TC
Muxing mode : SDTI
Frame rate : 59.940 FPS
Time code of first frame : 00:00:00;00
If there's any workarounds for this that'd be great. Will try and open a case with Adobe as well.
Copy link to clipboard
Copied
Hmm. So, this seems to be a problem with Windows 11 in combination with NVIDIA and Premiere Pro 23.2 (but I've seen similar posts with earlier versions as well). I also realised that unfortunately, when reopening the projects that worked before with the technique I mentioned, the crash happens again. To that, I don't have a solution. Anyways, thanks for your reply!
Copy link to clipboard
Copied
Hi, I have the nearly same problem with with windows 10.
Works perfect in Premiere 22
Copy link to clipboard
Copied
omg I was banging my head against the wall. This seems to work right now. I also rolled back my gpu drivers, uninstalled geforce experience and rolled back after effects as well. The ruumour going around is that you can't have geforce experience and premiere running together. It's March 17,2023.
Copy link to clipboard
Copied
Geforce Experience loads a bunch of things, including some audio "enhancement" items, that seem to cause issues for Pr. Best not to have it on the maching.
Neil
Copy link to clipboard
Copied
This is still an issue without a word from adobe. I'm having the same problem on a 4090.
Copy link to clipboard
Copied
To be more specific, the problem being:
I'm using a 4090 on Windows 11 pro. 13900k. Latest studio driver: 551.23
Copy link to clipboard
Copied
Anche io ho lo stesso problema, Premiere Pro non mi importa i file MXF.
Il mio sistema è:
Windows 11
Premiere Pro 23.2
Intel i9-13980hx
nVidia RTX 4090
64gb ram DDR5
Su After Effect tutto ok, Premiere invece va in crash.
Se avete soluzioni per favore.
Copy link to clipboard
Copied
Solution that worked for me: https://community.adobe.com/t5/premiere-pro-bugs/premiere-pro-build-85-cannot-run-mxf-raw-files/idc-...
Copy link to clipboard
Copied
The issue is still on-going... I have to say this is driving me nuts as I shoot mainly with Sony and MXF files, so I don't really want to convert all my MXF files to a MOV files or else... Not sure what they changed since 23.0 but this is really making it harder and harder for me to resist the urge to switch to Da Vinci... Seriously Adobe, with all the money you make from all creative around the world, you could at least make sure your software most basic function still work after adding all the fancy-shmancy AI components and whatnot.
It used to be simple to add MXF in Premiere Pro and edit. Not anymore... >_<
Nvidia 4090 / Win11 / Latest Nvidia Studio Driver
Copy link to clipboard
Copied
Here's two possible solutions:
To quote @Bacuba13 from another thread, who contaced the Adobe support:
«...the issue has been resolved by granting permissions to Adobe folders individually from file explorer during our call or you can go with the Run as Administrator option. All of my Adobe folders for some reason were "read only" or some permissions were not set to "allow".»
Or my workaround:
I found this video and its proposed solution was so simple. Import your MXF files/projects with already imported MXF files not per drag and drop or via 'File' and 'Import', but find the files in the Media-Browser and then drag and drop them from there.
Copy link to clipboard
Copied
Hi, take a look at the solution. Hope it works!
Copy link to clipboard
Copied
@Nomadidje take a look at the solution. Hope it works!
Copy link to clipboard
Copied
Thanks but of course I did try that solution before ranting on the forum hahaha.
I have to say the 24.3 stable version is out and it seems to have fixed my issue as I can relink my MXF files or import them with no issues....just like before !
So back to work, even more now that I've wasted a few days trying to convert my MXF to a MOV, downgrading back to Premiere v23+ and reimporting my sequence via xml I exported out of Premiere v24+, downgrading my Nvidia driver, trying different combo of driver and Adobe versions, changing folder permission attributes, etc....
All that instead of editing videos, which is what I'm supposed to be doing ! ^^
Anyway, thanks for the feedback and sharing the issues, at least we got an update that seems to have fixed what was broken in the previous one.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now