Skip to main content
Participant
April 17, 2024
Question

Errors when importing MXF files and exporting PNGs in AE v24.3

  • April 17, 2024
  • 4 replies
  • 968 views

Myself and several coworkers have started to get import/export errors with the latest version of After Effects (version 24.3). We have found that reverting back to version 24.0.3 completely resolved 100% of our issues. Here are some of the specific issues we've seen so far:

  • Exporting PNGs when the color space is set to Rec.709
    • This results in the classic "AEGP Plugin PNGIO library error." I'll attach screenshots of the errors to this post.
  • Importing MXF video files
    • The error message reads, "...cannot be opened, it may be in an unsupported format."

 

Does anybody know a quick fix for these issues, or do we need to wait for Adobe to release a patch? Transcoding our MXF files to another format is NOT an option. Our editor has done some tests with different formats and has requested that we keep the MXF files as-is if possible for the sake of keeping the color the same across all of our shots. The same goes for the PNG exports. Sometimes we need to export PNGs in Rec.709. We do it all the time. It's always strange when this error pops back up. Thanks in advance to anybody who takes the time to stop by and respond!

This topic has been closed for replies.

4 replies

Joost van der Hoeven
Community Expert
Community Expert
June 12, 2024

The MXF eror I've seen too. Often is was because a file was zipped/moved via collect files or similar . Try two things:
1. Copy the file to you desktop, and rename by adding "copy" or similar to the name.

2. Clear your cache as Ae/Pr then recreates the database and that might be the cause.

nishu_kush
Community Manager
Community Manager
June 12, 2024

You can upload the files to cloud storage and share the download link with us. If you don't want to share the files publicly, feel free to DM me or Paul.

I'll move your post to the Discussions board while we await your information.

 

Thanks,

Nishu

breecedkAuthor
Participant
April 18, 2024

Thank you for the quick response!

  • The MXF files are fairly big (400MB-7GB) so I'm not sure of the best way to share one of those with you.
  • As for the PNG issue, I managed to strip a project down to almost nothing and it still has the issue I mentioned above (unable to export PNGs with my usual render preset.) I would drop that here, but the forum won't let me upload an aep or zip. It says "(.aep) is not supported" and "(.zip) is not supported."
  • I also have system info on two of our computers that experienced the issue. I would upload those full .txt files but apparently txt files aren't supported either...Here's some of the more important information for those two computers:

 

COMPUTER 1 (031):

Item Value
OS Name Microsoft Windows 11 Pro
Version 10.0.22631 Build 22631
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name MFX031
System Manufacturer ASUS
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor 12th Gen Intel(R) Core(TM) i7-12700K, 3600 Mhz, 12 Core(s), 20 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1720, 8/12/2022
SMBIOS Version 3.4
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product PRIME Z690-A
BaseBoard Version Rev 1.xx
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.22621.2506"
User Name MFX031\animator
Time Zone Mountain Daylight Time
Installed Physical Memory (RAM) 128 GB
Total Physical Memory 128 GB
Available Physical Memory 39.4 GB
Total Virtual Memory 166 GB
Available Virtual Memory 46.5 GB
Page File Space 38.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

 

COMPUTER 2 (018):

Item Value
OS Name Microsoft Windows 10 Pro for Workstations
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-QT76QHP
System Manufacturer BOXX Technologies
System Model APEXX T4L_01
System Type x64-based PC
System SKU SKU
Processor AMD Ryzen Threadripper PRO 3955WX 16-Cores, 3900 Mhz, 16 Core(s), 32 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 0504, 6/2/2021
SMBIOS Version 3.3
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product Pro WS WRX80E-SAGE SE WIFI
BaseBoard Version Rev 1.xx
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\windows
System Directory C:\windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.3636"
User Name DESKTOP-QT76QHP\Breece
Time Zone Mountain Daylight Time
Installed Physical Memory (RAM) 128 GB
Total Physical Memory 128 GB
Available Physical Memory 34.5 GB
Total Virtual Memory 153 GB
Available Virtual Memory 40.3 GB
Page File Space 25.1 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Community Manager
April 17, 2024

Greeeings and thanks for reporting this issue.

I just did a quick test in 24.3 of dropping a .JPEG file into a Comp, Project Working Space set to Rec.709 (in Project Settings: Color), and this rendered to a PNG sequence without error.

To get further with this, I think we need more information:
1. System details.
2. Samples of the MXF source footage that will no longer import.
3. A sample project and footage, configured in the fashion that when you attempt to render, you're getting the various PINGIO errors.

Thx!