Skip to main content
Participating Frequently
June 22, 2023
Question

Importer Reported a Generic Error - Premiere Pro dynamic link to After Effects 2023 & 2024

  • June 22, 2023
  • 12 replies
  • 11684 views

I'm constantly having an issue within Premiere Pro and After Effects when I take a clip & 'replace with After Effects composition' in Premiere Pro.

 

The error gives me a, 'Importer Reported a Generic Error' on certain clips only, with the clip codecs being accepted with both Adobe Applications. Any solutions?

 

VIDEO LINK TO SEE ISSUE

 

Troubleshooting Steps:

-Cleared all media cache files for Premiere Pro & After Effects (issue still persists)

-Renamed clip files & changed clip locations (issue still persists)

-Ejected all external hard drives (issue still persists)

-Reinstalled Adobe Apps & CC Studio (issue still persists)

 

Info:

-Clip codecs are; Prores (.MOV) and .H264 (.MP4). Clips are not corrupted as this issue has happened to me numerous times randomly across 2023 and 2024 Adobe Versions.

-Clips located on native Mac Studio hard drive

 

Any suggestions would help, I've tried to get in touch with Adobe & their customer support failed to solve the problem & has wasted hours of my time screensharing. Note: This has happened numerous times over the past 2 years (2023 & 2024 CC versions) and it's about time to solve this frustrating problem.

12 replies

lehestro
Inspiring
May 9, 2025

I had this issue, but without any speedramps or any mp4 footage. My footage is .mxfs from a Sony FX3, which normally imports fine. 

I had some keyframed masks, but after reading this thread I deleted the masks and the dynamically linked AE project was created (which is odd, because I've created AE comps from premiere with masks before.  ¯\_(ツ)_/¯ )

 

However, I get this error where the footage appears as a black frame,. You can only see the footage when you scrub through the timeline. Also, the footage it is showing is not from this clip. 

 

laclaqueproduction
Participating Frequently
October 10, 2024

So, yes Update PR and AE just did the job !

laclaqueproduction
Participating Frequently
October 10, 2024

Hi everyone,

 

I just ran into this new issue, is there an easy solution to this problem ?

Kevin-Monahan
Community Manager
Community Manager
January 29, 2024

OMG, that's great info! Thanks for sharing.

 

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participating Frequently
January 29, 2024

Hey Kevin,

 

Thanks for that detailed insight. I believe I found the issue on my end (at least for what worked for me). When I speed ramp each clip, on some clips I receive that generic error (as stated in the original thread). Sometimes when I speed ramp the points conflict or seemingly overlap with eachother and gives a generic error when imported into after effects. I've proved this being the issue and solution on my end by moving each point of the speed ramp slightly away from each other, then when it imports succeccfully I double checked the points on the AE graph resulting with the points being one frame apart (rather than giving the error when they are overlapping).

Kevin-Monahan
Community Manager
Community Manager
January 29, 2024

Hi @defaultk901y1ok2uh8,

I got your message. A lot of issues like this are related to H.264 media, especially 4:2:2 10-bit footage or footage with a variable frame rate. Drone footage, mobile phone footage, and video captured on other consumer devices (action cameras, for example) are notorious for that kind of thing. 

 

The typical solution is to transcode or to create proxies on ingest. Editing with footage in a solid editing codec should help a lot. I use ProRes LT. You do need to have a good deal of storage while you are working with transcodes or proxies, but you can delete these files after you deliver/upload your finished project. 

 

If that is not working, try moving your files to a high speed media drive. That could make a difference too. 

 

I hope the advice helps. Let me know if you need help with the workflow. Good luck.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participating Frequently
February 18, 2025

I had this issue today fot the first time. AE and PP up to date v. 25.1, MacOS Sequoia 15.1.1
And what's funny - it also concerned the drone file, in that case, MOV file, 4;2;0 10-bit 25 fps.

What worked for me?
1. replace with AE comp not the drone file but whatever another one but from mirrorless camera, or gopro timelapse - than that worked
2. after saving an AE file linked to PP just click ctrl+z in premiere to undo linking unwanted clip

3. Choose to link with AE clip You want to replace

And that worked - no reason why 😉 

Participant
January 28, 2024

I have this issue as well, I compose a lot of real estate media. So lots of speed ramps drone footage etc. 
My workaround is to render out the project and create a new project from the render and cut the pieces i need to render after effects on. 

PITA Yes! 

Kevin-Monahan
Community Manager
Community Manager
December 22, 2023

Hi,

I'm wondering. Has this ever worked, or is this a new workflow? I informed the product team about this error. Can you share your project files with me? PM me if you, like. I hope I can help you find a reproducible case so we can have a good bug for the team to work on. Sorry for the problem. 

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participating Frequently
December 20, 2023

Still waiting for a solution.

Kevin-Monahan
Community Manager
Community Manager
December 7, 2023

Hi @Harel25647251oaoi,

I merged your bug with Nathan's. Seems to be the same issue. Let me know if it is not. Be sure to upvote.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio