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

ISSUE

Video Sequences imported from a linked AAF do not play back on Apple Silicon Macs. However, the same imported sequence/project plays back fine on Intel based Macs.

STEPS TO REPRODUCE:

1. Export an AAF from Avid Media Composer (or DaVinci Resolve...the issue occurs with AAFs exported from both apps), using linked media, not embedded

2. Import the AAF into Premiere Pro (22.4) on an Apple Silicon Mac (launching Premiere in Rosetta 2 mode)

3. Park the playhead anywhere in the imported sequence. The frame under the playhead does not appear in the Program Monitor until after an inordinate amount of time (usually 15 seconds on my 2021 Macbook Pro MAX)

4. Open the source clip in the Source monitor, and try to scrub or park the playhead on the clip. The same behavior occurs, where it takes 15+ seconds for the frame to be displayed

TROUBLESHOOTING NOTES:

1. Re-importing the source clip into the project––directly from the Finder––yields normal playback/scrubbing performance, even when edited into the same AAF imported sequence.

2. The same behavior occurs, regardless of if Premiere is running in Rosetta 2 emulation mode or not

3. The issue occurs with AAFs created with either Avid Media Composer or DaVinci Resolve

4. Taking the same .prproj file containing the AAF imported sequence, and opening it on an Intel Mac, results in normal, expected timeline playback/scrubbing performance

5. Initially importing the Avid AAF into a prproj file on an Intel Mac, then opening that same project on an Apple Silicon Mac does not resolve the issue.

6. The issue occurs when testing with multiple different clips from different sources.

7. The issue occurs even on the simplest, cuts only test sequences (e.g. no effects, no speed changes, not resizing etc)

8. Attempting to work around the issue on the Apple Silicon machine, by reimporting the source clip into the project, then doing Replace Edits on each timeline clip, does not work. The replace edit links to the entirely wrong timecode when doing this.

9. Deleting Media Caches does not solve the issue

10. We reproduced the behavior on different M1 Macs in two physically separate locations (so the issue is not related to shared storage)

11. XML imports of the same sequence (exported from DaVinci Resolve) work fine on the Apple Silicon machines

VIDEO SCREENCAST DETAILING THE ISSUE:

https://youtu.be/bCohCE5YfZM

I noticed this while working on a travel video and using phone footage. My computer was just not having it, while footage from my DSLR played back fine. then I noticed the same on my workcomputer when trying to edit drone footage. This hasn't been an issue before so I think it has to do something with the latest update. I cant only slighty play footage back when I don't use the proxy and put playback resolution on full, which doesnt fully help but at least makes it able to slightly go over my footage. I used all the different proxies available but nothing works

Hi!
I've heard I am not the only one to have this issue. Preview window in Premiere Pro 22.0 is terribly tearing. Like some kind of V-sync bug. It's not there on ver. 15.1.0. Though it's still has bugs.
I have read everything. I turned on/off/what ever else V-sync in my Nvidia control panel for Premiere. Turned on/off GPU for previews in proj settings. Forced the system to use different video adapters for Premiere. Nothing. Tearing. Even on pre-rendered clips. Even without any effects applied. On Full resolution, "High quality" preview settings. No matter if it's Low-res HD footage or heavy 4K vids.
If I open the same preview file from Adobe previews folder it runs OK. Exported video is OK. But it terrible to work. I can't say, if footage is OK, until I export it. And I normally add some glitches to my video transitions. How do I know, is it my glitch or a bug?
Definitely needs to be fixed. Check out attached file for an example please.

BR, Anton.
Gigabyte Aero 2021, 11th gen i7, 64 Gb RAM, RTX 3060. Latest drivers. Nvidia Studio driver.

My PC:

AMD Ryzen 9 5950X

NVIDIA GeForce RTX 3080

64gb Ram

Premiere:

V22.2.0 Build 128

First edit job working with footage shot on my FX6 and Ninja V recording ProRes RAW,

Have downloaded PC ProRes plugin etc.

Footage edits and grades like butter. No problem with fx. Looks lovely. Until...

I did full 'in to out' render for best possible playback for director, noticed a few playback glitches, then to my horror exported to H264 mp4 and different flavours of Quicktime ProRes and found these to be even worse. Same out of Media Encoder, Example attached, best illustrated from 20s.

This is a mixed media edit (some footage from drone BMPCC and GH5) only the ProRes stuff is glitchy.

Workaround is to stick a filter over the whole edit (using adjustment layer) to force render. This is works via Media Encoder but only half the time (often aborts), doesn't work in app.

Tested on my ancient MacBook Pro and works fine (of course) but is slow.

Have fiddled with moving media to different drives etc, no joy.

Have updated all drivers etc.

Deleted media cache.

Deleted render files.

Copied in to new projects/sequences/ etc.

Spent hours with Adobe support.

Have reinstalled Premiere etc.

My guess is it's some Ryzen / GTX3080 unique issue with ProRes RAW in Premiere,

I'm having the same issue as this person references in the link below with V. 22.3 when syncing a separate audio file to a video file. I did not use any markers and the program would bring up the spinning wheel and crash when I tried playing it back in the timeline. I thought it was a codec issue and exported the clip in ProRes but it didn't solve the problem. The only way I could play back the video was to unlink the attached audio and cut the audio file and video file separately and line them up manually.

https://community.adobe.com/t5/premiere-pro-discussions/22-3-freezing-trigger-identified-markers-left-on-clips-before-merging/td-p/12894176