Smart! I think thats the best play - anything you can do to avoid using ultra key in your timeline is going to give you much smoother playback. If you have access to Photoshop and are interested, the background removal tool is very good. You could automate some of your work by batch-removing backgrounds. Check out the thread here for more info on that. Or just stick with Canva if it works for you - looks like you can bulk-remove backgrounds there, too (which you may already be doing!). ... View more

Hi Evan, can you share what exact machine you have? Based off the specs you shared I'm thinking it is a laptop with integrated graphics (reported as "Intel Arc Graphics" by windows). This would mean you don't have a graphics card, so you aren't getting any of the performance boost by using the OpenCL. In particular, you say you are using Ultra Key a lot - this is a GPU-accelerated effect that really struggles if it only has a CPU to work with. If your prior machine had a discrete GPU, even if your processor was slower, it probably handled Premiere (and particularly the Ultra Key effect) much better.   To prove this point: if you take a normal h.264 clip (here's a link to a free download from Pexels if you don't have something handy) and drop it onto an otherwise empty timeline - do you get smooth playback? If yes, then the issue is likely related to your lack of GPU and usage of Ultra Key.   For a fix- it'll be a time-consuming process, but the only way I can think of for you to be able to edit comfortably would be to do all of your work without Ultra Key applied (or apply it and then disable the effect while you are editing) and then apply the key just before export. Alternatively: Import your PNG sequence to your project Drop the resulting clip into a timeline Apply your Ultra Key to the clip Export clip with either the "ProRes 4444 with Alpha" or "GoPro Cineform RGB 12-bit with Alpha" presets Reimport your keyed clip Repeat 1-5 for each clip Edit with your reimported ProRes or Cineform clips - these will have the the green keyed out so you'll have the transparency you need, but your computer shouldn't be experiencing the slowdown from having to apply the effect in realtime. Probably obvious, but the drawback to this method is that you can't adjust the key. You'd have to go back to your source clip, make the changes desired, re-export & replace.   Hope this helps! ... View more

@Carlos Ziade has correctly explained that a Proxy workflow is basically the only way you're going to get better performance with the machine you have. In addition to that, export your rotoscoped AE files to ProRes and import into your project, instead of using dynamic links. Linked files take much more computational power to play back. Realistically, you're going to have to do a lot of compromises like this to edit comfortably on a Macbook Air. If you do choose to upgrade (and are sticking with Mac) I would recommend looking at a Macbook Pro, Mac Studio, or Mac Mini. ... View more

To clarify - when you nest the sequence in your Vertical timeline, you are flattening it to those dimensions - that's why it is cropped. Peru Bob is correctly pointing out that you need to change the settings of your "cropped" nested sequence to match your original 4K sequence. ... View more

Old thread, but recently ran into a version of this kind of glitch and wanted to share a possible fix - Problem: Video file exports ok to ProRes, but exporting to h.264 (or transcoding from the good ProRes export to h.264) would result in video glitching similar to OP's image. Happened both directly out of Premiere and through Media Encoder.   Solution: Had to change from 2-pass to 1-pass encoding, and that fixed it. Alternative solution, if 2-pass encoding is a must, would be to use Handbrake (or your other transcoder of choice) to create an h.264 based off of a ProRes (or other all-i) export. ... View more

I'm not a big network guy but this is likely to be more of a network/config issue than a Premiere one. The only obvious/easy thing I can think of is to check that you have Jumbo Frames enabled (give this article a read for details on how to do that). I'll stress that that's "at your own risk".... if you're on a managed connection or have an IT person, would definitely recommend just working with them. Only other partial workaround - try exporting your footage to your local drive (I am assuming you are exporting right to the NAS). Then you can just copy those to your NAS as needed. ... View more

Hi, firstly would recommend closing Premiere and restarting your computer. Hopefully the project works again when you open it next.   Or it could be a workspace problem. Try Window > Workspaces > Reset to saved layout   One last thing that may work - in your project, create a new sequence with settings that match the one you are work in. Copy your entire timeline into that new sequence (in your current sequence: CMD+A then CMD+C, in your new sequence: CMD+V). Hopefully you are able to edit as usual in the new sequence. ... View more

