Quentin you could always try to downgrade your project by hacking the .xml inside the .prproj : https://www.youtube.com/watch?v=g8ecJNJsnn8

UPDATE: ADOBE RESPONDED TO ME

This is what they had to say, basically...

"We know, just use 2019."

This includes having to backtrack to 2019 versions of premiere, after effects and media encoder. Sorry but... it's 2020. How did they break such a crucial component that so many of their creators use. No "sorry for your inconvenience", we get to spend a bunch of money for software they seem in no rush to patch.. Goodbye to everything I started in their 2020 version of premiere.

https://www.youtube.com/watch?v=opBz0eJLrFg

This worked for me

Im having issues with my audio and videos i put into timeline that are being too fast with the video and audio and i NEVER messed with the speed, and it even says its at 100% is this a bug and or anyone know how to help me fix these issues :( ?

I have the same problem and a deadline! Totally unuseable!

Same problem here.

Temporary solution of Ewan Fletcher works, where you need to render the clip.
At least I can edit!

ADOBE WAKE UP!!!

Having the same issue. How can this still be an issue after months? Please fix ASAP this is a basic function Adobe it's not acceptable.

Btw a temporary workaround for basic speed changes - if you nest the clip you want to speed up before changing the clip duration, then change the speed of the nested clip, you will be required to render to get playback, after rendering the clip plays back at the new speed without the choppiness/stutter.

Very annoying workaround but got me out of a hole.

Fix please!

Same here...Frame Freezes after Speed-changes...Not cool Adobe...Nooooot cool!

Please fix this Adobe, this is a terrible situation you've put us in

I'm sick of Adobe cut-and-paste replies, blaming customers' computers when 2020 14.0.1 is the issue: slow playback with stuttering audio and multi-frame backtracking regardless of CUDA settings. Just as galling is Adobe's refusal to apologize, admit its mistakes and keep customers aware of resolution progress. Transparency is the responsibility of CEOs, Shantanu Narayen.

Being tone deaf to customers is inexcusable lack of corporate governance. Time to follow the money trail and take Adobe's failures to stock market websites in advance of the company's March 12 quarterly conference call. Adobe's Busines Ethics hotline: (800) 300-1026,

I have the same issue. I really surprised cuz I didn't think that many people gonna have the same problem. We need a solution. It's our tool to work and we have to respond to our clients. We pay for good software.

This bug also screws with proxy files. Premiere 2020 seems to be really buggy. Lots of other things that just don't work right that seemed to work fine in previous versions. Need an update with fixes.

Adobe Please Please fix this. I just updated and now it is affecting my clients and my business. The issue is glitchy playback in higher frame rates, plus ramping issues

I've noticed this issue as well. Adobe needs to fix this ASAP or I'm going to have to switch to Final Cut.

awful playback since upgrading. Shuttling at double speed results in audio dropout and stutter. Working with MXF files at 1080P but happens with proxies too.

I can't believe Adobe is charging everyone so much money for subscription and they're not fixing all these issues for months! I have a whole list of things they need to fix. Speed ramping is so important to so many people, and the dynamic link between premiere and audition also doesn't work. Super annoying!!! kudos Adobe 👏🏽 just perfect 👌🏽

Same Here, it's been more than 5 month that we have the same problem.
You can't review the footage that if you play the timeline is playing at 0.5fps.

This is unaccettable.
We're now thinking of switching to Resolve.

Ok, so I had a very similar issue so I tried exporting just a few in/out points to see what would happen. Turns out that if my in/out points contained a marker the export wouldn't work... so I removed all of my markers and rendered the entire video perfectly.

I have no idea what this means or if it's an isolated incident, but wanted to share just in case it makes sense to anyone else who could find a real fix to this issue.