Participant

Answered

Could not open source file. Please check that file exists with correct permissions

Forum|Forum|6 years ago
March 22, 2020
7 replies
20120 views

Hi, I keep getting this when I try to create new encode presets. I ran disk utility and all seemed ok.

Any ideas???

Many Thanks!

Drew

Error or problem

This topic has been closed for replies.

Correct answer Joseph Woods

I ran into the same problem and found a way around it.. try opening the file in quictime, then go to file>export, select the size you want, and make sure "Greater Compatibility (H.264) is checked. Huge pain, but it worked for me.. hope this helps.

L

LetsEditThis

Participating Frequently

This seemed to be some sort of permissions issue for me. But one that I couldn't resolve locally. I uploaded the video to Vimeo and let it convert it. Then grabbed the highest resolution I could. Original format was a .MOV and while I've had success int he past just changing the file extension, that didn't work here. Working on a PC.

M

Mazarate

Participant

I am trying to upload a .avi video to media encoder to convert into .mp4 but I am receiving the same error. Tried importing from desktop, then from external drive and nothing. I cant even export with quicktime because it does not support avi's. Need help. 😞

Sofa Digital

Participant

As a last resort, you can always play the video and record the screen using Quicktime in conjunction with the software Blackhole 16ch (it used to be SoundFlower a few years ago) to reroute the system audio to a virtual channel. So you can select it on the Quicktime audio recording input. Then you can play the video, record it and edit using any NLE. However, before that I would try using VLC Player to convert the file. It can read pretty much any codec out there and stream the contents to a new file.

teddy61174

Participant

I found that if you transfer the file to an external hard drive and open it from there, it works.

Joseph WoodsCorrect answer

Participant

I ran into the same problem and found a way around it.. try opening the file in quictime, then go to file>export, select the size you want, and make sure "Greater Compatibility (H.264) is checked. Huge pain, but it worked for me.. hope this helps.

S

Swj

Participant

I had the same issue, and this also worked for me.

J

Jaydude-wb

Inspiring

I am still suffering from this. Have to change permissions for each asset used. Never had that before. Think it's due to MacOS and Ae/AME not communication correctly.

I gave both Apps full disk acces in Preferences/Security/Privacy, but that does not solve the permission hazzle.

K

KAPUTZ

Participating Frequently

Where are the amazing engineers when we need them? I am paying for this *&%ˆ$ I need the job done.

Joost van der Hoeven

Community Expert

This is user to user forum where we users help each other. The Adobe engeneers do not always read everything here. If you feel strongly about a (new)feature or (bug) fix please post it here, as it will be read by the engeneers:
https://adobe-video.uservoice.com/forums/911308-media-encoder

Brandon Loshe

Legend

Hi drewd9949700,

Are you an admin with full permissions on your computer? Are you working off an external hard drive or NAS system?

What kind of source file are you trying to bring into Media Encoder? Is it some kind of video file (details would be helpful)? Is this a Premiere Pro project? Is this an After Effects project? Is this a Premiere Pro project with After Effects dynamically linked that you are trying to render in Media Encoder?

Any additional details would be helpful.

E

ericvisser9898

Participant

I've been running into this problem as well with Adobe Media Encoder. I've been trying to create proxy presets for Adobe Premiere Pro CC 2020. I've only been successful with H.264 but anything involving Quicktime as been a no go. I've tried Cineform and ProRes 422 Proxy with no success. This error pops up instead. I've personally thought it has to do with the fact that I'm editing using a PC instead of a Mac but correct me if I'm wrong.

estebanb19248148

Participant

Im actually experiencing the same problem and I'm seeing multiple other people struggle with it as well. I contacted them and they told me it was unstable frame. I thought this worked as it did with the test we tried. However, after trying to do it with my main project, I was back at square one.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.