Hi, regarding slowdown in other Adobe apps, it does sound like you are running out of memory. The reality is, 32GB of RAM just isn't what it used to be. Maybe it was an accidental omission, but if your machine does not have a graphics card (and is running integrated graphics off of a chip) it'll be harder for your machine to play back video.   All that said - I've seen that specific "skipping playhead" issue once or twice, and at least in those instances it was tied to an audio hardware problem. To fix, try going to Edit > Preferences > Audio Hardware, and changing your Default Input to No Input.   ... View more

Without knowing the computer & storage specs its hard to diagnose this - but as Ann mentioned, you've got a few factors working against you for sure. Anecdotally I've never had good luck with using HEVC on my timeline and will almost always opt to transcode to ProRes before editing. That'll solve the variable frame rate issue as well. (Proxies will give you a better experience on the timeline but won't impact final render time).   I can't tell for sure but it looks like you are adding captions over the video? The Essential Graphics tools can have a surprising impact on speed/performance. Maybe try exporting/rendering the video with that layer disabled to see if it speeds up significantly.   Also worth asking what your storage device is? If it is slow, that could be holding up your export. If you're unable to get a faster-writing storage device, I'd recommend outputting directly to your desktop and then copying over your export to whatever your external device is.   FYI, low bitrate does not necessarily mean a lower encoding time. The encoder can wind up working harder to crunch more information into a smaller file. ... View more

Hi @Jim1587 - so what is happening is your "living people" clip on track 1 is definitely at 100% opacity, but the background of the clean plate on track 2 is making that entire image appear to be 50% transparent.   Try changing the Blend Mode on your "ghost" layer (track 2) to Darken. EDIT: You could also keyframe the opacity to go from 0% to 50% if you want the ghost to fade in/out of reality 😉 ... View more

While this isn't a one-click option in Premiere, the following may be a good workaround for you. Step 1: For your video capture, before you record, set your camera to free-run, time-of-day timecode & sync it up with a clock (that is, if it is 10AM set your camera to 10:00:00:00, if it is 2PM - 14:00:00:00). That way, the timecode in your clips will accurately reflect when it was recorded in 24-hour time. Step 2: Import your footage into Premiere, and manually enter the date of recording into the "Description" field in your project bin. Step 3: Add an adjustment layer on top of your footage in the timeline. Apply the "Metadata & Timecode Burn-in" effect. Set "Line 1" to display Source Timecode. That is your accurate "24-hour" time. Set "Line 2" to display Description. This will display the date you have manually entered into the Description box in your bin. Make sure both lines have Source Track set to Top Clip (that is the default behavior).   Legally, I don't know if that is an acceptable solution, since it can absolutely be faked. If you need the metadata indellibly burned-in to the footage you will have to do so at the source -- most if not all cameras have an option to burn-in metadata (date & time) such that it cannot be removed. Good luck! ... View more

This is a bad answer but might function as a workaround for you before someone more knowledgeable answers - I had this problem today tracking simple movement in high-contrast areas (light boats moving on dark water). Some boats would be tracked without issue on the first click, others that looked identical in speed/color/contrast would hang indefinitely on Tracking - Progress... What worked for me: Cancel out if it hangs on "Progress" (if the bar begins to fill just wait - you should be in good shape) Adjust the mask slightly (reposition a node, or move the entire mask). Then reposition where you need it to be. Try tracking again Repeat until Premiere decides to track   Again, this is not a great answer - but it did work for me as a workaround. Here's hoping someone more knowledgeable has a better solution! ... View more

+1 to @Peru Bob's mention of Handbrake. I've worked on multiple projects in the past where people sent in iPhone footage of themselves as the source material, all VFR. Some of the clips worked without issue, other clips would have sync issues on the timeline, some only in export, and some would just crash the project on export. Not fun. We've made it standard now that all clips are batch transcoded through Handbrake to CFR before importing into a project. Based on the quality of our source material the 1080 Fast preset works for our delivery needs - but you may want to experiment with your quality settings if you are concerned about that. These are almost definitely overkill, but my recommendation for specs to preserve quality would be 1080 @ 15,000kbps, or 4K @45,000kbps. Last thought, its an old thread, but you may find this helpful: https://community.adobe.com/t5/premiere-pro-discussions/setting-constant-frame-rate-in-filmic-pro/td-p/8455600 ... View more

