Inspiring

Answered

AE to Media Encoder "Could not read from source. Please check the settings and try again."

Forum|Forum|5 years ago
May 18, 2020
8 replies
21040 views

I just installed a fresh version of Catalina on my machine as well as CC. Everything is the latest version at this date.

AE will not export to AME via Composition dropdown. It will open AME but no item adds to the que.

If I add the item to AE render que and then like que in AME it will put the sequence in AME. When I attempt to change any settings or render, I get the error "Could not read from source. Please check the settings and try again"

My best guess is that Catalinas new security features are preventing the apps from talking, but I don't know how to resolve the issue.

Correct answer ZJ1902

I have resolved the issue by doing another reformat. Seems like its a Catalina Gatekeeper issue.

S

SASORI

Participant

I have same issues...

And the resolve is quiete odd. 😐😐

The original file address is in folder with the name "RX-78", Everytime I try to render or ingest proxy from Premiere pro error message "Could not read from source. Please check the settings and try again" always pop up.

Then I rename the original folder, from "RX-78" to "RX 78", and error message never pop up again...

ericdl

Participant

Had this issue today when exporting from AE to AME. The encoding gnomes became angry and threw an error when the save file contained the hyphenated string "pre-comp", yet they were perfectly happy when it was renamed to "pre comp".

S

sajads19481100

Participant

I encountered the same issue while I am saving the AE file in my Onedrive. I saved the same AE file in my local machine folder and tried again, it resolved the issue for me.

R

RepDaniel

Participant

Having this exact same issue. Fresh install of ME and AE on a new MacBook. Not quite sure what reformatting means...

A

Alexandra2451908007c1

Participant

Have the same issue, can't export GIF file from after effects. What is reformat? What can help with this issue?

rayk76223196

Inspiring

Well, after hours of pulling my hair out over this non logical issue (as the source file was there), I decided to disable AVG (Virus protection). Media Encoder never had a problem after that! I don't understand why, perhaps it thinks Adobe products are viruses? Who knows...

Give it a try and see how you get on!

J

Jayel5D09

Participant

How did you disable AVG?

N

nikoskorexenidis

Participant

change the file directory where the AVCHD files reside and check if the issue gets resolved. For example, if the folder structure is:

AVCHD>BDMV>STREAM>.MTS0000

Create another folder, XYZ, and move the contents of the AVCHD folder to XYZ folder.

P

precise_Butterfly5C08

Participant

How do you do another reformat?

B

Bhavya5CFC

Participant

did you find out?

J

Jaysus917

Participant

still having this issue with character animator and exporting to media encoder in 2022!! I'm sorry but adobe this is a big issue and unacceptable.