Lagging/choppy backward playback

Hey there, @Imgorthand,

You wrote:

The edited material consists of Canon R5 files in 4K ALL-I format, which, as I understand, shouldn't be a challenge for this setup.

Noted. Strange also that it worked well in a previous version.

What are the details of this media file? Is the 4K footage variant H.264/HEVC 10-bit 4:2:2 footage? You can verify this with MediaInfo in Tree View. If you can provide a screenshot, that may shed some light on the issue.

Feel free to provide a sample clip that I can forward to the team. To keep it confidential, upload to DropBox or the like and PM me the URL.

I'm also a little curious about your Windows 10 build. Research says that Windows 10.0.26100, also known as Build 26100, is actually a Windows 11 build that was released to testers in the Windows Insider Canary and Dev Channels on April 3, 2024. It is part of the development cycle for Windows 11 version 24H2. Is it possible to update Windows to see if that might help your problem?

Thanks,
Kevin

Works like charm in 23.0.0

Broken in  in 23.6.9

Broken in  in 23.3

Broken in  in 23.1

Confirmed again that works like charm in 23.0.0

So the problem is here: 23.0.0 --> 23.1

I cant narrow it down any further (no 23.0.x versions available in CC), but I'm willing to verify the beta version again when you have a fix.

I noted that backward playback in 23.0.0 is constant CPU 100% and 5-10 GPU - despite that is works smoothly.

In the broken versions (23.1+)  the CPU stays 100% even for 10 seconds after stopping backward playback and GPU works only for a moment and then stays 0% during choppy backward playback.

For my work I'm switching to stable version 23.0.0.

Sumeet Kumar Choubey, There are no effects in the clip as my report is for Source view.

Kevin-Monahan,

I imported ProRes clip to my project and it plays smoothly both ways (CPU GPU usage is 20/10 avg both ways)

So indeed this issue is related with decoding Canon R5 ALL-I MP4 files. But please keep in mind this format is designed for easy editing and each frame is separately compressed. 

The cpu usage is only minimally higher when playing forward 30%vs 20% for ProRes.

There should be no reason for such a drastic difference back/forward.

The backward playback of those files must have worked well for most of last 2-3 years - or I woulnd not have grown accustomed to playing back often to find the ideal moment for marking.

I noticed the problems few months ago but I had a weaker rig then - and it was choppy for many reasons. On the new rig the problem is very transparent.

I might be persuaded to try to find the last working version 🙂

I tried the SHIFT reset and it did not help. 

And this is happening regardless of resolution - also at 1/16

😞

Does this still happen if you lower the resolution to half?

Can you try backing up your preferences and then hold down "SHIFT" while launching Premiere and check the boxes 

"Reset app preferences"

"Reset Plugin Cache" 

"Disable third-party plugins (one time only)" 

"Clear media cache files" 

I had several windows open, including Effect Controls, Lumetri Color, Project, Program, and Timeline - but closing them didn’t resolve the issue.

The playback remains choppy when running backward. After that, forward playback is also choppy, which significantly affects my workflow.

Set the workspace to essentials (and closing most windows) also did not help.

Additional sbservations:

For forward playback, CPU spikes to 100% briefly, then stabilizes around 30%, while GPU usage is between 5-20%.

For backward playback, CPU usage stays at 100% during choppy playback and for 10 seconds afterward, with GPU usage at 0%.

Sometimes, after forward playback, I can run backward smoothly for 1-2 seconds before it becomes choppy again.

Do you have any panels open? can you try closing panels like the effects panel.  Can you try changing your workspace.

I had "System Default - No Input" but changing directly to "No input" doesnt change the problematic behaviour.

Can you make sure that in your preferences under audio hardware your default input is set to "No Input"