Thanks for this! Still working in 2024. For whatever reason, shortcuts don't work for this. I had to right click->copy, right click->paste. ... View more

Hi @Priyanka26494747o2te, you can move around the frame when zoomed in with the middle mouse button or the hand tool (hotkey h by default). Select the hand tool, then use the left mouse button to click and drag anywhere in the Program monitor and you'll be able to move around. You can do the same thing with any tool active by clicking and dragging with the middle mouse button, instead. ... View more

Bummer 😞 Last idea, could try duplicating your sequence, and in the copied version, change your sequence settings to 50fps then back to 25. I don't really have a good guess as to whats causing that behavior but maybe that would 'force' the time remap to understand your clips are 50fps and not 25. Hoping someone with more knowledge than me can help with a fix!   (Afterthought - this does sound like more of a bug, would back kglad's advice on posting to the Bug Report forum. Hopefully will get you quicker engagement from Adobe's team!) ... View more

The notification reminded me - back in 2018/2019 I had this issue on a Macbook Pro. Eventually Media Browser just... started working again? This is almost entirely unhelpful, but might point to there being a preference/cache issue that was incidentally resolved in a computer/Premiere update. If you wanted you could try backing up and resetting preferences. Then just roll back your original preferences if that doesn't fix the issue.   But I hear you, hopefully someone more knowledgable than I has the actual fix!   If you haven't already, may be worth doing a repost to the "proper" bug report section of the forum. Technically this is the "Discussions" section. ... View more

EDIT: Just want to put up top, definitely double check all of your sequence and clip framerates. I've been "certain" I had a project set up correctly in the past only to realize halfway through that I had a framerate mismatch, etc. Well, that at least narrows it down. Seems like Premiere is reading the footage as 25fps (Optical Flow is introducing the warping by generating frames). You could try offlining a clip (right click clip on timeline > make offline) and then reconnecting it (right click > link media). Maybe that'll be the same as sort of "re-adding" it to the sequence, which you've said appears to work.   If that doesn't work, a potential workaround could be copying, removing, then re-applying the speed ramp: Copy your clip to clipboard on the timeline (hit cmd/ctrl + c). Right click that same clip on the timeline > remove attributes, and make sure only Time Remapping is checked (as a heads up this will temporarily change your clip length on the timeline). Click OK. Right click your clip > Paste Attributes, make sure only Time Remapping is selected. Click OK. Clip should play back correctly. Definitely a bit tedious but at least you don't have to re-do the time remapping from scratch. ... View more

I think a good first step is to restart Premiere & your computer, assuming you haven't done so already. A few other ideas... Delete your render files (Sequence > Delete Render Files) and try rendering a section of your timeline. Better playback? Another thing to try - right click the clip and change your time interpolation to Optical Flow. See if that plays back more smoothly? I don't know what would have changed, but would be a good idea to confirm that Premiere is reading your 50fps footage as 50fps and not 25 for some reason (In project window, right click > Media File Properties) ... View more

Got it. A few other ideas: Make sure that you don't have filtering enabled - "All Supported Files" should be checked Try unchecking this box before you hit "Locate" so you can relink with Windows Explorer instead. More of a workaround than a fix, admittedly. ... View more

So did unchecking the "Display exact matches only" box help? Outside of that, try: restarting Premiere; restarting computer; disconnecting/reconnecting your storage device where the media is located.   Looks like you are on Windows (7? 10? 11?), but I've seen a few posts recommending: cancel out of the link media dialogue (i.e. open your project with media offline), then go to Window > Projects, and make sure the project you are working on is checked. Then try relinking media from your bin/timeline. I'm on Mac so I can't verify if that is a valid fix, sorry in advance if that doesn't help. ... View more

Sorry for asking the obvious, but are you 100% that the filename did not change in the handoff? Assuming the names match up, I don't know why Premiere isn't seeing it the file. But, if you're confident that you know exactly which file you need to relink - uncheck "Display exact matches only" near the search box, select your file, and relink. ... View more

