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

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!

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.

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?

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've opened a CS6 project in Creative Suite and all is working fine apart from all the caption cards which can't recognise the font.

There are loads and I don't really want to have to go to each one to select a new font, so it would be good if when you get the 'Invalid Font Family' warning you get the option to choose the alternative. Courier is a much wider font than the one I had before, so now most of the captions run off the screen and I have no choice but to change each one manually.

You've had this problem for ages - why haven't you fixed it?

Current Behavior: Whenever you import a long R3D file Premiere automatically groups the smaller "spanned" clips into a larger clip. If you import the clip via the media browser it works fine because the media browser will hide all but the first clip in a sequence. But if you try to import multiple folders(multiple cards, or days of footage.) Premiere will still group the clips, but it creates a full length master clip for each of the parts the the file was split into causing tons of duplicate clips.

The only work around is to manually recreate your folder structure using bins in premiere and go through each card one by one importing them into bins, or go through and delete all the duplicate clips after importing the usual way.

Expected behavior: When you import a group of spanned R3D files premiere will group them into a single master clip and not create a duplicate master clip for each file in the sequence.

This is a huge waste of time for anyone working on a large project using Red cameras. This problem has existed since at least 2013 and seems like it should be a really easy fix that would save RED users so much time.

The problem we're running into was brought up by someone else in the forums back in 2017:

https://community.adobe.com/t5/Premiere-Pro/Why-is-Premiere-linking-the-wrong-clip/m-p/10646862#M229918

In our environment, we edit off of our server, and have done so for a long time now, without issue. All systems used to be Macs, but we've started introducing some PC systems into the mix, and now we're starting to run into complications.

This particular complication is around Premiere relinking to the incorrect media when switching between system OS.

1) Create a project in OS A (could be Mac or Windows), and then edit something.
2) Replace an asset in the timeline.
3) Save the project,
4) Open the same project on OS B (the opposite of whichever you chose in Step 1).
5) Marvel as your clip (replaced in Step 2) is linked to the old media.

This only seems to happen with media which have undergone the "Replace Footage" treatment, and this never used to happen when we were only using the one OS.

System Information:

All systems are running the latest Premiere release (13.1.5)

PC:
Windows 10 (1903)
Intel i9-9900X
64 GB RAM
Nvidia RTX 2070 (431.36)

Mac:
OS 10.14.6
iMac Retina 5k, 27-inch, late 2014
4 GHz i7
32 GB RAM
AMD Radeon R9 4GB