I'll emphasize that the HE thing is in part my opinion and experience as a video editor and not necessarily something that will be shared by others. There are lots of people that I'm sure love and swear by Hardware Encoding and have never hit any issues. As someone who helps out a lot on various forums with support posts, I can tell you that using Software Encoding does tend to solve certain issues with exports, be it errors or glitches. I'm not quite tech savvy enough to be able to tell you if it's an Adobe implementation thing, but I suspect it's a bit more to do with how the hardware works. Even across other applications like in 3D packages, GPUs tend to be for speed and not necessarily quality. The CPU can output nicer images and calculate more advanced things, but at the expense of time.  ... View more

You could try a media cache clear just in case something got borked in there. Peru already mentioned the GPU driver. Personally I avoid Hardware Encoding when it comes to my final exports because historically it has been more error-prone, prone to render glitches - especially with more complex content and compositing in the timeline. Software Encoding is slower but more reliable, at least for me. But I hate QC'ing at the end of the project so I like to do the most stable and reliable possible export options, which is often to go to a ProRes master first, but at any rate, I save the Hardware Encoding for my review-quality versions. ... View more

When you're using Dynamic Link it's really going to depend on what the content is and how optimized that is over in After Effects. You're basically opening a background version of After Effects and are processing full frames of whatever is built over there, and that can be quite complex. You can have AE projects that take several minutes per frame to process. It could be using effects that are constrainted to the CPU or single-threaded, which could create a bit of a hardware bottleneck. But it's hard to be able to answer any more thoroughly than that without better understanding what this mogrt or dynamically linked comp is. They can be convenient, but aren't necessarily fast. Edit: You added the link to the mogrt in your other post. Thank you. Probably depends on which title you are using but some of those may be using methods that can be a bit slow to process. You can also try opening these MOGRTs up in After Effects and rendering directly out of there to see if it goes any better. ... View more

Hardware is only a small part of the equation. You can share the full specs of your system, Premiere version, but very importantly: what kind of media are you working with and what are you doing with it in the timeline?  ... View more

Can you try to render and replace the clip in the sequence?   A media cache clear might also be helpful.   Also trying a different video codec or export settings. Like exporting to ProRes first rather than H264. Or using Software Encoding with H264 instead of Hardware Encoding. ... View more

Glad it worked. It's a good little thing to know. I used to have some funky workflows to accomplish the same thing when this was probably under my nose the whole time. ... View more

I just wanted to chime in to support what Neil said. You have a nice hardware setup, but as soon as you see "iPhone/GoPro" footage as your source, you can't help but...   You hardware is only going to take you so far, and no amount of little setting tweaks here or there are going to make as significant of an impact to optimization as the media you work with.   Phone footage is probably the single worst thing you can put into editing software right now. HEVC is going to be the most difficult video codec to decode, mixed with Variable Framerate, which is like poison for editing software. That'll give you media pending issues, longer than usual encode times, frame sub errors and errors of all kinds during playback and export, render glitches, audio desync, etc. Like I said, poison. It won't always have problems, but it's just not a stable kind of media to work with. Variable framerate = variable results.     I don't know the specific specs of the GoPro footage you're working with, but it could be any combo of H264, H265, and sadly I think recent models are even capable of shooting VFR as well.     Point being: Hardware is only half the battle. Media makes a huge difference when it comes to performance and stability. With the right video codecs and workflow somebody with 1/10th the computer you have could probably match the performance and editing experience you get.     Another potentially flawed but hopefully effective analogy. You could buy a Ferrari, but then pour waterered down gas in the tank, and it's probably not going to run very well... It's not the Ferrari's fault. It's capable of great things. But the car - the hardware - is not the full picture of what it takes for it to run at its peak performance.   ... View more

Asking the obvious question here, but did you look for and reopen the sequence from the Project Panel? A Sequence is like a piece of media that lives in the Project Panel. It contains your edit and opens up in the Timeline Panel. You can close a sequence and reopen it again, you can remove the Timeline Panel entirely.. it doesn't mean the sequence is gone.   ... View more

