I've recently been encountering strange issues when Importing .MOV files into Premiere 2019 or 2020, where I'd get a "File Import Failure: We were unable to open the file on disk" error. The error also occurs in After Effects, with the same files.

The files import or open without issues in every other video application I tried (DaVinci Resolve, Quicktime Player, Screen (Videovillage.co), VLC, IINA, Telestream Switch Pro & FCP-X).

After a bit of sleuthing, I figured out that the problem only occurs with .MOV files that were specifically transcoded out of Apple Compressor 4.4.8 (which is the latest version for macOS Mojave, as of 2020-10-17), AND also contains audio tracks.

MOV files that were encoded as "Video Only" out of Compressor 4.4.8 did not exhibit the import issue. Nor did the same file transcoded out of Compressor 4.3.2 (last High Sierra compatible version) with audio tracks enabled.

.MOV files transcoded out of other apps (such as EditReady) did not have any issues importing.

Changing the video/audio codecs or encoding parameters used to transcode them did not have any effect on resolving the issue.

Files that were transcoded to non-MOV containers out of Compressor 4.4.8 (e.g. .MXF & .M4V) all import fine, regardless of the presence of audio tracks in the transcode.

Deleting the physical audio tracks from the suspect .MOV files (using Digital Rebellion's "QT Edit" tool) did enable them to be imported without error. But obviously, this isn't a particularly ideal workaround if your camera footage has sync'ed audio in it.

So there seems to be some sort of bug that is causing File Import failures with .MOV files that were specifically encoded with Compressor 4.4.8 .mov files, AND also contains audio tracks in them.

I was first inclined to submit this issue to Apple as a bug, but the fact that no other application on my Mac (macOS 10.14.6, with latest Apple "Pro Video Codecs" package installed) seems to have problems importing the same files makes me think it's an Adobe specific bug.

Here are my test files, if anyone wants to help investigate:

Master ProRes .mov file (this is the source master file I used for my testing): https://d.pr/v/k6DYrJ

Test Transcodes: https://d.pr/f/MGIgWv

The Test transcodes in the .zip file contain the transcodes of the Master ProRes file, in various formats, from Compressor 4.3.2, Compressor 4.4.8 and EditReady 2.6.5. All the Compressor 4.3.2 & EditReady encodes import into Premiere/AE without issue. The only encodes in the Compressor 4.4.8 folder that import fine are the .MXF and .M4V files, as well as the .MOV file which was encoded with the "Format" option set to "Video" instead of "Video and Audio"

My current workaround is to "rewrap" (NOT re-transcode) the offending files to new .MOV files, using EditReady. This appears to strip out whatever internal inconsistencies existed in the original transcode, and allows them to be imported into Premiere again.

Here's a link to an EditReady-rewrapped version of the "compressor4.4.8-Apple ProRes 422 LT.mov" file. This imports into Premiere without issues, and is not re-transcoded, either.

https://d.pr/v/I0DiZg

Premiere Pro v14.8 on WIndows 10 - Canon XF utility installed on PC

My Canon Camera transfers footage onto my computer. With a specific File Structure. This is the structure for my Camera Canon XA50
../CONTENTS/CLIPS001/Filename.MXF
../CONTENTS/CLIPS001/Filename.THM
../CONTENTS/CLIPS001/Filename.XML

I believe Other Canon Cameras like the C200 have maybe a couple of other files for each video file. On top of the MXF, THM and XML files.

So, When I use the media browser ti import

Each file comes into Premiere Pro and Gets named CLIPS001 for every single file I import. All called CLIPS001.

Ok now if I rename the FIle structure to read CONTENT rather the CONTENTS so:
../CONTENT/CLIPS001/Filename.MXF
../CONTENT/CLIPS001/Filename.THM
../CONTENT/CLIPS001/Filename.XML

When I do this the files all get imported with the actual Filename as expected

I found that out on this user forum - https://community.adobe.com/t5/premiere-pro/canon-mxf-files-being-renamed-on-import/td-p/10864114?page=1
- See down the bottom, reply from user SR833

That user reports you can call that folder anything as long as it doesn't have an S in it basically.

Can we have this fixed please? It's super annoying. And if I rename the folder it no longer works with the CANON XF Utility.

Note this happens whether I import from the File-Import menu or through the Media Browser.

I also note that the creation dated for these files do not get imported either. I'm not sure if it's related or whether I should submit a separate bug report for that. But can you look at the filenames issue for this report. And check the creation date.

The MTS format seems to be a problem for Adobe Premiere Pro. Sync, choke and import problems. Lots of posts report these problems, but one by one they get little attention.
There are lots of professional equipment that record and use this format, still these problems have been following Premiere for years. Some has been solved, but some has also returned in newer updates.What about doing what any other video application handles without so much fuzz. Fix MTS import and make it easy for editors. No more transcoding to get those files into Premiere....that is not an ideal solution. That's a time consuming workaround. Something you might expect in a freeware product. Not a #1 professional editing suite.

Thanks

In almost every large documentary project I work on with huge amounts of different media there is always some bad media that causes massive playback issues, which is really frustrating when I need to work quickly.

While I like the fact you don't have to transcode everything to a native format like in Avid, therefore avoiding big and expensive workflows, I do think Premiere should assess all media upon import and tell you if it wont be able to play it back well, and if it can't then it should ask you if you'd like to transcode this media to a more premiere friendly format using Encoder, eg Pro Res.

Something like this would help all projects run smoother, without constant lagging and playback issues. Im on an iMac with 32gb RAM, 8gb graphics, 4.2 GHz Intel Core i7 - this should be plenty to run Premiere!

I have been using Premiere pro from last 5 years now.
Sorry to say but it doesn't feels anymore worth it as it takes ages to load thumbnails in the Project bin.
I have a good fast IMAC machine with 32 GB ram on it.

I have exchanged chats with the support team but till date there has been no solution to it. Tried everything from Clearing Media Cache to Changing Rendering Engines to resetting the software to reinstalling the same.

A lot of my fellow editor have switched to FCP due to the same issue and i might soon if this exists.

IT IS LIKE KILLING TIME WHICH HAS NO OUTPUT AT ALL.

Solution is simple.
1.As soon as we import the files they should have the thumbnail previews opened.
2. Thumbnails should load in the Background and not only when you scroll through them.
3. Each time you open the same project thumbnails should reload again.

PLEASE WORK ON THIS! PLEASE!
Feels like this post will too go in vain looking at others which are years old and still not taken up by Adobe!

WAKE UP ADOBE!

I have a Canon EOS R5 which can shoot video in HEVC or RAW 10-bit 422 format. Premiere can load all its files fine, but when I examine their properties inside Premiere Pro the HEVC and ALL-I HEVC files show as 10 bit 420 files. Not 10 bit 422. The RAW Files don't actually show the color depth or chroma information. All the files seem to load and edit fine, but it seems to be misinterpreting the 10 bit 422 HEVC files as 420.
Is this a bug, does it affect my color grading, or is this some intentional conversion that Adobe is doing with these files internally?

If you change the frame rate of a video files after you create the proxy the edit is different in the timeline with the proxy and the original media.
More your in point is far more the clip in the timeline change between orignal & Proxy files. I think the change for the frame rate is not apply to proxy files. I found the pb with the latest CC2020 in juin 2020. It is very easy to reproduce the pb. Chose an 24P original media, create proxy, change the frame rate to 25P ad the clip in a new 25P with an in&out point. Change the viewer between Proxy/original the first and last picture change for every clip in the timeline with the same edited Framerate and change all your timeline coherence.