Companion and Propresenter locks up

[BeardedFollower]

Describe the bug/issue I am seeing an issue where upon startup, both companion (using streamdeck xl) and Propresenter become practically unusable, where clicking a button on the stream deck takes 5 seconds to trigger the ATEM to change input. Curiously, the issue does not occur when the presentation is targeting the presentation layer, and issue can be avoided if I manually switch the targeted layer before opening Companion, and then switch back.

To Reproduce Steps to reproduce the behavior: Open Propresenter, fire the beginning of the presentation targeting the announcement layer.

Expected behavior I would expect to be able to open propresenter and have a rolling presentation targeting the announcement layer, while being able to control other areas of propresenter via the companion app.

Screenshots Every second there's a large amount of "slide triggered" notifications in Companion. There are no buttons in companion that trigger this playlist, it is triggered manually within Propresenter.

In this image, you can see that we have a library item called "Announcements-Scroll.old" that is on a 10 second timer to the "announcements" layer within Propresenter.

Local Propresenter instance config

Versions/Environment (please complete the following information):

• ProPresenter Version [e.g. 7.9.2] 7.9.2
• OS of ProPresenter Machine [e.g. MacOS 11.6/Windows 10] Windows 10 ver 21H2
• Companion Version [e.g. 2.3 ] 2.3.1 (2.3.1+4641-v2-3.1-dc01ac7c)
• OS of Companion machine [[e.g. MacOS 11.6/Windows 10] Windows 10 ver 21H2
• Debug log output when issue occurs (Turn on debug log) FPC-STREAM-JC_companion_log_20221008-1109.csv

*Any Other Context Announcement-Scroll.old.pro.zip Attempted to rename presentation file to .old and recreate, but issue persisted.

[Roadsguy]

I get a similar issue, though it doesn't seem to be related to Announcements layer slides and instead happens about 9/10 times a connection is established between Pro7 and Companion. While the Slide Triggered lines flood the Companion log, Pro7 is largely unresponsive, though media layer videos (such as background loops), timers, and other content continue to display properly.

Pro7 is also unresponsive to commands from Companion, such as a button I have that triggers a Specific Slide action and a Set Look action. However, if I disable the connection within Companion, those actions will sometimes only then pass through, long after I pressed the button.

I'm running ProPresenter 7.10 with Companion 2.3.1 on Windows 11 21H2.

[BeardedFollower]

@Roadsguy Just wanted to follow up on this, I updated to the latest Propresenter 7.10.2 with the latest BETA Companion build 2.4.0+4741-beta-cc597a5b and the issue seems to be resolved.

[hartjacob]

I'm having this same issue running ProPresenter 7.12 and Companion Build 2.4.2 (2.4.2+4911-v2-4.2-fcb5a863). Is anybody else still having issues with this or are there any other solutions? Thanks!

[hendrikmalgo]

I have the same issue and have done some extensive testing. It is definitely related to the announcement layer. Whenever I have it on and enable the connection in Companion, the mass triggering starts. Fortunately we don't need the announcement layer but can run our slides from it on the normal presentation layer.

I hope this problem will be fixed soon. In the meantime, my workaround tip would be not to run slides in the announcement layer but to find another way to do it.

[hartjacob]

Thank you! Turning the Announcement layer off worked. However, I really need to use the layer in my workflow. BUMP for a fix to this ASAP!

[BeardedFollower]

@hartjacob have you tried just using the native ProPresenter APIs? I transitioned to using the API, and it's been significantly more flexible for us.