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.

I have been dealing with this issue for a while, I have read every relevant topic on this forum to no avail.

Windows 10
32 GB ram i7 500GB SSD
GeForce RTX 2060

So this only happen occasionally, Id say 1 out of every 35 attempts of dragging clips to the media files in Premire, but sometimes if crashes when I only open up the file explorer, before I even try to drag a clip in. Usually the clips are MP4 since it sometimes happens when I just open file explorer it may not matter the type of file.

One thread seemed to suggest that changing the sequence codec to prores 422 instead of "ifram only MPEG" which appears to be my default for some reason. But this has not helped.

Anyway I have set me autosave to every minute so that has kept me from loosing too much time but I edit all day every day and It happes probably 4 or 5 times a day so I would love a fix.

When inserting two MP4 video files, there is a glitch.

If I drag two video files onto the timeline, no problem. Both the audio and video are imported, and the files are adjacent to each other on the timeline. If I import the second video by dragging it onto the timeline, with the first video already on the timeline, then ONLY the audio is imported.

I have reinstalled Premiere Pro and updated my video card driver as well.

A separate issue that -might- be somehow related is that the audio of an exported MP4 or MP3 file has a background buzz, which is even for parts of the video where there was no audio, so it's caused by the export (or before). I'm only mentioning that, because it seemed to start at the same time as the other problem.