Skip to main content
Participant
January 24, 2023

BUG: Playback in timeline wont stop when moving at double speed or more (v22)

  • January 24, 2023
  • 78 replies
  • 5379 views
in the newest update (v22) of premiere pro, when you shuttle right in the sequence at double speed, (or more) the playback won't stop, even when shuttle stop is pressed. Adobe premiere acts normally otherwise, (you can save and quit) but it will still keep playing at that speed. Even closing the sequence doesn't make it stop. You have to close out of the app and then re open the project.

78 replies

Participating Frequently
February 28, 2024

Ps where should people send project files for analysis and fixing?

Participating Frequently
February 28, 2024

Also, it doesn't just happen when playing at double speed, but intermittently during normal speed editing / playback. Probably spending 10-15 minutes of each editing hour waiting for the timeline to stop playing. 

Participating Frequently
February 28, 2024

It is beyond annoying for me. It is totally interrupting the workflow. Using ProRes proxy files in the project exclusively. No audio effects. M2 Max Macbook Pro 2023 with 32gb RAM  OS 14,3. What is the fix?????

Participating Frequently
February 28, 2024

I am having the same problem with version 24.1.0 build 24 running in an M2 MacBook Pro. Is there a fix or a version that can be reverted to to address this? It is virtually impossible to edit with this bug. 

Participant
January 2, 2024

Same thing happening for me. Yes, it's an older project that I have not touched for yeas and very long and instensive, but geez, this thing ought to be fixed by now, no?

Chris Spiegl
Community Expert
Community Expert
December 22, 2023

Sadly I can still report that this is a reality. It heavily depends on the video files, often the codec, and effects on the audio timelines. All those things play a role in the playback getting hung up or not.

 

But when it happens, it is incredibly annoying when you can't stop playback.

 

I just wish it would overall be more solid and reliable so that these type of things just don't happen.

ryanhasegawa
Participant
December 21, 2023

fwiw: after working on an old version of like premiere 22 for like a year now, I tested updating to 24.03 and at least for my timeline its been working pretty solid for a week or so. Fingers crossed

Participant
December 20, 2023

UPDATE: sorry you can forget that method, it's not working for me after 1-2H of editing, seems like it only delays this bug

Participant
December 20, 2023

Clarification: it's not fixing it 100% it's more like instead of closing premiere you would need to wait 1,5 minutes but you'll retain your progress and can save it, also for me if 3-5 presses of space do nothing I'll start to hit Command+S or CTRL+S and when premiere gets back it will show me saving dialog window.

Participant
December 20, 2023

I got the exact same issue with any multicams regardless of camera count 2-24 doesn't matter, when I start it is fie to go x2 speed with ulticam view on, but after 10-20 minutes I will hit play and won't be able to do anything at all, and the worst part is that all cameras are butter smooth and there is a clear sound, just no control at all, so I know that my machine is good enough to play all of them in multicam view.

 

But I was trying to counter it and nothing works, except one thing, it's very inconvinient to set up but I wil try to add dead space on my timeline every 2-3 minutes, I will just paste insert adjustement layer on video track above my nest, step forward many and insert it again and till the end of my timeline (step forward many can be adjusted from 5 frames to 3 minutes, and for timeline of 13 hours that is a work for autohotkey or any script app)

and when I got all timeline mangled with all those adjustment layers I will delete this track in wich adjustment layer sits and I got myself a dead space to change something enough to not have this issue, I think it's somehow affected by cache that premiere creates and those blank spots allow it to relax and, I honestly have no idea but it works for me.