High priority bug: EVERY sequence crashes at 34:46 on the timeline in latest update v22.3
The latest update to Premiere Pro has a HUGE and crippling bug on my system (and judging by the forum posts many others too). Every timeline I open on projects new or old crash at 34:46 on the timeline. Exports hang at that time and Premiere can't be recovered to a useable state without a Force Quit. Audio sticks on the sample at that time when scrubbed over.
This is a massive problem that renders this version of Premiere Pro unusable for sequences over 34:45 duration and needs fixing as the highest priority.
This was fixed in the 22.3.1 release. Update to at least that version or later to get the fix. This problem only affected version 22.3.0.
Chris Spiegl commented
Adobe also published that this is fixed in v22.3.1
> Premiere Pro stops playback at around 34:46 (Fixed in v22.3.1)
Chris Spiegl commented
Seems Fixed in v22.3.1
I just installed v22.3.1 and the issue did not happen with this version.
I was able to play from 34:40 to 34:59 and could pause after without issues.
I also exported two projects with sequences ca. 45 minutes in length with Media Encoder v22.3.1 and was able to complete the export (which did not work with v22.3).
I am on M1 Max MacBook Pro with macOS Monterey 12.4 Beta (21F5058e).
For me, this was happening on a master sequence which has a multi cam sequence with 3 angles for video. Audio was one mono and one stereo track (however the stereo track was unused at the 34:45 mark.
I really hope this is resolved and will not happen again. What a crazy bug!
Ryan Green commented
Had the same issue, didn't matter what I did, or what footage or project it was. It was always occuring. Rolled back to 22.2, and it fixed the issue.
Joe Murphy commented
That particular sequence had 4x audio tracks - each a Standard mono track and the project was 30fps 48Khz audio. Other sequences seem to have the same issue with a variety of track layouts. I've reverted to 22.2 the issue is solved there.
Rick Altizer commented
Premiere Pro 22.3 hangs at 34:44:00. Tried everything, different media, clearing cache, updating graphics card, always hangs at exact spot:
34:44:00. As soon as I reverted back to Vs 22.2 problem went away.
Andy Gilleand commented
In my sequence, I had a 5.1 master, 3x 5.1 tracks, and two stereo tracks. My source footage has 5.1 uncompressed audio, and I'm using all 3 of the 5.1 tracks with that audio.
The first stereo track was mapped to output in the center channel only. I had only one mono audio clip in this track. When I deleted this audio clip, the bug stopped happening, and I was able to export my entire sequence. This clip was something like 5 minutes into the sequence, far before the 34 minute mark, and that section itself rendered just fine.
I'm guessing premiere probably does some kind of optimization by removing unused tracks before rendering, which perhaps could have been what solved my issue.
Although I was still using the second stereo track which had the default channel mapping.
Hope this helps diagnose the issue.
Dan Brandenburg commented
I'm having the exact same problem on Windows. This new interface is just awesome.
Kevin Monahan commented
Thanks for reporting this, Scott. It's in support's list of top issues.
Scott Taylor commented
22.3 and beta of Premiere Pro/Media Encoder get stuck at 00:34:43 in the timeline. This has been identified on the forums by people on Win/Mac platforms. My own system is MacBook Pro M1. If I'm just playing the timeline, the audio first cuts out and a few seconds later video stops. I can trigger this by scrubbing along the timeline until I hit the magic glitch point. I am usually able to save after hitting the glitch, but playback is broken and I must force close the application. I can edit any point on the timeline before or after that point, as long as I don't actually play that glitchy time. Media Encoder also becomes unresponsive after it passes that point in the timeline. I've noticed when it happens that the TextEdit or Quicktime Player applications spontaneously start, though that is inconsistent and may not be related. We've tried uninstalling, clearing caches, etc. All the expected workarounds... But this seems a lot more global of an issue than just bad data in someones cache. https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-renderer-crash-at-34-43-in-the-timeline/m-p/12887774#M406307 - Rolling back to version 22.2 of both applications 100% solves the problem.