Adobe Media Encoder error - the file could not be imported. Could not open source file.

[davidd42937246]

I'm using a TNT drive to encode locally saved videos and save them on an amazon s3 drive. 
Whenever I try to import mov files, I get this message which also says "please check that the file exists with correct permissions. 
I checked, and they do. I even renamed the mov to mp4 because I read somewhere that worked for someone else.

I reinstalled AME, and nothing is working. Please help

[labt13]

I have the same problem that just appeared this week. I had no problems last week importing the same file types. The error appears in both Premiere Pro and Media Encoder for four like files. Media Encoder supplies the most detailed error message. "mov file could not be imported. Could not open source file. Please check that the file exists with correct permissions."

[KAPUTZ]

Hello #Adobe, what do I do now?

[RoscoeSas]

I'm having the same problem.

[KAPUTZ]

Changing the file from .mov to .mp4 solved the issue for me. But not getting any answer from the company is scary - and unprofessional.

[angelad52501097]

Same!  .mov to .mp$ fixed it for me.

[angelad52501097]

* .mp4

[angelad52501097]

wait, i spoke too soon, it did not work.  I have audio, but no video.  still need answers.

[gregbowendesign]

This worked for me too. Thanks much, really needed this movie. It was a native screen capture too??

[kyle.jorve]

I have the same issue. I've looked around and I can't see that Adobe's acknowledged the problem or offered a solution.

[Justine5D56]

So, none of you have received an answer from Adobe? Here I am having the same problem, I tried using to Media Encoder to change to MP4 but it won't except the file either? Adobe are you going to follow up on this thread???

[jerryr16487096]

Likely being caused by one or two issues. 
First, temp files are probably being created on the tntdrive by Adobe.  Due to tntdrive using a background queue/cache, the deletion of the semaphore temp files may not be immediate.  Maybe change the cache options to resolve that.  

second possibility, S3 allows for case sensitive file and path names.  Therefore it is possible that path references may not find the files they need.  Try putting all of your files in lower case letters.  

[Lisa5CD0]

YAY! I HAVE THE ANSWER!!!!  So...I did a chat with an Adobe Cloud agent; I already had Handbrake installed so I was lucky otherwise I would have been apprehensive about this solution (I use Handbrake to fix synch problems with music videos).  If you're not familiar, Handbrake is a program I downloaded free from the internet. I HATE doing that but again, I *really* needed a free program to synch my music videos. I'm not made of $$$ haha...anyway, I simply dumped the video into Handbrake, clicked the Video tab, there was an option to change the frame rate to "constant frame rate." I did that, rendered it in Handbrake and, VOILA! It converted my clip into a VIABLE .mp4.  I AM SOOOOOO RELIEVED. I frequently do special effects and render first in iMovie, but it renders the clip into a .mov file.  Anyway, hopefully this will help some of you and this isn't too late for your projects - at least it will help you all (and hopefully others) with your projects going forward.  Good luck everyone! 

[Kerri5CD6]

Thank you SO much, this worked perfectly!!

[jaydude-wb]

Suffering from this for a year when rendering After Effects comps in AME. The problem is that the temp files that AME creates don't have the correct permissions. My solution is, when the Ae comps are in the AME queue, to go to the folder, change the permissions to Read & Write for everyone, and then start the encoding queue.

Quite a hazzle - hope this ever ends.

I am on MacOS Catalina.

[Phantom2024]

Try this:

https://www.autokroma.com/blog/BETA-For-Influx-Importer-Adobe-Premiere-Pro-After-Effects