Premiere Pro v24.4 - footage buffers and freezes even after rendering

[milesl78286852]

The latest version of premiere pro (v24.4) has caused all of my projects' footage to buffer and freeze frame even after rendering, making it completey unusable for me. For example, a clip where I have the scale key framed in to out will still scale in, but the image will be freeze framed for no reason. This is affecting a large majority of clips on the timeline of every one of my projects and I am unable to get any work done using v24.4. For an update that's for "bug fixes and other improvements", it's complete garbage and ruined all of my work. Adobe needs to get it together because this software is worse than it's ever been. 

SIDENOTE: I have another issue with the transform effect. Scaling in past a certain point makes the effect stop working. I'll scale in at 249 and it'll be fine, and then at 250+ the render bar will turn red and the effect stops working (it's no longer zoomed in). I swear, it's always random bugs and problems with effects that make absolutely no sense whatsoever and it's really annoying and bizarre. Quite frankly this is ridiculous considering how much I'm paying to use this software 

Mod note: Edited for content. Title was changed to reflect issue.

[artofwot]

Interesting - I'm still on 23.3 and have avoided 23.4 because of the issues I've read about. But two of my co-editors are using 23.4 on the same Production and after they edit the project in 23.4, I'm experiencing the freeze frame issue with the project on 23.3.

It's happening on BRAW footage for me. The only solution I've found is to re-import the footage and replace the old instances of the clips in the multicam sequence.

I've tried a bunch of other things - clearning media cache, plugin cache, detaching proxies, offlining and relinking - nothing else worked for me. Very frustrating.

[Kevin-Monahan]

Hi @artofwot,

I got your note. Are you using the free version of the BRAW plug-in or the Autokroma one? Since BRAW is not a supported format, you might try the latter plug-in if you are using the free one. It is difficult to address a bug with BRAW since it is not supported by the engineering team.

It is unfortunate that you and others are receiving unexpected behavior from BRAW footage. From Adobe support's perspective, you might try transcoding the footage to a mezannine codec (ProRes, DNxHD/HR), or create proxies with those codecs if you would like a better editing experience. Probably not what you wanted to hear, but that's what I would do rather than live with my mulit-camera editing functions going south.

Native BRAW support is one of the top requested features. You can upvote for it here. Very sorry for the frustration.

Thanks,
Kevin

[artofwot]

Hi Kevin!

Yeah, no worries! I haven't seen enough to know if this is BRAW specific. I had my co-editors roll back to 23.3 and I think that'll help. We are using the paid version of the Autokroma plug-in and it's always been very reliable for us so this seems, at least for now, 23.4 related.

[Kevin-Monahan]

Hello @milesl78286852,

I read your message. It sounds like you are having performance issues, mainly. I'm in support and not on the product team, so perhaps I can help. If you want to file a bug report that is actionable, may I suggest you format your post, as outlined in How do I write a bug report?

Use the template below to provide us with information: 

• Issue - A short description of the problem. 
• Adobe Premiere Pro version number: FAQ: How to find the exact version of Premiere Pro you're using?
• Operating system - Windows or macOS, and which version of those operating systems?
• System Info: CPU, GPU, RAM, HD:

  • CPU

  • GPU and Driver Version

  • RAM

  • Hard Drive (and, if external, how the drive is connected: USB 3, Thunderbolt, etc.).

• Video format: Provide information about the type of video you're using. For example, XAVC-I 4:2:2 10-bit. If you're not sure, let us know what settings you selected on the camera. If you don't have access to the camera, sharing a sample file is useful. 
• Workflow details: Tell us any specific info about the project or sequence. For example, is it a multicam sequence?
• Steps to reproduce - Exact steps, in a numbered list, that are needed to reproduce the problem.  
• Expected result - What should have happened after the last step?
• Actual result -  What did happen after the previous step? 

Optional but helpful: upload media, project files, screenshots, or screen recordings demonstrating the issue. 

With that info, the product team can try to reproduce your issue and address it internally. It can also help support with diagnosing the source of your problem.

Keep in mind that you can always contact assisted support here for one-on-one troubleshooting. The chat pod is in the lower-right corner. Please ask to be connected to the "video queue" where our video support staff can help you directly. Ask for a case number, so it can be tracked by you and my staff in support. The video queue is open Monday to Friday from 7AM to 7PM.

Sorry for the frustration and the hassle.

Thanks,

Kevin

[Kevin-Monahan]

Good morning, @artofwot,

Thanks for the response and added context. I hope that rolling back can help in the short term. For my personal projects (yes, I am an editor by trade), I am flying on 23.4. However, I have a pretty clean system with no plug-ins installed, using standard formats, and simple projects (I use a Production containing many small projects—works great).

I have been hearing about issues recently on macOS, though. My colleagues and I cannot reproduce any such performance issues that have been raising the alarm. If you could detail your specific issues, perhaps we can flush out a repro case that the engineers can chew on. Feel free to file a separate bug in a new post, if you want, and I'll advocate on your behalf. Hope your day goes well and thanks again for posting.

Cheers,
Kevin