Dynamic link "could not read from source" error

Community Beginner ,
Nov 20, 2020 Nov 20, 2020

Copy link to clipboard

Copied

I have seen a hundred posts about this issue dating back at least 6 years, and I haven't seen a consistant solution.  

 

I am running the latest AME (14.6) and AE (17.5.1), but every time I push a comp from AE to AME the dynamic link error comes up.

 

Since I pay over $600 a year for these programs, and I spend about 20% of every workday trying to fix or find a work around for some issue with these apps, can someone walk me through a solution to fix this error?  

 

My system is macOS Catalina 10.15.7, 4 GHz Quad Core Intel i7, 32gb RAM.

TOPICS
Dynamic link

Views

90

Likes

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
Advocate ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

LATEST

There's still several problems with dynamic link on Catalina, admittedly.

 

Do both apps have full permission in your system preferences? In Security & Privacy, you can grant the apps that you use permission to admin settings.

 

Also, are you using any third party plugins or effects in AE? For me, I found a comp that had Videocopilot a lens flare in it, which caused it to fail to connect to either Premiere or AME, even though the layer was turned off. 

 

A potential workaround that only worked for me on one of my projects (figured this out spening 20% of my work time, too) was to dynamic link the project to Premiere Pro instead of AME and export from there. Oddly enough, I found that I could even queue the project from Premiere Pro over to AME. Weird, I know.

Likes

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