@intuitive_Dreamer5E95 "Question : If I am doing interpret footage at 120 fps does that mean now all those 120 frames in the clip playing at 24 frames a sec will now be played back at 120 frames a sec ?  Will I undo what HFR mode did to my captured frames and the clip fps will be adjusted back to play at 120 fps ?" Yes. The clips will play back in "realtime" instead of slow motion.   "And does that mean what camera and adobe are basically doing is controlling the speed at which these 120 captured frames are shown at 24 frames a sec or 120 frames a sec ?" Also yes. ... View more

That clip you shared, C0066.mp4, was captured at 120fps but is being played back at 5x slow motion as a 23.976fps. That's what the "HFR record setting 24" in your camera settings refers to.    To explain a little differently - your camera captured 120 frames each second, but created a clip that is playing back 24 frames per second. So all the data is there, its just that the camera created a clip playing it back in slowmo instead of realtime.   If you would prefer it to be read as a 120fps clip: in your Premiere bin, right click (or ctrl+click) on the clip Modify -> Interpret Footage tick the "assume this frame rate" radio button, and enter 120   Based off of what you shared in your post "Sequence 03.mp4" my guess is that you added your 23.976fps clip to a 30fps timeline, and then slowed it down additionally. The ball being blurry is because your shutter speed was too low. I would say that this is more of a camera "problem" than a Premiere one. That said, I can't know for sure without seeing the source clip... but I stand by my guess! ... View more

@ThisGeneration.net Knowing that its an A/C unit is good info. In theory you should be able to reduce the sound with a notch filter (check out this tutorial, covers this and a variety of other techniques.) Additionally, you could either use a noise gate or manually adjust volume keyframes to further isolate the voices from background noise (i.e. volume up when character is speaking, back to zero when they aren't). Then stack these layers on top of your "background sound" layer (which maybe is something you've captured, or something you'll have to generate... or purchase). But in theory you'll wind up with 3 channels - (1) Voice 1, (2) Voice 2, (3) room noise. Hopefully will at least sound more natural than back-and-forth between room tones.   The only other thing I haven't seen mentioned, give the AI voice-enhancing tool a shot. Might wind up being too clean as its meant to replicate being right in front of a mic, but maybe at a low percentage it'll just help strip out the background noise. ... View more

@Peru Bob Appreciate you looking -- @PaulMurphy's video posted in this thread is a great solution for me. ... View more

Good find! Something to keep in mind should I need the effect on my end. Also, same here - I browsed around through Adobe's recommended third-party alternatives and couldn't seem to find a simple Radial Wipe equivalent. At minimum, their support document really should have hyperlinks that directly corrolate to a recommended replacement - or maybe some professionally-made, downloadable mogrt replacements.   On Mac, filepath to find the plugin is: Macintosh HD/Applications/Adobe Premiere Pro 2024 -> Right-click the "Adobe Premiere Pro 2024" app and select "Show Package Contents" ... then browse to Plugins/Common/AEFilterRadial_Wipe.bundle ... View more

@AndrewTheGreat - from that page specifically: "Projects that were made in previous version of Premiere Pro that contain obsolete effects can still be opened. The effects or transitions will still appear in your sequences and in the Effects Control panel on the clips they been applied. However, the Obsolete Effects folder, Obsolete Transitions folder and four Presets folders – Bevel Edges, Solarize, Convolution Kernel and Blurs (Windows Only) will not be accessible in the Project Panel. You can copy and paste your applied obsolete effects and transitions between clips and sequences in your project and continue working with them on new clips and in new sequences you create. Any custom presets you have created and saved in a previous version that contain any obsolete effects will remain." Not saying that this is a "good" solution - but based on this it looks like you should be able to copy over an older project that has the effect you've referenced, and then apply that effect to your new clip. Might even be possible to save a custom transition based on that so you just have easy access to it.   I am on a managed machine & haven't upgraded yet, so I can't test out on my end... though now that I think of it, let me know if you need that effect, I can send you a project file with a Radial Wipe applied to an adjustment layer. I'm getting off-topic, but I think a good compromise from Adobe could be to bury a "show obsolete effects & transitions" button somewhere in a Settings menu. That way it discourages new/current users from using problematic effects, but they can still be enabled if they are part of legacy workflows, or even with performance issues it really is the best solution. I don't think recommending users purchase third-party plugins (for features that are effectively being removed) is an acceptable solution. ... View more