Adobe Premiere Match Frame

[Mohammed Huberty]

Ive been searching for days and I've found no answer. On Avid, you can do a match frame from your sequence in the record monitor to another sequence in the source monitor, as long as this one has the same frame. It dosn't have to be the original clip. On premiere, the only match frame you can do is with the original clip, which will automatically appear in the source monitor. Even if you put a sequence into the source monitor, premiere will just ignore it and give you the original clip.

I found this pretty curious, since it can actually do the opposite ! Here's what I mean : if you try a reversed match frame from whatever sequence in the source monitor, it will not work (the sequence in the record monitor stays as it is). BUT if you do a reversed match frame with the exact same sequence as the one in the record monitor (you then have the same sequence in the source monitor AND in the record monitor), then it works ! It gives you the same frame you have on the source monitor !

For those who would be interested, I precise that if what you wanted was to make an IN / OUT selection after the match frame + reverse match frame to then insert or overwrite from one sequence to another, it is indeed impossible with the classic IN / OUT method. BUT you can still use the clipboard by making a IN / OUT selection, lift or extract it (+ ctrl Z if you want to keep it) and then switch to the other sequence and then ctrl V to overwrite OR shift ctrl V to insert.

I'm currently editing a feature documentary in Premiere Pro CC 2019. About a week ago, when I would match frame back to original footage, Premiere Pro would start to lag (Not Responding, according to Task Manager) for a good minute or more before correctly matching back to the footage. Sometimes it would not match back and I'd have to End Task. Occasionally, I'll get the same issue when loading the footage from the project bin into the source viewer as well, so not match framing isn't an option. Obviously this is seriously cramping my workflow and I can't get much done.

This problem occurs with a wide array of footage, meaning, it doesn't just do it when loading one type of footage, or one piece of footage. Sometimes it will lag with clip X, sometimes clip Y, sometimes clip Z. (And yes, the next time clip X, Y, and Z load fine.) This problem occurs whether I'm on a Mac or a PC.

I've tried all the usual troubleshooting techniques - deleting media cache, moving some of the footage to a local drive and seeing if the problem still occurs (it does), turning my settings way down, trashing my preferences, closing Lumetri panel and audio mixing panels, restarting, rebuilding the project from scratch (I started a new project, re-ingested all the media, and then brought in only the relevant timelines from the previous project), deleting all the lumetri effects, starting a new project file and importing the old project file, and calling adobe support.

The last item was probably the least helpful, as they basically did everything I had already done and then told me they couldn't help me unless I moved all my footage to a local drive. (Not really possible - we're a feature doc with about 15 TB of footage at the moment.)

All media is stored on a QNAP TVS-1282T3, to which I'm connected via 10GbE (PC) or Thunderbolt 2 to 3 adapter (Mac). Generally holds connection speeds between 600MB/s and 1.1GB/s as tested by transfers as well as Blackmagic Disk Speed Test. Firmware is up to date and works with other projects just fine.

PC is pretty beefy- dual Xeon E5-2690 on an Asus Z9PE-D8 WS motherboard with 128 GB RAM and an NVidia GTX 1080. Generally cuts and grades 4K material in high res without dropping frames off the QNAP without any difficulty. I have a blackmagic decklink SDI 4K outputting to a 4K monitor, but problem exists whether using this or not.

All the techniques you listed are troubleshooting directly relating to Premiere, but it sounds more like a video card issue to me. Have you updated your Nvidia driver? Make sure you check for any new drivers on Nvidia's website, and not through Windows Update or whatever built-in utility Windows has nowadays. Hopefully this helps?

Okay, cool. It's quite interesting that the issue doesn't come up with an older version of the project. Is there anything significantly different between the projects in terms of what you have imported into the project?

Here's a fuller update, which may help shine some light on the issue. The director of the project works remotely with an exact duplicate of the media. We share project files back and forth and since all media is mirrored and shares the same folder structure, we've generally had no problem. I keep the master of the project and import sequences from her project when necessary.

I found a fix for this. I experienced the same problem today. This occurred on a project I have been working on for a few months without any issues, and then today very time I hit "F" to do a match frame, Spinning Beachball of death. I also am working from a QNAP NAS. I'm using 5K Red footage. I trashed prefs and also uninstalled and re-installed Premiere. This did not fix the issue.

