Glitchy scrubbing on interpreted footage in source window...

guys, never update unless you know that you're OS and hardware will work properly in the new OS.  If you're on the mac, you can create a bootable clone of your startup drive using something like carboncopycloner and quickly restore your system to it's usable state so you might want to take the chance and adobe allows you to install an update without deleting earlier versions.  On my 2012 macbookpro, I've got premiere 2017, 2018, 2019 and 2020 but adobe no longer allows downloading of 2017 and 2018.  I only keep them on my system because I provide support for a few clients who are "change averse" and refuse to update.  I know you all want the latest bells and whistles, but hardware requirements get more stringent and even if the update works, there may be issues. 

I believe I have found somewhat of a solution for this issue, I have been dealing with it for awhile as well. For me, when the playback keeps jumping around while scrubbing footage ive interpreted from 120 to 24, I have found that rendering the clip twice eliminates this issue.

I have a brand new 2020 iMac with 32gb RAM, solid graphics card and a fast processor. The hardware is definitely not the issue here. However, after rendering the first time, the clip will usually show a yellow line above the clip, and then green after the second render. At this point, the scrubbing issue goes away.

Hopefully this is just a bug that can be addressed, but for now, this seems to work.

Here's a link to the other thread:

https://community.adobe.com/t5/premiere-pro/stiiillll-getting-glitchy-scrubbing-on-interpreted-footage-in-source-window/m-p/11201513

I am have the SAME PROBLEM!!!!  Jumping all over when trying to scrub manually, and using the JKL commands for premiere to playback fast.  But also when just manually scrubbing, it jumps all over to random frames and stutters.   Never had this issue until I updated Premier Pro recently.  ADOBE -- Give us some answers!!!!!!!!!!!!!!

What "changed" was updating code. Applications have to move forward with media and gear. So the newer versions of most complex applications will typically require newer, more capable gear than older versions.

I've had computers in my shop since the 80's, and when we got our first computer ... we "splurged" ... and got the HUGE 40MB hard drive. That's right, 40 megabytes. We were told that was absurd, we'd never use all that much space. The computer had a base RAM of 600-something bytes (I think that's the figure) of RAM, and we also splurged for installing extra, so we had a full megabyte of RAM. Absurd as it was.

I don't know how many "major" programs that I still have the floppy or optical discs for ... that haven't worked on any computer for decades. dBASE ... that was a HUGE company in digital terms. THE database app to have. Any business of any size, that did any computer tracking of anything, used dBase.

Know anyone working in dBase now? Hmmm ... oh, btw, have you ever heard of dBase? When I mention that app anymore, I do tend to get blank stares.

Yea ... time ... and computers ... and applications ... move on. It's a right pain, as I thoroughly hate switching to a new computer, getting all my apps, data, preferences, everything just working again. Besides the cost. And I desperately need a new rig, it's awaiting the missus' go-ahead on purchase ... gonna be around $5G USD. Big OUCH. But ... for what I do, and planning to use it over the next 3-4 years ... I can't go less.

Neil

This is landoe,

I'm not sure if it's the issue but your CPU and your GPU do not meet miniumum system requirements. What happens if you move back to version 13.x (2019)?

Thanks,
Kevin

I have the same problem and looking for solution. I use Asus ROG with i7 9750H with 1660Ti. The other problem is when i use call out graphic sometimes the program is crash or freez and work very very slowly. As you can see the laptop have two GPUs and i think the problem comes from the fact that the Premiere uses the built-in video card for playback. I tried everything that could be done but the result did not change. I just haven't tried disabling the integrated video card, but I don't know how.