Autel Evo2 Pro video (4k 30p H.264) imported in 14.9 fine. In 15.2 I receive "File Import Failure" Unsupported compression type. I completely cleared my cache to try to fix it. No luck
MediaInfo details:
General
Complete name : V:\28182 Las Brisas Del Mar\MAX_0170.MP4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 575 MiB
Duration : 46 s 34 ms
Overall bit rate mode : Variable
Overall bit rate : 105 Mb/s
Writing application : Lavf58.20.100

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 1 frame
Format settings, GOP : M=1, N=15
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 46 s 34 ms
Bit rate : 105 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 30.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.421
Stream size : 575 MiB (100%)
Title : Autel.Video
Color range : Full
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC

When importing AVCHD files from different recording sessions but part of a same project when .MTS files are dragged into a timeline and multiple timelines from different recording sessions are open at the same time...audio playback from other .MTS files in other timelines occur. This most likely happens because every .MTS is labelled with a generic number 00001.MTS. It could possibly be that Adobe Premiere has the ability to catalogue and continuously keep things organized...but when it sees multiple files with the same numbering system it's not hard to imagine it getting confused even thought the clips are in separate BINS and were imported at different times. Maybe a solution is to have a date and time put before the generic number so each .MTS file is unique by filename and this will never happen. I have been lucky enough to save the project and reopen and the timeline plays back properly...but the unpredictable nature of the .MTS file naming problem is unnerving...especially when you have invested a week editing. The main problem is the way MAC OSX sees the AVCHD as a package that you can't "expand" to see the contents. Otherwise renaming and reconnecting files might be a "FIX" but the import process needs to be improved because of the way MAC OSX sees these files when imported. Premiere needs to make unique names when imported.

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.

For years, I've had issues with the sequence timecode matching up with the burn-in timecode of my videos. It's gotten worse in version 14.8 and 14.9.

When I would load in a H.264 mp4 or mov files and create a new sequence from clip, the sequence timecode would always be 1 frame off. I have been transcoding it to ProRes 422 (in Premiere) and creating a new sequence from that clip --and then timecodes would match.

But in 14.8 and 14.9, it's much worse and the timecodes are way off. I have gone back and forth with 14.7 and can confirm this.

After messing around, I noticed that when I go to Interpret Footage, it shows my video being 29.9701 instead of 29.97. If I modify it to assume frame rate 29.97, then the timecodes will match. Even so, it seems like a bug that's been around for a long time, but worse in 14.8 and 14.9.

This baffled me for years. There is only one option in the Import Options dialogue - a box to tick Image Sequence on or off. Why in the world is it hidden?! One option is literally not taking any extra space from the import window, and it's ridiculous that I have to constantly first click another button to open the ONLY option in order to click it On or Off. Very time consuming and annoying when importing multiple different items. Can you please please make it always visible? In fact instead of the "Options" button there should just be this one simple tick box...

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

Media Browser is awful - to the point that I spent $300 on Davinci Resolve JUST to get a working media browser. I capture clips at 400Mbps which results in very large files. When editing I only want to capture the good takes from SD to my storage drive. So I need to view them. But Media Browser refreshes every second, which means I lose my place and have to scroll down over and over and over. At some point Media Browser will refresh before I get back to where I was. Also, the clip preview performance is very sluggish. So I bought Resolve - which for me is essentially a $300 media browser that only refreshes the folder I'm viewing when I tell it to, plays clips smoothly, and shows them in a window that's large enough to evaluate the video.