Media from a phone is some of the most challenging and problematic footage you can possibly work with. It's going to be HEVC, which is the most processor-intensive video codec you'll find out there, as well as having Variable Framerate, which causes all kinds of issues in video editing software. You mention using a plugin of some kind so if you have intensive effects on top of the most difficult video codec, on top of variable framerate, you're basically setting yourself up for a rough time. ... View more

I just like to reduce reliance on the mouse as much as possible. There are some editing scenarios where I don't even have to take my hands off the keyboard. Aside from speed it reduces wrist strain for me. After twenty years of editing/working on the computer I'm a bit more sensitive to it. ... View more

I did see that Ann's suggestion does work in that specific context: Pin to Clip unchecked, and if you are hovering over the scroll bar. So that is something I didn't know, but I'm still just in the habit of using +/- for everything. It's well-ingrained muscle memory, and I tend not to work with Pin to Clip unchecked outside of specific instances. That's just me, though. We all get used to doing things certain ways. ... View more

I don't believe ALT + Scrollwheel works in Effect Controls, no. Feature Requests have been moved to these forums, you can find more info here: https://community.adobe.com/t5/premiere-pro-discussions/faq-how-do-i-file-a-bug-report-or-write-a-feature-request/td-p/13362039   Personally, I'm in the habit of using the +/- keys to zoom in/out on the Timeline, and those also work in Effect Controls. And I definitely don't use the scroll bars. I've probably spent less than 60 seconds using a scroll bar in my 10+ years of using Premiere. ... View more

You can try looking in the Nvidia Control Panel, also I would look at the video in this post: https://community.adobe.com/t5/video-hardware-discussions/premiere-pro-using-integrated-and-not-dedicated-graphics-card/td-p/9522241   Do you know what GPU driver you are running? Updating might also be something you need to do. Studio Drivers are what you should use for creative applications. ... View more

Do you have a GPU turned on as the renderer for Premiere? That would be in File > Project Settings > General, under the Renderer section. The GPU handles real-time scaling in Premiere. It doesn't come through super clearly in your photo, but it looks like the render line at the top of the timeline is red, which would also be an indication that you are set to Software Only as your renderer.  Without an active GPU as the renderer you would have to actually render the sequence to see the results of the animation that you've done. ... View more

Does Premiere let you set CUDA as the renderer in Project Settings? You can disable this warning banner in preferences as there's nothing you can do about the iGPU, but you can still continue working with your dedicated GPU if that is working. ... View more

You can look at the clip properties to see if there's a color space difference between the clip and the sequence. And in the Project Panel you can select the clip, right click, choose Modify > Interpret Footage, and see if there is a LUT applied there (otherwise a LUT would be applied via Lumetri Color as an effect on the clip.)    Some other things to investigate: Disable Hardware Accelerated Encoding/Decoding in Preferences > Media (and restart Premiere) Turn off the GPU as the renderer for the software to see if that helps (File > Project Settings) If either of the above help then it may be GPU driver related. You could try updating or changing your GPU drivers. You can try clearing the media cache You could attempt to address the problem clip(s) by transcoding them outside of Premiere with something like Shutter Encoder. ... View more

FYI Handbrake will only output Long-GOP codecs. An alternative would be Shutter Encoder, which is also an FFMPEG GUI but lets you transcode to a multitude of other formats, so you could correct VFR and reencode to an intermediate codec at the same time. ... View more

Can confirm on my side. Never worked with DJI footage in my entire career that didn't have some kind of issue, and it has only gotten worse since they've moved into using HEVC. Not uncommon to see these posts regarding issues with the exported video. It's pretty much always worth transcoding ahead of using that stuff. ... View more

It may have been your computer choking on the HEVC/VFR. Just beware when working with your proxy that it may not line up with your original footage, especially on longer clips (because of the VFR on the original clip) ... View more

