Participant

Performance Issues with Multicam Project in Premiere Pro (PC vs Mac)

Forum|Forum|10 months ago
April 24, 2025
2 replies
304 views

Hello,

I'm experiencing severe performance issues in Premiere Pro when working on a complex project on my PC. The project includes a 10-camera nested multicam sequence and 50 audio tracks.All proxy files are encoded in Apple ProRes Proxy.I’ve tested the project in both Premiere Pro 2023 and 2024, and the results are the same.

My Playback is smooth, even in multicam view. However, editing is extremely slow — moving clips on the timeline, clicking, trimming, and other basic interactions have major delays. Proxies are active, and High Quality Playback is disabled.

I tested the exact same project on a Mac, and the performance is significantly better. Timeline interactions are fast and responsive, so the issue seems to be related to PC performance or configuration, not the project or media itself. Ex: Moving a big chunk in my timeline: 68sec with PC. 30sec with Mac

What could be causing this lag on my PC?
Are there known settings or optimizations specific to PC that could resolve this?

Thanks in advance!

@Fergus H

Processor: Intel Xeon Gold 6136 CPU @ 3.00GHz 2.99 GHz

Installed RAM: 96GB

System type: Windows11 64-bit operating system

Graphics Card: NVIDIA Quadro 4000

jamieclarke

Community Manager

Hi @vicky36826950bk7k - Can you let us know which gpu driver version you have installed? Adobe recommends using the "Studio" driver version when working in Premiere Pro.

Is your media all the same?

Could you right-click on one of your media clips in the Project panel, choose “Media File Properties”, and share a few screenshots of what you see there? That’ll help us get a better look at the source media details.

On macOS, Premiere Pro playback performance is generally better with ProRes proxies because Apple hardware accelerates ProRes very efficiently. However, since you’re on a Windows system, you’d likely get better performance using H.264 proxies instead that format tends to be better optimized for hardware decoding on most PCs.