Propresenter 7 Release Notes 🔥

This is the "thank goodness" fix. For the last two minor patches, hitting Undo was terrifying—you never knew if it would remove a typo or nuke your entire song arrangement. The release notes confirm this nightmare is over. 5. Slide Layering: Alpha Channel Love The note says: "Improved rendering for layered slides with alpha channels (PNG/TIFF)." What that means for you: If you use lower-thirds, animated logos, or transparent overlays, they will render sharper and without the "black box halo" effect.

We’ve all had the "blue screen of death" on a stream because ProPresenter lost connection to the NDI source. This update significantly reduces that handshake failure. If you live-stream, this is the single best reason to update. 3. Audio Playback: Finally, Sane Cue Points The note says: "Fixed an issue where audio cues would drift when using 'Play from Marker' in a loop." What that means for you: If you use ProPresenter to play backing tracks or sound effects (slide advance cues, pads, stings), they now start exactly where you told them to. propresenter 7 release notes

We’ve dug through the latest so you don’t have to. We filtered out the developer jargon and focused on the features that actually change how you run a service. This is the "thank goodness" fix

This update doesn't look sexy on a spec sheet, but it will make your Sunday run 15% smoother. And in church tech, 15% fewer headaches is a miracle. This update significantly reduces that handshake failure

Here is what’s new, what’s fixed, and—most importantly—why you should (or shouldn’t) hit “Update” before Sunday morning. The note says: "Improved Stage Display alignment and aspect ratio handling for custom layouts." What that means for you: No more cut-off chord charts or lyrics bleeding off the edge of the iPad.

Drop a comment below if you’ve found a hidden bug—let’s help each other out before sound check. Disclaimer: Always test major software updates on a rehearsal computer before deploying to your main production machine. This blog post is based on general patch notes behavior; check your specific build number in the app.