Phone footage is some of the most challenging and problematic to work with. That's due to the combo of HEVC and Variable Framerate.   HEVC is the most complex video codec you can be working with right now. It's really great at using temporal compression to get things into a small file size and maintain quality, but the advanced algorithms used to do that are exactly what makes it incredibly difficult to decode (play). Your computer is doing complex processing to figure out what each frame of HEVC looks like since each image has to built from a large group of the surrounding frames.    Combine that with Variable Framerate (VFR), which is like poison for editing software. Editing software like Premiere likes a constant framerate since it's using timecode to precisely keep track of where every frame and every edit decision you make lives. When the framerate is constantly fluctuating up and down throughout your clip it causes all kinds of issues from long load times and media pending issues, longer than usual encoding times, audio will slowly drift out of sync, frame substition errors, and just a host of other errors and unpredictable behavior.     The combination of those two things make for just about the worst editing experience you can have right now. Transcoding those clips ahead of editing to correct the VFR and get it into a more manageable video codec can completely change your editing experience. If it were just a bad editing codec like H264 (AVC) or H265 (HEVC) then I'd say to make proxies, but you can't make proxies out of clips with VFR because the proxies won't line up.     In general, the majority of issues people have with performance, playback, etc., all come down to the media you use, not as much your hardware or editing software, so the more you learn about that technical side of things the more you'll understand about why certain things happen the way they do and how you can resolve those issues and have a smooth and stable editing experience.   Some resources: Information on video codecs in general: https://blog.frame.io/2017/02/15/choose-the-right-codec/  Information about VFR: https://www.reddit.com/r/VideoEditing/wiki/faq/vfr/   Also worth trying would be clearing the media cache: https://helpx.adobe.com/premiere-pro/kb/clear-cache.html   And another couple of things that can help or can be related to those audio playback issues: - Making sure you have enough I/O bandwidth on your storage, ports, etc. so that you aren't saturating the speed with data. Since you're working with very compressed source media it's unlikely that this is the issue, but it can result in similar behavior. - Moving your audio cache to a faster drive like an SSD or NVME ... View more

The way they handle color spaces has certainly changed/improved over time, but that doesn't necessarily mean you can't achieve the same or similar results. But I don't know what kind of situation we're talking about here and how nuanced it is. If it's the fact that you are recording HDR content and now Premiere actually recognizes and treats it like HDR rather than automatically adjusting the color space to Rec709, then that's just something to quickly learn, rather than go back to an older version. And it also seems like going back to an old version would eventually be unteneable, since they fall out of support. ... View more

Probably not. There are other ways to move timelines/clips between versions and software, though, such as an XML. Have you tried to figure out what is going on with your color in the new version? What is going on with the color? What kind of media are you using?  ... View more

Seems like there are a lot of very different issues described in that User Voice post. But just to get some other background info here: where is this media from? Codec and specs?  Anything happen if you select the clip and go to the Clip menu and choose Generate Waveform. Also, have you cleared media cache?  ... View more

Throwing out an alternative to setting the duration (which is totally great) just to have another helpful trick in your bag: If you select an edit point and press `E` that will 'Extend Edit to Playhead.' So in this context you could select the edit point of your AL/Transparent Video, press End to jump to the end of the timeline, or go to the timecode of your choice, and then press E. Works with other edit types as well like ripple and roll.  ... View more

What are we looking for in this? It doesn't look obviously distorted to me. ... View more

Your graphics card (GPU) has drivers - the software required to run the GPU. You update these drivers through the GPU manufacturer, so if you have an Nvidia GPU, you would go to Nvidia.com to get the drivers (or use their windows app - geforce experience). Macs typically get their drivers via the OS updates since all of those are integrated.     Phone footage is also something to be wary of since it will be Variable Framerate and typically a challenging video codec as well. It's some of the most unpredictable, most problematic media you can work with. ... View more

Just for clarity since the OP mentioned changing the renderer. The hardware accelerated encoding/decoding option is not the same thing as that. That feature was relatively new, affects playback of unoptimized editing codecs like H264/5 only, and when it comes to VFR media it can cause more harm than good. Again - not suggesting turning the GPU off as the renderer for the software, just the GPU acceleration for H264/5 feature. ... View more