When Proxies are ON, my video playback freezes

[AblazeApax]

When I activate a proxy, that I have attached the same footage, my video playback freezes after a few seconds and the audio does still play in the background. I just downloaded Adobe Premiere Pro on my Macbook. This process would work for me when I used the 2020 version, so I'm confused as to why its not now. Additionally, playback works fine when playing back with 1/4 resolution, but I want it to be completely smooth as it was in the 2020 version.

I have version 24.3.0 of Premiere

I am using a Macbook Pro with:

Processor: 2.4 GHz Quad-Core Intel Core i5

Graphics: Intel Iris Plus Graphics 655 1536 MB

Memory: 8 GB 2133 MHz

[Kevin-Monahan]

Hi @AblazeApax,

I read your note. Check system requirements: https://helpx.adobe.com/premiere-pro/system-requirements.html. Are you meeting specs?

If your computer worked before but not now, progressive versions of the software do need more power as time passes. Sorry for the frustration.

Thanks,
Kevin

[Robert31074709yn47]

I am having the same problem and I think it's due to clip lenght, over a certain length the proxies just freeze, this can be in the middle of a clip that has been proxied.  When the proxies are turned off the clips play fine but obviously for a quicker easier workflow I'd love the proxies to work, any tips greatly appreciated 

[Kevin-Monahan]

HI @Robert31074709yn47,

Thanks for your notes on this bug report. In attempting to reproduce the bug, I had similar issues. I used a ProRes preset at half-res. I also used the new custom watermark feature. Can you provide any details so that we can provide them to the team?

Thanks,
Kevin

[Kevin-Monahan]

The status of this bug report is updated.

[Robert31074709yn47]

Hi Kevin, thanks for getting back to me.  I've realised that sometimes when proxying through ME for some reason it doesn't fully proxy the entire clip so that's why the clip is freezing as the proxy is incomplete, I've now gone back through and re-proxied the clips which were faulty and this has fixed the problem but maybe there's an issue with ME and proxying