Premiere 24.4.1 - Scrubbing and Playback Issues - Had to Roll Back to 24.3

[mustbebelize]

I've been using Premiere since version 1 over 25 years now.  There have been ups and downs and struggles, but in the last few years, it's been smooth sailing.  But this new update - version 24.4.1 is a nightmare.  I can't even scrub through my timeline.  Matter of fact, it won't even playback properly.  Anyway, after troubleshooting, I finally installed the older version 24.3 and I'm back editing .  What's up with that Adobe?  

Mod note: The title was changed to reflect your issue and for search purposes. Sorry for the frustration.

[R Neil Haugen]

That sort of behavior is most often entirely affected by "local" conditions ... your combination of factors: OS, CPU, RAM, GPU, vRAM, type and connections for used drives, media used, and effects.

As you  didn't give any details on any of that, "we" can't even speculate. Past suggesting something basic like holding a modifier key down while launching Premiere, and clearing all cache files of course. Or perhaps starting a new project, then from the MediaBrowser panel, importing the assets of a previous version project.

It seems most users are getting along fine.

[mustbebelize]

Thanks for a response.  I'm using custom built computer with a MSI Tomahawk motherboard with Intel(R) Core(TM) i9-14900K 3.20 GHz, 64 GB Ram and a Nvidia GeForce RTX 4070 on Windows 11 with all NVMe M2 drives.  One for Windows, one for media and one for cache. Never had an issue until the 24.4.1.  I tried clearing cache, uninstalling 24.4.1 and restarting Windows then reinstallling 24.4.1 - two times to be sure and still dead in the water.  So I rolled back to 24.3 and it worked.  So what suggestions may you have to successful update and use 24.4.1?

[R Neil Haugen]

And the involved media and any effects used?

Is the default audio input set to None (which cures an amazing array of things ...) ?

[mustbebelize]

The media assets are just mp4 files in H.264 format in high definition at about 50Mbps with 59.94 f/s shot on 2 Canon camcorders.  So it's 2 layers of video and audio and I use Lumetri color effects since it's dance recital footage and transitions and titles are from Premiere's effects palette.  Not a very complex setup.  

Setting the default audio input to None is a good tip.  I'll check that out.

Thanks again for your input.

[R Neil Haugen]

"just" high-def H.264 and 59.94fps ... um, that is not easy media for working in an NLE. 8K RED raw normally plays back easier. Just noting that.

Premiere gets more 'demanding' of hardware with each version, as is not unexpected. I work for/with/teach pro colorists,  mostly in Resolve, running massive machines. They dislike any clips in H.264. Period. Often transcode to something else before starting the conform process.

So it will be interesting if say your audio input was something else, and "none" fixes this.

[mustbebelize]

That's news to me that Premiere dislikes h.264.  That's the native format for many years in Sony and Canon camcorders that myself and probably hundreds of thousands if not millions of videographers use.  

At the very beginning one of the main goals of NLEs was the ability to mix and support different file formats.  And that's what determined much of the success of the NLE.  Adobe Premiere did that well for me many years.  And now you're saying they don't want to do that anymore?  Come on, I can't take you seriously anymore.  Don't take it personally and you don't need to answer this cause I won't engage.  I need an Adobe expert to answer my post.

[R Neil Haugen]

Weird take. I can't see that at all. I was talking of the trouble computers have with the load that long-GOP codecs present. Not Premiere specifically. Didn't you read the part about colorists in Resolve?

Apparently you have no training in long-GOP media, which the Sony and Canon rigs use at times. And you question my expertise? Just ... wow.

Neither Premiere nor Resolve can change the workload. As only a few frames outta the camera are complete "iframes", nearly every frame requires up to 30 or more other frames be decoded and stored to RAM/cache before it can be decoded.

You don't notice so much in straight video player playback. Bur an NLE or grading app is grabbing bits and pieces of many clips on the fly, stringing them together.

That first frame of a clip? The NLE has to find the iframe *before* that clip, decode it, then take the datasets of changed pixels for each frame after it, to create that first frame you see. With some drones, that can be up to 60 or more frames that aren't shown, just to be able to create the first shown frame.

Some hardware handles this better than others. Intel's KF CPUs don't have their QuickSync hardware inside and are horrid with long-GOP media. Most AMD CPUs have not had any internal hardware so all computation has to be the slower software only route.

[Loc N.]

This happened to me as well! All my projects are having CLEAR issues play back, even with PROXY! Everything was working perfectly as could be BEFORE the 24.4.1 Update!

[mustbebelize]

Good to know that I'm not the only one.  As a matter of fact, several other people have mentioned the issue with the 24.4.1 directly to me.  I am still waiting on Adobe to address the issue.  

[RODRIGO29736536fdtp]

Same here! All previous versions works fine. I had to go back to 24.3

[GreyTigerXX]

Same. I'm also expereincing issues with selecting tracks and copy and pasting clips. The program always pastes clipes on the same track regardless of which track is active. In fact, selecting track doesn't work properly either. 

[R Neil Haugen]

 That might be because they changed the behavior for track pasting a few builds back. It's caught a lot of people. So are you aware of that change? If not, that would be the reason for the track issues.

If you know about that, and are having troubles, not good is that ... channeling Yoda here ...

[kmalaise]

I can second the behaviour, it is very obvious the 24.4.1 version ( and the 24.5 version and the beta 25 version as well) have this issue.  We're running PP on more than 20 Macstudios UltraM2 and we did the upgrade to 24.5 (from 23.3) and were confronted with the terrible playback behaviour. We rolled them all back to 24.3 and that solved the issues. So Adobe please do some more testing and bugfixing before releasing updates. Companies who use your products are not supposed to do the testing for you.