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

I stopped editing for several months and recently came back to it. What I noticed is that Pr seems to have some issues importing the same types of footage that it previous had no issues with: 4K/60 h.264 files that are 5-6GB in size. Previously, Pr would just import them in with no issue. Now, Pr seems to lock up during the import, and again when I try to put that footage on the timeline for the first time.

During this "lock up", one CPU core from my 7900X is pushed right to 100%. The rest of them are at or near idle. It's a different core each time that goes to 100%, but it happens every time.

System:
Windows 10 Pro v.1903
Core i9 7900X OC'd (and water cooled)
2 x nVidia 2080Ti GPUs OC'd (and water cooled)
64GB DDR4 OC'd
SSD pairs in RAID0
HDD pairs in RAID0 (7200 RPM)
Scratch space on an M.2 drive

None of the resources are being taxed except that single CPU core. If there's any other info I can provide that might help get to the bottom of this, let me know!

This has not been fixed even though Adobe has claimed to fix this.

I have the media in one master project. My assistant has a their shared project. I open a small sequence from that project and drag the media from it it into my main project. EVEN THOUGH I ALREADY HAVE ALL THE MEDIA, I STILL GET DUPLICATED MEDIA. And on top of that it creates a separate folder for each small clip of footage. Take a look at the attached screenshot.

This is horrible. Fix this asap please. What's the point of shared projects if we can't move media back and forth between them?

I'm importing 14 different JPG images to Premiere to create an image sequence, but even when the images are all different, once I import them to Premiere, the preview and the export can't read the different images and shows all the images as if they were the same image than the first JPG.

I've been trying several different ways of doing this, and I already spent an hour of my life to make this work, and I still cant.

It should be the simplest thing to do, but it looks like it's too much for Premiere. Real shame, embarrassing to be honest.

You guys keep updating and updating, and every day we find more and more bugs on each program of the Adobe Suite.

A real shame.

Premiere appears to be misreading the BT.709 files that the 1D X Mark III produces for 4K video. The camera produces video with 4:2:2 chroma subsampling.

Premiere shows the properties of one these files as:

Type: MPEG Movie File Size: 2.40 GB Image Size: 3840 x 2160 Frame Rate: 29.97 Source Audio Format: 48000 Hz - Compressed - Stereo Project Audio Format: 48000 Hz - 32 bit floating point - Stereo Total Duration: 00;00;43;29 Pixel Aspect Ratio: 1.0 Alpha: None Video Codec Type: HEVC 10 bit 4:2:0 (Full Range)

Note that the chroma subsampling is listed as 4:2:0.

The camera produces 4:2:2 video for this case. I've checked with Canon Professional Services to make sure I had my camera settings correct.

There is a third party application, Media Info, that reads the metadata of a wide variety of video files. It shows that the file from the camera is using 4:2:2 chroma subsampling. Below is the output of that app.

Is Premiere getting the chroma subsampling wrong or is it actually changing it on import?

Thanks,
Dan

Here is the output of Media Info

General
Complete name : /Volumes/Projects1/covid data/testvideo/AU7I1575.MP4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/hvc1/CAEP)
File size : 4.77 GiB
Duration : 1mn 27s
Overall bit rate mode : Variable
Overall bit rate : 468 Mbps
Encoded date : UTC 2020-07-30 11:22:39
Tagged date : UTC 2020-07-30 11:22:39

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Format Range@L6.1@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 1mn 27s
Bit rate mode : Variable
Bit rate : 467 Mbps
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) fps
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Bits/(Pixel*Frame) : 1.880
Stream size : 4.77 GiB (100%)
Language : English
Encoded date : UTC 2020-07-30 11:22:39
Tagged date : UTC 2020-07-30 11:22:39
Color range : Full
Color primaries : BT.709
Matrix coefficients : BT.709
Codec configuration box : hvcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 1mn 27s
Bit rate mode : Constant
Bit rate : 256 Kbps
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 KHz
Frame rate : 46.875 fps (1024 SPF)
Compression mode : Lossy
Stream size : 2.65 MiB (0%)
Language : English
Encoded date : UTC 2020-07-30 11:22:39
Tagged date : UTC 2020-07-30 11:22:39

Other
ID : 3
Type : Time code
Format : QuickTime TC
Duration : 1mn 27s
Bit rate mode : Constant
Frame rate : 29.970 (30000/1001) fps
Time code of first frame : 00:23:19;17
Time code, striped : Yes
Language : English
Encoded date : UTC 2020-07-30 11:22:39
Tagged date : UTC 2020-07-30 11:22:39

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?