When you are "seeking," (which means QUICKLY looking through a long video by clicking and dragging the playhead with the cursor,) there is sometimes very high "prefetch latency," meaning that frames will load slowly, resulting in very few frames being shown. This can make it very difficult to find what you're looking for.

But when seeking, perfect frame accuracy is not nearly as important as seeing what you're doing. Therefore, to reduce the "prefetch latency," I suggest that the nearest I-frame is loaded and displayed FIRST, (because I-frames are always the fastest to load) while the exact B or P frame is still being slowly decoded. As soon as it's decoded, it can be displayed, replacing the displayed I-frame.

If the user is seeking quickly, there might not be enough time to load the P and B frames before the user has already moved the playhead nearer to another I-frame. This is fine! The I-frames should always take priority.

In VLC, there is a similar feature called "fast seek."

Combined with my "ghost playhead" feature suggestion, it would be made clear to the user exactly what is going on. (Linked below)

However, it would probably be important for fast seeking to be optional, and perhaps even off by default, as it may confuse some users.

NOTE: This works best if only ONE video source is visible. With more than one video on the timeline, the I-frames will probably not be in the same spots. Nevertheless, it COULD still work, but there would have to be multiple ghost playheads. This might be too difficult to code, and confusing and frustrating for users, who won't understand why premiere is showing video frames out of lockstep, especially in cases where one video has high prefetch latency, and the other is low.

LINK TO FULL EXPLANATORY VIDEO: https://youtu.be/XeFezzmG22c

LINK TO GHOST PLAYHEAD USERVOICE ENTRY: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/42186274-a-ghost-playhead-which-always-marks-the-timeline

It's happening more often than usual. To reproduce the error you must be working for a couple of hours within a file (large or small it doesn't matter). After a while it will freeze the entire software (including the mouse cursor) if you just hit playback - EVEN if you already pre-rendered that part (green bar is up).

Never had this problem before this update 14.6.0.

Also, Premiere just freezes when you hit playback, so if you manage to stop the playback you will be able to save your work and exit the program (which will not solve the issue). A temporary solution that I found is to restart the system, after that you can open your file normally until it bugs out again after a couple of hours.

To me it looks like a huge memory leak might be happening.
My specs are:
CPU: Intel® Core i9 9900KF
Motherboard: Intel Z390 High End
RAM: 32GB DDR4 2400Mhz
SSD M.2 480GB
GeForce RTX 2060 6GB GDDR6 192-Bit

Any ideas on how to solve this?

Rendered playback set to FULL resolution does not always actually playback at FULL. Often drops to 1/2 or less frame rate and stutters.

Need to stop and restart playback numerous times for the software to actually engage full resolution playback.

Timeline is set to ProRes422 1920x1080.

Happens with both single GPU and with eGPU.

iMac19,1 with Vega48 with 128GB RAM, 3.6GHz 8-Core Intel i9.
macOS Catalina 10.15.7 (19H2).
RX5700XT is the eGPU when in use.

This is NOT a drive speed issue. All drives connected are SSDs with minimum 450MB/s speeds. Scratch drive is NVMe with 2000MB/s. System drive is Apple SSD with 2500MB/s. No errors reported with DriveDx at all.

Include DVD (And all possible media) burning capability within the app. The fact that I had to purchase the entire Creative Cloud to be able to render a video and now that I need to copy video content to a DVD player to share with nursing homes and can NOT DO IT WITH ADOBE PRODUCTS is frustrating. Give us the ability to do one stop production. And recognize that the WORLD is not yet streaming and downloading all their content because they either do not have reliable internet or they do not have the technological capability/aptitude/money/time or will to try to access everything from a cloud.

When using LUTs in Lumetri, playback performance becomes really poor - like, stuck at 10-12fps consistently. Overall responsiveness drops as well. This is especially true with "heavier" LUTs and when using them in an adjustment layer.

Any version of Pr Pro 2020 beyond 14.3.1 exhibits this issue, so it's been around for a while. I was bummed to find that the issue is still present in 14.5 because the GPU accelerated decoding for H.264/265 media is an excellent addition.

Anyone know if Adobe is looking into this bug?

General notes:

I've noticed this problem on multiple systems (specs below)

It happens on all types of video sizes and codecs I've tested (H.264,
HEVC, ProRes, 4K footage, 1080p footage, etc.)

Smaller file size LUTs seem to create less of an issue than larger ones but still noticeably reduce playback performance

I believe adjustment layers create even more of an impact hit

System Specs:

System 1
Windows 10 (May 2020 update)
i7-7820X
64GB DDR4 2666MHz RAM
GTX 1070 (have used multiple drivers to test but currently on latest studio driver)
All drives are either NVMe SSDs or SATA SSDs

System 2
Windows 10 (May 2020 update)
i9-9900K
64GB DDR4 2666MHz RAM
GTX 1070
1TB NVMe SSD

Problem: Currently playback lags significantly whenever an JPG image at its full resolution (6000x4000) is added to the timeline despite selecting 1/4 or 1/8 playback quality or changing playback settings. Playback stops completely when motion effects are applied (like scale/position changes).
Problem occurs even on a computer that handles 100mbit 4K videos at Full playback resolution without problems.

Expectation: Since an image is just 1 frame, it actually should be easier for computer to handle it and I would expect a smooth playback. It would be fine to also see it at reduced quality, because currently, reducing playback quality does not affect image playback quality.

Solution: Since I understand that actually a conversion process is happening for each frame from e.g. 6K to 4K/FullHD (whatever the timeline settings are) - this conversion should happen either on import or you could allow to do proxies like with 6K video footage, but not on playback.

Reason for importing full 6000x4000px images instead downsized is because photographers often need to show the 100% resolution. Thanks!

It's just happening to this project so far but it's very frustrating. I make a cut and everything ahead of the cut loses audio. I can undo the cut and audio is back (but then I can't edit forward without matching frame, dragging clip into new sequence and continuing that was which is annoying). I spent a long time trying a dozen things with the adobe chat customer service thing and nothing worked. Interestingly, I can export the section that's lost audio and the export has audio, so I guess it's a playback issue or something. I've attached screenshots just to give you an idea. I'm using most updated version of premiere. My comp is iMac (27-inch, Late 2012), Mojave 10.14.6, 3.4 GHz Intel Core i7, 32 GB 1600 MHz DDR3...please help!