ProPresenter performance settings for smooth playback

Stuttering can come from the media file, the storage path, total output load, drivers or the wider signal chain. A useful approach is to isolate one variable at a time instead of assuming the computer needs replacing.

Diagnose in this order

Work through these before changing any settings. The order matters, because each step rules out a whole category of causes.

1. Does one specific clip stutter, or many of them? A problem limited to one file points first toward that file; a problem across many files makes the wider system and output load more important to test.
2. Does it stutter from local storage? Copy the clip to fast local storage and test again. Network shares, removable drives and cloud-synced folders add variables that are useful to remove during diagnosis.
3. Does it improve with a simpler output setup? If it does, total output pixels or part of the signal chain may be contributing to the problem.
4. Does it stutter with nothing else running? Quit browsers, sync clients and streaming software, then retest.

Get your media right

Start with the media file because it is easy to test without changing the production machine.

• Codec. Renewed Vision recommends H.264 or H.265 for normal playback, and ProRes 4444 for videos that require an alpha channel.
• Bitrate. Renewed Vision currently recommends 30 Mbps or less for HD and 50 Mbps for 4K when using H.264/H.265 delivery media.
• Alpha channels. Clips with transparency need a format that supports it properly. ProRes 4444 is the usual recommendation.
• Resolution. If a 4K source is only ever shown in a 1080p workflow, testing a correctly sized 1080p delivery copy can reduce unnecessary decode and scaling work.
• Frame rate. Mixed source and output frame rates can create motion judder. If motion looks uneven, test a version prepared for the frame rate used by your production workflow.

Use local storage as a diagnostic baseline

External and network storage can work, but they add bandwidth, cable, network and background-sync variables. When diagnosing a playback problem, test the same file from fast local storage first. If the local copy is clean and the original is not, investigate the storage path rather than changing unrelated ProPresenter settings.

System settings on the production machine

• Disable sleep, screensaver and automatic display dimming.
• Turn off notifications, which can appear on the audience output.
• Postpone operating system and application updates until after the event.
• Check whether antivirus, backup or indexing activity is saturating disk or CPU during playback; do not disable security protections just to make a test pass.
• Pause non-essential cloud synchronization during a controlled test so you can see whether background disk or network activity is part of the problem.
• Keep GPU drivers current on Windows, but update them midweek and test afterwards.

Reduce the pixel load

If testing shows the machine is genuinely at its limit, reducing total output pixels can lower the workload. Only reduce resolution where it still meets the viewing requirement, then retest the same media and output path so you can confirm whether load was actually the bottleneck.

When to investigate hardware

If the same problem remains with vendor-recommended media, fast local storage, minimal background load and a simplified output path, a hardware or driver bottleneck becomes more plausible. Use ProPresenter's screen performance statistics where applicable, check the exact machine/GPU limits, and upgrade only after you can identify the constrained part of the workflow. Our requirements guide explains the vendor-published workload factors.

Build a habit, not a fix

Re-encode media as part of preparation rather than as an emergency response. A five-minute conversion on Thursday is a much better use of your time than a stuttering background loop on Sunday, and it makes the whole system predictable, which is really what you are buying with all of this.