What fixed the problem for me (temporarily, see below) was re-naming the folder my original footage exists in. Upon launching Premiere, I was prompted with locating all the files. Pain in the butt, but it worked. I also got it to work by right-clicking the footage in the project window and select Replace Footage. Then navigate to your original footage location and select the exact same file on the NAS. I did not rename the file or folder. Hope this solution works for you too.

We were able to completely solve the issue by deleting all Lumetri effects and all essential sound effects. This, of course, is not an ideal solution. We lost days of color and sound work, but ultimately better than not being able to edit.

So match frame works in CS6, but in Premiere Pro CC, there are a couple odd things happening for me. When pressing F the Source panel will exibits any one of a few different behaviors (seems entirely random):

3. Occassionally the correct (matched) frame (usually only the first time I use Match Frame on any given clip in my sequence). All subsequent Match Frame commands while on the same clip in the sequence will not update to match Source with Program, they'll either stay on the first matched frame for that clip, or go black.

You can still drag the audio (or video) portion from the Source panel to the timeline and it will be the correct portion of audio (or video), but actually "matching" a frame seems broken in Premiere Pro CC (again, it works in CS6).

Hey all just wanted to say that apparently you need to select the track that the clip is on you are trying to match frame and then place the CTI over the clip you want to do it to. Doesnt seem to matter which clip is selected or not, all seems to depend solely on which track is selected (The top most track takes priority if multiple tracks are selected)

Right. That much is understood. However, what I'm experiencing is different. I've determined it is only happening to some clips. Others work as intended (as you've described). I wish I had time to get sidetracked today and post a video of what's happening. It'll have to wait until I'm wrapped up with my current multi-cam project (due last week).

Interestingly, the clips that have the problem are the SAME clips that do not have the problem (once on the timeline, is there a way to tell which is a subclip, merged clip, etc? Probably. No time to investigate. I shouldn't even be spending time writing this post. lol.)

Play around with different clips and subclips of the same clip on the timeline. I believe what I have going is several subclips of the same clip on the timeline. Unless I missed one or two, I've set them all up with "soft" handles (new feature in CC).

Perhaps what is happening in the "black" Match Frame clip is that the Match Frame is saying, "OK, we have a subclip on the timeline that starts at 0 seconds and 14 frames. So then when I do the match frame (of this "soft" subclip) the software is saying, let's find this clip and jump to 00:00:00:14 of the master clip and place it in the Source monitor.

Premiere Pro CC. No recent updates to install, unfortunately. Windows 7 Professional. 64-bit. Source footage: .MOV from Canon EOS-7D. No error message. The program acts as if it has done the right thing (but it hasn't). I'm not running any other software, but I have a few other things installed: Microsoft Office, RedGiant PluralEyes 3.0, Camtasia 8.0, Snagit 9 and a few other minor utilities such as Beyond Compare 3 and AusLogistics Defrag, etc. I'm careful not to install much, if anything, that I don't need for editing. Most of my codecs come as part of Premiere. I have Flash installed for Chrome (and maybe for Internet Explorer). I have Firefox, but I don't have Flash installed for that. I also have installed Quicktime Pro 7.7.3 (1680.64). I don't run Java on this machine at all.

Hello, I am using version 14.9 of premiere and I'm having match frame issues. Some clips on my timeline do not want to match frame. Sometimes the clips match frame on other desktops but sometimes they done. Please help

currently there's no match frame capabilites with any merged clips. match frame works fine with original clips. Also, I'm at a loss as to how I can reveal the actual timecode of these merged clips. I thought I could just reveal the timecode number and match back to that but I'm a bit lost as to how to find the real timecode of the video portion of the merged clip.

i'd go back to cs6 but it appears that cc7 has made working with the sony raw files much more stable. the problem working in cs6 is that sony raw 4k files cause premiere to be unstable and crash the program quite often. I'm hoping that a patch will be released soon.

It sure seems as though the merging process is breaking the match frame option. When I try to match frame it goes to a random frame in the source clip. and if I try again it'll change to another random frame.

3a8082e126